Board Thread:Consensus Track/@comment-22479560-20131027141943/@comment-22479560-20131027231916

@Kroq-gar78:

I summarize your point of view: Is that correct?"
 * You don't like the idea to only reduce Data Redundancy (= remove Data Redundancy from all pages except the item page itself, where property values from the switch statement are duplicated in the info box for example).
 * You like the idea of transcluding property values to completely avoid Data Redundancy, and
 * If avoiding Data Redundancy implies storing the switch statement, as in my first post this thread, on a separate page, you prefer an item subpage with a short name.

@Balagog gro-Nolob: I'll react to your post when I've tested Variables Extension, the below is without them.

The work on the example I promised in my previous post isn't finish but I've some intermediate results I'd like to share. 1. I made a page new Silver Ring (to continue the same example) that produces more or less (I took a few shortcuts) the same output as the current Silver Ring. With a more carefull migration the old and new page could be identical, except of the inconsistencies. 2. The new Silver Ring page has a subpage /Data that hold the switch statement. The new Silver Ring page uses the subpage several times to transclude a property value. For example. This is in line with: Kroq-gar78 wrote: ...I think if we do subpages, we could transclude a relative path, like so: ... 3. As a rough example to illustrate the quote below I migrated the current Infobox to a new Infobox. Documentalist wrote: The infobox now takes the properties one-by-one. This makes adding an extra field to the infobox time consuming because all item pages have to provide the additional properties on the infobox call.

With the switch and the spit above we can replace all single property parameters by just one property item: The infobox can use any property the switch offers, and if the infobox changes, the item pages remain the same.

The current InfoBox has the parameters: name, image, caption, weight, value, class, enchantment, and id. The new InfoBox only has one unnamed parameter.

The current Silver Ring uses the current InfoBox by calling it: The new Silver Ring uses the new InfoBox by calling it: To get the weight of the Silver Ring the new Infobox calls. The new situation is shorter, (and attractive for people that "like stuff that's easier to type") -^

If we have implemented the current Infobox and a future InfoBox would display the materials-required-to-create-the-item the future InfoBox interface changes: it gets an extra parameter 'components'. Because of this interface change all items that use the template have to change to provide the value of the new 'components' parameter.

If we have implemented the new Infobox and a future InfoBox would display the materials-required-to-create-the-item the future InfoBox can pick it from the Data subpage:. No interface change is required.

4. If we look at the wiki text of the new Silver Ring, we'll see that it's likely that all (jewelry) item pages are identical. All differences in the current situation are moved to the data pages. This gives us the opportunity to template the whole page.