OTOH type enforcement may be hurt big time by having pages assoc'd with default forms rather than with categories (which have default forms). OTOH, it can provide adequate page customization, but the problem is that page level security remains an incomplete solution in mw. So I still vote for the more useful 'Has Primary Category', because I think it's safe to say that every resource has a fundamental, generally agreeable-upon, type. In multiple inheritance, it is at least "first among equals" that is being represented by the propery. It probably may also figure into defining computational contexts.
On Mar 11, 4:39 pm, Yaron Koren <[email protected]> wrote: > Well, the most straightforward solution would probably be to allow pages > themselves to have a "Has default form" value, which would most likely be > set through the template. It might be a reasonable option. > > By the way, I think the reason this hasn't come up as an issue before is > that, with Semantic Forms, pages usually only belong to one category: the > one that defines their "class"; all other data is handled through semantic > properties. Out of curiosity, what else are you using categories for? > > -Yaron > > On Wed, Mar 11, 2009 at 5:02 PM, John McClure <[email protected]>wrote: > > > > > > > Yes, alot of letters :) Thanks for the reply. I am wondering if there > > could be a better method that doesn't rely on (what I am hearing) is > > an arbitrary ordering of categories assigned to the page? Maybe what > > I'm thinking of is a special property that can be assigned to a P(age) > > -- call it: has Primary Category, or something -- that indirectly > > calls out which form is to be used to edit the P(age)... Again,, > > thanks for the reply. > > > On Mar 11, 12:38 pm, Yaron Koren <[email protected]> wrote: > > > Wow, that's a lot of letters. :) If I understand the question: there's a > > > separate table in the MediaWiki database that holds each page's > > categories; > > > that's where Semantic Forms looks, until it finds the first one that has > > a > > > form associated with it (if it can't find one, as you guessed, it goes on > > to > > > the namespace). I don't know how the order of categories in that table > > gets > > > set, but I wouldn't count on them always showing up in the same order. > > > > -Yaron > > > > On Wed, Mar 11, 2009 at 3:21 PM, John McClure <[email protected] > > >wrote: > > > > > It seems that the form selected for editing a page is based on (a) the > > > > first form found to be associated with a category assigned to the page > > > > (b) the default form for the page's namespace. Is this correct? > > > > > I'm having no problems creating page P in namespace NS using form F2, > > > > because the link [[form:F2]] is directly invoked. F2 is not the > > > > default form for NS, rather F1 is, but F2 is the default form for C2, > > > > the first category assigned to P (C2 is a subcategory of C1, whose > > > > default form is F1). C2 is assigned to P via T2, the first template > > > > invoked within P. > > > > > When P is edited. F2 is displayed, exactly right. But I am wondering > > > > if F2 is being selected only because T2 happens to be the first > > > > template specified within P. If it should be moved, say, to the bottom > > > > of P following some other templates that specify other categories to > > > > be affixed to P, categories that each have a default form: would that > > > > have an effect on which form is displayed for editing P? > > > > > Thanks.- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Semantic Forms" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/semantic-forms?hl=en -~----------~----~----~----~------~----~------~--~---
