[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: In Search of XML Interoperability: XLink + XML Schema =Interoperabil

  • From: David Wang <dwang@m...>
  • To: Jean Marc VANEL <jean-marc_vanel@e...>
  • Date: Thu, 17 Feb 2000 15:41:08 -0500

xml interoperability

> In this search for Interoperability, I want to advocate for another way of linking things than Xlink: it's RDF.
> 
> What is RDF's advantage compared to Xlink ?
> 
> Instead of inventing new xlink attributes, e.g. this had been suggested:
> 
> isA | hasA | equiv | isLike | partOf
> 
> RDF allows to link two resources WITH ANY DOMAIN-DEFINED SEMANTICS.
> I'll give examples, and list afterwards the architectural implications.

I think RDF certainly is generic and powerful enough for this purpose
since it essentially is an agreement on how to describe some resource. 
RDF says nothing about what we are actually describing; that is
completely up to the domains to figure out.

So, extending your line of thinking even further, basically any
"language extension/proposal" than wants to describe a property of any
given resource (be the property something like relation-to, linked-to,
encoded-in, etc) can be recast in RDF.  I agree.  Your four examples are
excellent illustrations (well, the first two were more concrete; latter
two were more hand-waving. ;-) ).

In that case, one can probably argue that XLink is simply a particular
instance of RDF, so why bother progressing on XLink or any other
language/extension/proposal that describes some attribute of a resource.

In fact, this point has been acknowledged in the XLink Working Draft at
http://www.w3.org/TR/xlink/#rdf-examples .  They admit it!  XLink can be
written in RDF!

So, I think that it's true that XLink can be recast into RDF.  But that
does not make the problem XLink is trying to solve any easier.  Ok, so
XLink is syntactic sugar for RDFs, but there is real value in defining
and figuring out how to relate and link resources.  And syntactic sugar
is not necessarily bad. :-)  It certainly helps to focus the problem up
front.  You'd agree that having all the power of RDF without a
well-defined way of wielding it can be sorta... dangerous, not to
mention less than useful.

/David


***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/threads.html
***************************************************************************

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.