> But even with these one-per-element types/models I'm still
> not sure how
> to achieve the sort of application-specific "tightening" of
> the content
> model which Carl suggested though. e.g. if an app wants to tighten its
> own content model for dc:date so that it validates as a date
> rather than
> only to the loose base model, or if OAI wants all element
> content to be
> strings....
My XMLSchema knowledge is far from perfect, but have you investigated the notion of abstract types? That is,
<xsd:complexType name=dateModel abstract="true">
stuff about dateModels pertinent to the generic cases
</xsd:complexType>
Perhaps this approach is also flawed -- I don't think you can instantiate an element to an abstract type. BUT it does allow for the notion of "sub-classing", which is what we really want to do: we want to be able to view information as DC:date and as myDC:date at the same time ...
- Naomi Dushay
|