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

RE: What is a document?

  • From: "Didier PH Martin" <martind@n...>
  • To: "'XML Dev'" <xml-dev@i...>,"Mark Birbeck" <Mark.Birbeck@i...>
  • Date: Mon, 22 Nov 1999 22:00:24 -0500

mark didier
Hi Mark,

Didier PH Martin wrote:
> Didier reply:
> Yes mark, if we got the notion of scope for rendition it
> would be a lot
> easier to assemble fragment/documents into a whole. Obviously, each
> assembled part would have to take into account that it is
> included in a
> whole for rendition (i.e like an HTML+CSS document for
> example).

Mark said:
I wouldn't impose such a limitation myself. Why should the fragment
'know' anything about its container? (If I understand you correctly -
and apologies if I don't.) Provided it has its namespace declaration
then it can in theory exist in any container that will have it.

Didier reply:
It didn't meant that the fragment has to be semantically aware of the
container but more that the associated style sheet (the style sheet
associated to the fragment) has to be aware of the global context. For
instance, will only provide rendition instructions for the fragment.

Mark said:
In fact, with RDF you could just wrap some XML in a CDATA tag and bung
it in a description. Or you can place it in a BizTalk 'envelope', or you
can use MIME, or even package it up with headers and send it through
HTTP/WebDAV. Each of these has different notions of validity. RDF or
BizTalk (or XML Fragment Interchange) require that the containing
document is well-formed XML with its contained object(s). But a
PROPPATCH in WebDAV requires that the containing document is well-formed
HTTP (plus a bit), and the document describing the elements being
patched are well-formed XML. So we have different notions of
'correctness' with different transports.

So, we have the notion of a document that we need to transport, and it
has its own requirements as to well-formedness, validity, etc. And then
we have the transport mechanism which has its own means of communicating
errors, etc.. And in some situations XML will be used as the transport
mechanism - as with BizTalk - but I don't think it should logically be
treated any different to other transport mechanisms. (Of course it's
handy to have it as XML because we can use all our other tools to handle

Didier reply:
I agree

Didier PH Martin

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/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.

Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.