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


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] Partyin' like it's 1999

[ Lists Home | Date Index | Thread Index ]

> -----Original Message-----
> From: Eric Hanson [mailto:elh@cs.pdx.edu] 
> Sent: Thursday, October 28, 2004 5:02 PM
> To: Bullard, Claude L (Len)
> Cc: 'Michael Champion'; xml-dev@lists.xml.org
> Subject: Re: [xml-dev] Partyin' like it's 1999
> Bullard, Claude L (Len) (len.bullard@intergraph.com) wrote:
> > A radical suggestion:  maybe what they really need are binaries and 
> > the creation of a binary specification can provide a subset 
> of what is 
> > expressible in XML.  They aren't the same, just that it might be 
> > easier to create a subset outside XML The Spec.  My 
> intuition is that 
> > the shock would come from elsewhere, such as new chip design or the 
> > sudden emergence of reliable telepathy.
> > (Why yes, the siddhi are real; they just aren't reliable, Sherman.)
> > Of the cases presented, isn't the really gnarly one namespaces? 
> > In other words, if the edges of that were tidied, how much 
> pain would 
> > go away?
> > 
> > Ok.  Any parties interested in posting their favorite five bad 
> > problems with XML in order here?  I wonder what the consensus is on 
> > the top two.  (XML, not XML apps like
> > XSD.)
> 1. There is no way to look up, discover and retrieve the 
> library of resources that support with a namespace-qualified element.
> If you come across a piece of data, there may be hundreds of 
> supporting resources like XSL transformations, schemas, 
> xforms, text documentation, etc.  We need a way to link the 
> resources to the data.  This is the biggest problem with XML 
> today.  

Some of this capability already exists natively in the OASIS/ebXML
Registry standard, and some is being implemented in the future through a
Technical Note (that I am working on) within the OASIS/ebXML Registry
Technical Committee that describes a standard mechanism for registering
fine-grained artifacts such as elements, attributes, data types, and
namespace identifiers, and associating these fine-grained artifacts with
other fine- and course-grained artifacts accordingly. There is a very
high degree of interest in this capability within the US federal
government space.

Kind Regards,
Joseph Chiusano
Booz Allen Hamilton
Strategy and Technology Consultants to the World

> XML is this great universal data format, great, but 
> until it has a cooresponding supporting resource discovery 
> mechanism, we lose half the power of using a universal 
> language in the first place.
> This is hardly a new idea, but IMHO a greatly neglected one.  
> It was proposed by Tim Bray and the XML packaging group back 
> in 1999, the related resource packaging part anyway, but the 
> group was closed due to lack of interest.
> http://www.textuality.com/xml/why-pkg.html
> http://www.w3.org/XML/2000/07/xml-packaging-charter
> 2-5. I can't even think about any other XML problems until 
> this exists.  It's so fundamental and obvious it blows my 
> mind that it doesn't.
> Eric
> -----------------------------------------------------------------
> 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://www.oasis-open.org/mlmanage/index.php>


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

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