Last modified: 2007-11-30 16:34:20 UTC
For red-links, it is sometimes ambiguous which form should be used to create the page being linked to: a relation called "appears in", for instance, could be linking to a page populate-able by a form called "Book", "Magazine" or "Newspaper", for instance. This can be solved if relations can have a relation defined for them called "Has alternate form" or just "Has form". There can then be two kinds of behavior:
- if there is a single "Has default form" relation defined for this relation, and one or more "Has alternate form", the red link will go to the default form, but a dropdown at the top will let the user select one of the other forms and go to that one instead, for this page.
- if there are only "Has alternate form"s (or "Has form"s), clicking on the red-link will take the user to a page containing only a dropdown (or maybe a bulleted list of links), letting the user choose which form to use to create this page.
There doesn't seem to be a need to allows this new relation to be used for categories or namespaces: both of these really only need one form, as far as I can tell.
Also, no page should have more than one "Has default form" value.
"Has alternate form" relation/property added in versions 0.7.7 and 0.7.8.