Lists Home |
Date Index |
- From: "Steven Livingstone, ITS, SENM" <firstname.lastname@example.org>
- To: Didier PH Martin <email@example.com>, "'XML Dev'" <firstname.lastname@example.org>
- Date: Mon, 22 Nov 1999 15:07:00 -0000
I would say the content is the document. The BizTalk framework will simply
allow content to be transported in a message format, telling processers
which understand the relevent tags (ie. the BizTalk environment) what to do
with the content - where to route it etc...
I suppose it's much like posting a letter, where your content is hidden
within the envelope and the envelope simply has instructions (ie. Airmail,
Address etc..) on how the envelope should be handled? - Not sure about
That's a bit simple to explain the entire framework, but some BizTalk
processing would have to be done, although there is no reason why you should
not be able to directly extract the XML content within the <message> tags?
Steven Livingstone - http://www.deltabiz.com
07771 957 280 or +447771957280
Professional Site Server 3, Wrox Press
Professional Site Server 3.0 Commerce Edition, Wrox Press
> -----Original Message-----
> From: Didier PH Martin [SMTP:email@example.com]
> Sent: 22 November 1999 13:52
> To: 'XML Dev'
> Subject: What is a document?
> Continuing the reflection on biztalk like XML formats, a question occurred
> in my mind: In a biztalk like message, what is the document?
> Hypothesis 1
> The biztalk message is the document. Your content included in the biztalk
> message is a fragment.
> Hypothesis 2:
> The content is the document. The biztalk element is an envelope.
> We want to provide the message rendition for human consumption. Thus, the
> biztalk message is set for automated agents on both sides. However, we
> to provide a style sheet with the message so that if a human wants to take
> look at it, it can be rendered with style ;-)
> Hypothesis 1 - reasoning:
> If the biztalk message is the document, then the style sheet has to be
> included at the biztalk message level. But the real content and the part
> control by the sender is the fragment contained in the biztalk message.
> the biztalk processor may do the following if the sender included a style
> sheet in the fragment.
> a) remove the style sheet PI from the fragment
> b) import the fragment style sheet in its own style sheet.
> the two style sheet are merged
> Hypothesis 2 - reasoning:
> No it does not work without some processing from the biztalk engine
> the scope of action for a style sheet is the whole XML document, not a
> fragment. Thus, the biztalk message is the document, not the contained
> According to the actual state of the art, only Hypothesis 1 will fly. If
> think of rendition, we have to think of document. If we think about
> document, then a biztalk message is also a document. The content (your
> message) is only a fragment. In the XML world there is no actual standard
> notions of
> a) envelope
> b) multiple document embedding for transport (each embedded fragment being
> separate entity interpreted by different agents)
> Didier PH Martin
> xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
> Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on
> CD-ROM/ISBN 981-02-3594-1
> To unsubscribe, mailto:email@example.com the following message;
> unsubscribe xml-dev
> To subscribe to the digests, mailto:firstname.lastname@example.org the following
> subscribe xml-dev-digest
> List coordinator, Henry Rzepa (mailto:email@example.com)
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)