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

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: [xml-dev] An approach to let XML 2.n resources hold multiple entitie

[ Lists Home | Date Index | Thread Index ]

Nice,

In addition to this discussion, another thing I'm interested in seeing
proposals on is ways to better nest XML, as in SVG embedded in XHTML,
instance data in XForms, etc. (including how to deal with entities and ID).

One partial solution I've considered is a "Doctype instruction". Instead
this allowed only in the prolog:

<!DOCTYPE html 
     PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>

You'd have this, allowed anywhere where there's a transition between
different "Doctypes":

<?DOCTYPE html 
     PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";?>

Since there are multiple versions of some vocabularies that can't be
distinguished by the namespace, only by the DOCTYPE, something like this
would help processors figure out what to do.

The PI syntax isn't a requirement, just something to possibly smooth over
the transition.

.micah


-----Original Message-----
From: Rick Jelliffe [mailto:ricko@allette.com.au]
Sent: Thursday, March 20, 2003 9:50 AM
To: xml-dev@lists.xml.org
Subject: Re: [xml-dev] An approach to let XML 2.n resources hold
multiple entities


From: "Paul Prescod" <paul@prescod.net>

> Here's a simpler proposal. Take this:
> 
> [1]    document    ::=    prolog element Misc*
> 
> And make it:
> 
> [1]    document    ::=    prolog (element Misc*)*
> 
> This is not straightforwardly SGML compatible, but I think it is 
> significantly easier these days to change SGML than it is to change XML. 

Nice. But I don't think that it does the same thing: my proposal provides
an alternate syntax for internal entities which also allows bundled 
other documents.  (Thinking about it more, it suggests that it might fill
some nice needs if the entity mechanism was rejigged to allow appendable
entities rather than having them in a prolog.)

I think you would need to have some top-level attribute available to
say "this branch does not form part of the infoset" so that it can
be referenced from an XInclude without appearing in the document
twice (assuming we will perform some kind of XInclude linking early).

Cheers
Rick Jelliffe

-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>




 

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

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