Lists Home |
Date Index |
- From: "Simon St.Laurent" <SimonStL@classic.msn.com>
- To: "XML Dev" <firstname.lastname@example.org>
- Date: Thu, 25 Jun 98 21:24:19 UT
John Cowan wrote:
>Chris Maden wrote:
>> The other option would be for XSchema to standardize some sort of
>> documentation elements, similar to what's outlined above, or similar
>> to the DocBook reference pages.
>That is the option I originally proposed for the content model
>of the DOC element, using a small subset of HTML 4.0.
>See http://www.ccil.org/~cowan/XML/ibtwsh.dtd for the subset.
As I approach 2.6, XSchema Extensions, this becomes an enormous issue. The
2.6 XSchema Extensions
2.6.1 Documentation Extensions
2.6.2 Constraints on Extensions
Right now the DTD contains ONLY XSC:Doc (when I remember the namespace prefix)
elements for extension. The DTD I'm working with uses only the
itsy-bitsy-HTML elements for that area. To me, this seems inadequate for many
purposes, like data typing elements. (For straight documentation, I think
All of these other purposes may, of course, be achieved by reference, as in:
<MyXSC:DataType ElementName="Latin" Type="Text" MaxLength="90"/>
Where the Latin element would be specified to contain text of some sort, no
more than 90 units (bytes, characters, etc. depending on the spec) worth.
I'd like XSchema to include a way for this information to be kept with the
element declaration. While inclusion by reference works, it's not a lot of
fun to do cross-referencing when scanning through a huge schema.
a) add another subelement for XSC:ElementDecl
b) give XSC:Doc a content model of ANY
c) avoid doing this entirely
d) do something else I haven't thought of yet.
Suggestions? In the meantime, I'm working on namespaces.
Dynamic HTML: A Primer / XML: A Primer / Cookies
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)