[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: interop, not standards
- From: "Bullard, Claude L (Len)" <email@example.com>
- To: "Simon St.Laurent" <firstname.lastname@example.org>, email@example.com
- Date: Thu, 15 Mar 2001 16:24:12 -0600
Nothing to disagree with in the article. Note:
"But whatever the difficulties in finding a suitable place or places to have
these conversations, now is the time for it. The industry is too young for
standards, but old enough for interoperability. So don't think about
standards yet, but whatever else you think about, think about
He gives a list of people he thinks are worth talking too
and places where they talk. So, he chose a means for you
to choose the means and said what any good standards committee
member can tell you: spec until you have enough experience
to standardize. That interoperation agreement is a spec.
Bray says some enlightening things in his Taxi article
about what it means to create a DTD.
Build simple bridges to allies and defend them.
I don't think a single standards vet will argue with
the common sense in that one. Standards aren't the problem.
Rick said it: the issue is the PSVI
and its relationship to the new specs.
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
From: Simon St.Laurent [mailto:firstname.lastname@example.org]
Sent: Thursday, March 15, 2001 2:56 PM
Subject: interop, not standards
Here's an interesting piece:
Starts from the premise:
"Whatever else you think about, think about interoperability. Don't think
about standards yet."
Not specifically about XML, but about the same landscape.
Simon St.Laurent - Associate Editor, O'Reilly and Associates
XML Elements of Style / XML: A Primer, 2nd Ed.
XHTML: Migrating Toward XML
http://www.simonstl.com - XML essays and books
The xml-dev list is sponsored by XML.org, an initiative of OASIS
The list archives are at http://lists.xml.org/archives/xml-dev/
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: email@example.com