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

RE: After XQuery, are we done?

  • To: "DuCharme, Bob (LNG-CHO)" <bob.ducharme@l...>,"Ben Trafford" <ben@p...>, <xml-dev@l...>
  • Subject: RE: After XQuery, are we done?
  • From: "Hunsberger, Peter" <Peter.Hunsberger@S...>
  • Date: Fri, 22 Oct 2004 13:32:21 -0500
  • Thread-index: AcS4XfPfa65DNHkLTQC0uD7A8btElAABEbog
  • Thread-topic: After XQuery, are we done?

RE:  After XQuery
DuCharme, Bob (LNG-CHO) <bob.ducharme@l...> writes:
> 
> The more general concept of linking, which is the 
> representation of a specific relationship (often, a typed 
> relationship e.g. weblog entry X 
> praises/criticizes/misrepresents weblog entry Z) can be 
> modeled well enough with RDF. No existing syntax to represent 
> the RDF model is getting great traction. Among the efforts to 
> come up with new syntaxes, the RDF-in-XHTML project is 
> working with some ideas that can do much of the job of 
> expressing resource relationships without scaring too many 
> people off, which I find encouraging. They're mostly thinking 
> in terms of metadata for now, e.g. how to represent 
> statements like "1. this web page has a rights profile 
> described at this Creative Commons web page, 2. this page was 
> authored by that person, 3. that person has a home page at 
> http://whatever." If someone wants to write a stylesheet 
> that loads these facts into a database, or turns them into 
> a/@href links or javascript popups, and it serves the needs 
> of their users, great. 
>
> I've felt for a while that linking is about expressing relationships 
> and attaching metadata to those expressions, and RDF is good for that.

> What a developer does with those expressions, like what the developer 
> does with <title/> and <xref/> elements, is up to his or her
imagination 
> and familiarity with the options available in the output device at
hand.

Why you need RDF?  What does it give you that plain old XML doesn't give
you in this case? An OWL link-base so that you can do off-line
relationship management perhaps? But then the problem becomes
addressing/labeling/identifiers and mapping to this link-base?  

Let me put this another way: if what's being asked for is the management
of relationships between domains then the real problem is agreeing upon
common identifiers between those domains.  Once you've got that I don't
see that it matters whether you put those identifiers in RDF or plain
old XML.  I see the value for RDF for relationship management, I don't
think I need RDF for exposing the relationships to the outside world
(but I could probably be convinced otherwise)...



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.