From the documentation Field names are a holdover from the 'old' revisions table in MediaWiki 1. Please explain how this answers the question in some more detail.
How it answers the question is not clear. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete?
Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta. Now live: A fully responsive profile. Visit chat. How do I request a ballot? When do I vote? When are polls open? Who Represents Me? Congress special elections Governors State executives State legislatures Ballot measures State judges Municipal officials School boards.
How do I update a page? Election results. Privacy policy About Ballotpedia Disclaimers Login. For this reason, the information recorded in the slots table is kept to a minimum about 25 byte per row. It is worth noting that the initial use case for MCR Structured Data on Commons led to a significant increase in the number of edits. This is however due to the data model used for the additional content Wikibase , which favors high granularity of edits.
The effect would have been the same if the data had been stored on separate pages, it is unrelated to MCR. MCR just provides a way to manage multiple content objects per page, it does not know or care about how this content is structured what model it uses. MCR would manage e. However, MCR enables data that has previously embedded in the primary content typically wikitext to be managed separately.
This allows such data to be stored in a more suitable form, such as JSON. MCR provides a place to store this data and integrates it with the update and rendering mechanism, but it does not provide a user interface for interacting with the data. MCR is designed to remove the need to embed structured data in wikitext.
One example for this kind of thing is the way TemplateData places meta-data about template parameters on the template page using a special syntax.
Instead, this information could be stored in a separate slot, in a machine readable form such as JSON. This would enable the creations of a specialized API and a dedicated user interface for displaying and manipulating this information. As of , MCR doesn't directly help with creating that API or UI, it just removes the complexities of extracting and replacing structured data embedded in wikitext.
Another example are categories: Wikitext uses a special syntax to place pages in categories.
0コメント