OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: XSchema Spec, Sections 2.0 and 2.1 (Draft 1)

[ Lists Home | Date Index | Thread Index ]
  • From: Chris Maden <crism@oreilly.com>
  • To: xml-dev@ic.ac.uk
  • Date: Mon, 8 Jun 1998 16:47:31 -0400 (EDT)

[Paul Prescod]
> Reuse is important, but it should be more structured than even IDs
> and references. It should be strongly-typed. Something that is an
> attribute type in one context should be an attribute type in all
> contexts. It is the typelessness of parameter entities that causes
> problems. Getting all of the object types right in XSchema 1.0 would
> probably be a bigger project than we need.

But if they're general entities in XSchema, then they get parsed in
context, and their type is enforced by the XSchema DTD.  Picture this:

XSchema with XSchema DTD, before non-DTD entity mechanisms:

<?xml version="1.0"?>
<?xml:namespace ns="http://www.purl.org/NET/xschema" prefix="xsc"?>
<!DOCTYPE xsc:xschema
  SYSTEM "http://www.purl.org/NET/xschema/xschema.dtd" [
<!ENTITY para.content
 "<xsc:mixed>
    <xsc:element idref="emph"/>
    <xsc:element idref="literal"/>
    <xsc:element idref="term"/>
  </xsc:mixed>">
]>
<xsc:xschema>
  <xsc:elementdecl id="para">
    &para.content;
  </xsc:elementdecl>
</xsc:xschema>

This is a bit ugly, but it's clean: the type of a "parameter" entity
is validated because it's parsed in context.  Unlike DTD parameter
entities, they have to be declared in the prolog to the schema, but
that makes parsing cleaner.  But then, once there's a non-DTD way to
declare entities:

<?xml version="1.0"?>
<?xml:namespace ns="http://www.purl.org/NET/xschema" prefix="xsc"?>
<?xml:namespace ns="http://www.purl.org/NET/xents" prefix="xent"?>
<my-document-bag>
  <xent:entitydecl id="para.content"><![CDATA[
    <xsc:mixed>
      <xsc:element idref="emph"/>
      <xsc:element idref="literal"/>
      <xsc:element idref="term"/>
    </xsc:mixed>
  ]]></xent:entitydecl>
<!-- this is one example of why I think that you shouldn't try to
     tackle entity declarations just yet... -->
  <xsc:xschema>
    <xsc:elementdecl id="para">
      &para.content;
    </xsc:elementdecl>
  </xsc:xschema>
</my-document-bag>

-Chris
-- 
<!NOTATION SGML.Geek PUBLIC "-//Anonymous//NOTATION SGML Geek//EN">
<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
"<URL>http://www.oreilly.com/people/staff/crism/ <TEL>+1.617.499.7487
<USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>

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





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS