W3C home > Mailing lists > Public > public-xml-binary@w3.org > April 2005

RE: Comments on XBC Use Cases

From: Cutler, Roger (RogerCutler) <RogerCutler@chevrontexaco.com>
Date: Tue, 12 Apr 2005 15:22:34 -0500
Message-ID: <71C38086EA230D43941DD0A3BAFF8CA929C63E@bocnte2k3.hou150.chevrontexaco.net>
To: "Bullard, Claude L (Len)" <len.bullard@intergraph.com>, "Norman Walsh" <Norman.Walsh@Sun.COM>
cc: public-xml-binary@w3.org

It seems to me that most of the use cases involve using binary XML to
transmit information, not to store it.  I know that this is definitely
true of the one I contributed.  In the case of transmitting seismic or
well log data how long the format remains valid (beyond the time
necessary to do the transmission) is utterly irrelevent except, of
course, for the obvious issue of software versioning.  If XML is used to
transmit the data (via a Web service, for example), it would obviously
be reformatted into the industry standard (which is not XML and which
almost certainly never will be) before archiving.

I doubt that the people involved with mobile devices care very much
about anything but transmission, either, although I am certainly not
qualified to speak for that industry sector.

So even if I agree (and actually I think I do) that archival storage
with binary XML is not a real good idea, I don't think that effects most
of the use cases very much.  The use cases indicate specific situations
where binary XML would be useful, in some cases to the extent that XML
would not be useable otherwise.  They most certainly do not indicate
that binary XML would be useful in ALL usage scenarios.  So although
there might be some point in listing the things binary XML would NOT be
good for in order to warn people not to make mistakes, I don't see that
it's very relevent to the issue immediately at hand.

-----Original Message-----
From: public-xml-binary-request@w3.org
[mailto:public-xml-binary-request@w3.org] On Behalf Of Bullard, Claude L
Sent: Tuesday, April 12, 2005 2:39 PM
To: 'Norman Walsh'
Cc: public-xml-binary@w3.org
Subject: RE: Comments on XBC Use Cases

Yes.  Same here.  I reprocessed ATOS SGML docs 
into HTML and XML in very short order in '95/96.  As a lifecycle 
enhancer, markup is quite effective (putting aside the 
problems of semantic associations to GIs).

Human to human communications, and communications that 
may require inspection to verify or validate benefit 
greatly from text representations. Cut and paste 
operations, debugging by hand, etc., are better 
in plain text. My experience is (from VRML), that 
one keeps the document in that format until satisfied, 
then compiles it/binarizes/zips.

I don't think of a binary as a replacement for XML. 
I think of it as an alternative encoding for those 
cases where performance or size do matter.

That is why X3D has three encodings, all with equivalent 
information properties, and each optimized for some 
quality the designers thought critical.  I fought 
the idea of three encodings, but so far, we don't 
have any evidence that they have created lifecycle 
problems (just implementation costs).  The problems 
that are evident are usually in the object model 
and the programming interface.  So one might ask 
if the binary introduces processor semantics problems, 
but I doubt that is the case.  It is a case for 
better performance trading on reuse and access.


From: Norman Walsh [mailto:Norman.Walsh@Sun.COM]

I think you're asking "how long does a document have to exist before it
becomes important to be able to read it independent of the systems that
originally produced it?"

| What about short lifecycle documents?
| Lifecycle is in the eye of the operator.  While the lifecycle
| property is a compelling property of XML, it is not of 
| necessity a constraining property of all of its applications 
| in time and space.  Forgetting is as important as remembering.

That's a good point. The long-term understandability of an ephemeral
message is irrelevant. Though there's nothing about understandability
that prevents one from forgetting :-)

To be a little more clear, I wasn't trying to assert that it be a
"constraining property of all of its applications" only that in the
"electronic document" use case, it was a property of very high
importance, in my opinion. That use case, as I understand it, is about
documents authored by humans for communicating information to other
humans. People tend to care about stuff for a long time. I have some 10
year old XML (uh, SGML) documents that I can read just fine and some 20
year old word processor documents that I fear are gone forever.
Received on Tuesday, 12 April 2005 20:22:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:42:01 UTC