OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: Nesting XML based languages and scripting languages

[ Lists Home | Date Index | Thread Index ]
  • From: "Frank Boumphrey" <bckman@ix.netcom.com>
  • To: "Tim Bray" <tbray@textuality.com>, <xml-dev@ic.ac.uk>
  • Date: Fri, 24 Apr 1998 02:03:55 -0700

>Hmm; bear in mind that XSL is a year away, probably, from being a W3C
>Recommendation.  Thus anybody who charges into implementation of a moving
>target is incurring some risk as well as potential benefit<<


What about us poor authors!! We have to write "knowledgeably" about a
subject that doesn't even exist. Our books usually appear at about the same
time as a spec which invalidates every thing we have written!!

Frank

-----Original Message-----
From: Tim Bray <tbray@textuality.com>
To: xml-dev@ic.ac.uk <xml-dev@ic.ac.uk>
Date: Thursday, April 23, 1998 6:38 PM
Subject: Re: Nesting XML based languages and scripting languages


>At 05:50 PM 4/23/98 -0700, Don Park wrote:
>>However, I have heard through the grapevine that there is a lot of XSL
>>development activities at Microsoft with at least one project close to
>>completion.
>
>Hmm; bear in mind that XSL is a year away, probably, from being a W3C
>Recommendation.  Thus anybody who charges into implementation of a moving
>target is incurring some risk as well as potential benefit; at least one
>early-XML-adopter is right now feeling the pain of retrofitting case-
>sensitivity into running code with an installed base.
>
>Having said that, it's good that people charge ahead with implementation
>of pre-release specs because it tends to reveal problems that you just
>don't notice until you implement.  And having said *that*, I think that
>anyone who implements a business-critical application based on an
>unfinished, unratified spec has shitferbrains.
>
>There have certainly been instances, inside W3C committees, where vendors
>have argued against changes on the grounds that they'd already implemented
>things; so far, such objections have generally failed to carry the day.
>
>On which subject, check out the "Status of this Document" language
>in the namespace working draft, elegantly authored by Ralph Swick and
>Ora Lassila for the RDF activity, and stolen by me for namespaces.
>
>Bottom line: yes, there are advantages to being inside the process,
>but early implementation is a two-edged sword. -T.
>
>
>xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
>Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
>To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
>(un)subscribe xml-dev
>To subscribe to the digests, mailto:majordomo@ic.ac.uk the following
message;
>subscribe xml-dev-digest
>List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
>
>


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS