Re: A certain difficulty: E-Commerce & RDF

Hi,

considering the two postings from David and Mark (partially cited below)
the real challenge for RDF appears to be to get used in e-commerce for
exchanging information.
However, there are efforts to establish standards going on in e-commerce,
most notably

http://www.ebxml.org/

A quote from the web-page:
<quote>
Our Mission
To provide an open XML-based infrastructure enabling the global use of
electronic business information in an interoperable, secure and consistent
manner by all parties.
</quote>

A United Nations sub-organization and OASIS seem to be involved in this,
together with a pretty impressive list of other companies.

Could anybody involved in this project comment on the relationship to RDF?
Since they are aiming at similar goals than RDF, they have to face the
same questions.
If nobody from this project is on the mailing list:
does it make sense to contact the responsible persons of ebXML ?

Ciao,
         Stefan


At 11:31 AM 2/27/00 -0800, Mark wrote:
[Text deleted]

>However, a world wide standard that allowed sharing from existing data
>stores could work. Especially in the current digital economy. It made sense
>to me that RDF was the next logical step in creating this world wide
>information data warehouse. RDF is essential to get greater value out of the
>world wide web data resource.
>
>My suggestion is that you ASK THE USER before rewritting it or killing it.
>
>For example, an ecommerce site might ask for a common way to share catalog
>information.
[Text deleted]

 >David Magginson wrote in
http://lists.w3.org/Archives/Public/www-rdf-interest/2000Feb/0092.html
[Text deleted]
 >There's a lot of money in this [exchange of serialized objects 
independent of >protocols or programming language (added by SDe)]
 >]: e-commerce requires much richer data nowadays, and retailers want that 
data >to flow from wholesalers and wholesalers want that data to flow from 
producers. >If you take a look at data-exchange right now (tab-delimited 
dumps, product->specific tables, etc.) it's a bit of a bad joke. Writing 
specific XML formats >for each exchange task is a small improvement, but 
you miss out on the network >effect of being able to share 90% of the 
processing software, because the XML >data model is too low-level.
[Text deleted]

Received on Sunday, 27 February 2000 15:35:04 UTC