Altova Mailing List Archives


Re: [xml-dev] opposite of infoset

From: Robin Berjon <robin.berjon@------.-->
To: "Simon St.Laurent" <simonstl@--------.--->
Date: 8/20/2003 4:54:00 PM
Simon St.Laurent wrote:
> Well, not exactly opposite, but I need a term I can contrast with
> infoset, as in the following usage:
> 
> --------------------------
> If we look at this example:
> 
> <book  id="rt456">My book</book>
> 
>  From the [MISSING WORD] perspective, we have a start tag for a book
> element which includes some whitespace, then an id attribute with a
> value of "rt456".  The start tag is followed by the text "My book",
> which is then followed by the end tag for the book element.
> 
>  From the infoset perspective, we have a book element with an id
> attribute whose value is "rt456", and that element's content is "My
> book".
> --------------------------
> 
> "Text" doesn't quite seem appropriate, nor does "serialization",
> "markup", or "XML".

I agree that text and serialization don't cut it well, but what do you find 
wrong with markup or XML? They both seem fine to me.

-- 
Robin Berjon <robin.berjon@e...>
Research Engineer, Expway        http://expway.fr/
7FC0 6F5F D864 EFB8 08CE  8E74 58E6 D5DB 4889 2488

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.