On Mar 11, 4:39 pm, Yaron Koren <[email protected]> wrote:
> 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?
>
I think the mechanics are almost there for doing multiple categories
in a natural way. To use Patrick's example, my contact: namespace
contains [[category:Contact, Business, Person, ...,Group]] pages
(Contact is the superclass for the others). These categories' default
form has one (or more) for-templates for each class a contact is
allowed to be (in). My goal is to pass *zero* args to the
template:primary class, treating it as a 'bundle' of bundles of
properties, different from those that are mere bundles of properties.
Maybe some efficiencies will result during user training, queries &
maintenance.
Google aspect programming to get more info. Here's to fun without the
sun from the Pacific Northwest :)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
