Subject: RE: XPDL (was Re: XML is broken) From: "Gavin Thomas Nicol" <gtn@xxxxxxxxxxxx> Date: Mon, 5 Apr 1999 09:05:55 -0400 |
> >manifest > > root xml doc > > subsidiary xml doc1 > > image 1 > > subsidiary xml doc2 > > subsidiary xml doc3 > > stylesheet alternative one > > stylesheet 11 > > stylesheet 12 > > image 13 > > stylesheet alternative two > > stylesheet 21 > > stylesheet 22 > > image 23 > > > >The mechanism of compound xml documents is clearly transclusion using > >XLink, and for stylesheets, import. This "manifest" could also be called a "catalog", and SGML systems have had such beasts for many years in various different forms. Some systems only used them for document-component lists, and others for both processing data and document components. Something like this is crucial to the success of XML (get's rid of all the PI nonsense), especially for email where multipart messages containing XML will be sent. I worked with Don Stinchfield on a catalog-based proposal for email of SGML some years ago, and it had many advantages... including mixed push/pull and not requiring any new mime multipart types (HTML in email requires multipart/related). Using XML for the encoding is obviously The Right Thing. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
XPDL (was Re: XML is broken), Simon St.Laurent | Thread | Re: XPDL (was Re: XML is broken), Chris Lilley |
RE: SUMMARY: XML Validation Issues , Ed Nixon | Date | RE: XML is broken (was Re: Why Does, Didier PH Martin |
Month |