tm-pubsubj-comment message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: RE: [tm-pubsubj-comment] Good PSIs never die
- From: "Bandholtz, Thomas" <thomas.bandholtz@koeln.sema.slb.com>
- To: 'Kal Ahmed' <kal@techquila.com>,"'tm-pubsubj-comment@lists.oasis-open.org'"<tm-pubsubj-comment@lists.oasis-open.org>
- Date: Thu, 21 Mar 2002 13:54:28 +0100
[Kal:]
No
one has yet said that the documentation would be XML ! But even so which is more
human
readable:
<record>
<isbn>123456-09-23</isbn>
<auth-code>AHM1298</auth-code>
<pubdate>20011110</pubdate>
<stock-code>98993939385402</stock-code>
</record>
<book>
<book-title>XML
Meta Data</book-title>
<authors>
<author>Kal
Ahmed</author>
<author>Danny
Ayers</author>
...
</authors>
<published>2001-11-10</published>
<description>
-- blurb about the book goes here </description>
</book>
I
would suggest that XML of the first form is "machine-readable" and XML of the
second form is "human-readable". But depending upon the system(s) involved, the
first form might be the only form that can be automatically generated for the
subject indicator.
[Thomas:]
We have been talking about XTM, RDF, XHTML, customized
XML so far - all this is XML. But you may be right - needs not to be XML. But I
think it should not be binary encoded.
Readability only depends on the specific intelligence
implemented in the machine/human.
If I (human, hopefully) understand the encoding of
<auth-code> etc., I can read it.
If a machine doesn't, it cannot read it
neither.
Cheers
Thomas Bandholtz
XML Network
Competence Center Content
Management
SchlumbergerSema
Sema GmbH
Kaltenbornweg 3
D50679
Köln/Cologne
+49 (0)221 8299 264
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC