>>
>> I've been building a fairly complex Schema using an XML-Data
>> definition converted to a DTD. I've been making extensive use of
>> inheritance, and have observed that I'm using inheritance to
>> accomplish three objectives. If XSchema provides or could provides
>> methods to readily accomplish these objectives, then we might be able
>> to sidestep poorly defined or difficult to implement constructs (For
>> example, I've avoided attempting to merge the child's content model
>> with the parent's content model)
[... useful suggestion for inheritance snipped ...]
>>
>> How readily does XSchema accomplish each of the objectives?
>>
>> Are there any minor enhancements to XSchema that would make these
>> objectives more achievable?
I think this is a very important area and one that a lot of us are keen to
get into. For example, at present I am implementing (part) of XML-data (or
XML-data-like) components in JUMBO. I am then finding that I need to extend
these for more specific objects. In my mind there are two separate, but
combinable issues:
- XML-data primitives. I think it would be extremely useful to implement
them (but without the additional relationships).
- deriving more specialised components from them (or from anything else).
I think that the XSchema team has been taking this in stages - i.e. first
get as simple a schema as possible and see if it works. This has to include
ways of extending it - possibly in ways like you suggested. Then think of
specific ways to extend it that we can all agree are valuable. Of course
this is all still experimental but I have good feelings that it's worthwhile.
P.
Peter Murray-Rust, Director Virtual School of Molecular Sciences, domestic
net connection
VSMS http://www.nottingham.ac.uk/vsms, Virtual Hyperglossary
http://www.venus.co.uk/vhg