[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XSchema: multiple proposals

• From: John Cowan <cowan@l...>
• To: XML Dev <xml-dev@i...>
• Date: Wed, 03 Jun 1998 14:31:36 -0400

Toby Speight wrote:

> Hmm.  I see your point.  I think what I dislked about Ron's proposal
> is the unconstrained #PCDATA here:
> 
> Ron> <!ELEMENT NotationValue (#PCDATA)>
> Ron> <!ELEMENT EnumerationValue (#PCDATA)>
> 
> I think that the list-of-elements structure can be retained, but with
> tighter constraints by writing
> 
> > <!ELEMENT NotationValue EMPTY>
> > <!ATTLIST NotationValue Value NMTOKEN #REQUIRED>
> > <!ELEMENT EnumerationValue EMPTY>
> > <!ATTLIST EnumerationValue Value NMTOKEN #REQUIRED>

That's what my draft does wrt enumerations.  I have more problems
with notations, because it doesn't make sense to me to have to
redeclare every notation name with every notation attribute,
since any notation attribute can refer to any notation name.
Thus I treat notation attributes like other attributes with
predefined types.
 
> John> Now that is an excellent idea!  However, it would be necessary
> John> to permit arbitrary XML markup within the doco, so a content
> John> model of ANY is probably the right thing here.
> 
> I'd like to agree at least some conventions here, but I think we
> should defer the details until later.  For the moment, I think we
> should concentrate on *where* we can put documentation.

Agreed.  I'll think about it.
 
> With IDREF, we could keep the documentation separated from the schema, but
> I'm a follower of the theory which says that the closer the documentation
> is to the code, the more likely they are to correspond.

I think that's best also.
 
> I don't think this is really workable.  We don't have SUBDOC in XML,
> nor do we have anywhere in the XSchema DTD that we can insert another
> tree rooted at XSchema.

For me it would be easy to add DOCTYPE (my root type) as another
top-level type co-ordinate with ELEMENT, ENTITY, and NOTATION.

> Even if the mechanics can be made to work,
> I'm concerned about ID clashes.  Can namespaces help prevent this?

Yes, particularly if there were some way to say "Colon-free names
brought in from this schema have an implicit 'ns' of xxxxx".

> I'm not convinced about wanting only to link-in whole XSchemas, either:
> it seems to me that lots of people would want P[aragraph] (and its
> children) from HTML, for instance.

I'll consider that.  But linking in HTML4.0:P brings in a lot of
baggage, specifically its content model, which includes virtually every
other HTML body tag.  I suspect that DTDs (and, a fortiori, XSchemas)
tend to be far more closely interwoven than people really suspect.

-- 
John Cowan	http://www.ccil.org/~cowan		cowan@c...
	You tollerday donsk?  N.  You tolkatiff scowegian?  Nn.
	You spigotty anglease?  Nnn.  You phonio saxo?  Nnnn.
		Clear all so!  'Tis a Jute.... (Finnegans Wake 16.5)

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Reusing/referencing partial XSchemas (was: XSchema: multiple ...)
    • From: Toby Speight <tms@a...>
  • Re: XSchema: multiple proposals
    • From: Peter Murray-Rust <peter@u...>

• References:
  • Re: XSchema: multiple proposals
    • From: rbourret@d... (Ron Bourret)
  • Re: XSchema: multiple proposals
    • From: Toby Speight <tms@a...>
  • Re: XSchema: multiple proposals
    • From: John Cowan <cowan@l...>
  • Re: XSchema: multiple proposals
    • From: Toby Speight <tms@a...>

• Prev by Date: XSchema: New draft of John Cowan's proposal
• Next by Date: Re: XSchema: New draft of John Cowan's proposal
• Previous by thread: Re: XSchema: multiple proposals
• Next by thread: Re: XSchema: multiple proposals
• Index(es):
  • Date
  • Thread