[
Lists Home |
Date Index |
Thread Index
]
If you're steering away from "serialization", then I would suggest
the term "concrete". Ironically, that may be too abstract for
your purposes.
The two I thought of before seeing your list below were serialization
and xml.
- Chris
-----Original Message-----
From: Simon St.Laurent [mailto:simonstl@simonstl.com]
Sent: Wednesday, August 20, 2003 12:56 PM
To: xml-dev@lists.xml.org
Subject: [xml-dev] opposite of infoset
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".
--
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com -- http://monasticxml.org
-----------------------------------------------------------------
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>
|
