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

RE: Meta-somethingorother (was the semantic web mega-permathre

  • To: <martind@n...>,"Dare Obasanjo" <dareo@m...>,"Michael Champion" <mc@x...>,"XML Developers List" <xml-dev@l...>
  • Subject: RE: Meta-somethingorother (was the semantic web mega-permathread thing)
  • From: "Joshua Allen" <joshuaa@m...>
  • Date: Wed, 9 Jun 2004 11:26:24 -0700
  • Thread-index: AcRORe1UkIeGp9Q8Sgm84j3Lx91XEwAB2ZxQ
  • Thread-topic: Meta-somethingorother (was the semantic web mega-permathread thing)

RE:  Meta-somethingorother (was the semantic web mega-permathre
> > doesn't bother me, but if people get so sidetracked than maybe it's
the
> > fault of imprecise language.
> 
> Yes this is precisely the problem, when we talk about the RDF
framework
> (let's get explicit here) we are facing two cases:

> a) RDF is used to add some meta-data to some existing data (also
called a
> resource). The data may not necessarily be accessible thought an HTTP
GET

It's even worse than this.  I don't think anyone *ever* uses RDF to "add
meta-data to some existing data (also called a resource)".  It just
can't work this way.  The data and the resource are separate, and you
*always* talk about the resource in RDF, and *not* about the data.

They really are completely separate.

The result of doing an HTTP GET is emphatically *not* "the resource".
If anything, the result of doing an HTTP GET is some data *about* the
resource.  It is a representation of the resource; just like a painting
or photograph could be a representation of you.  (This is the whole
point of the REST religion, BTW).

So the "data" that you get from an HTTP GET is not really conceptually
different from the other "metadata about a URL" that we might talk
about.  If you wrote it in triples, you could conceptualize that:

s: http://www.netcrucible.com/blog
p: dc:Author
o: allenjs@h...

s: http://www.netcrucible.com/blog
p: ns:representation
o: <html><head><title>Better L....

Note that you might even want to use different representation predicates
for different user agents, and so on.  Obviously in practice nobody
shares resource representations this way, since we have HTTP and it
works fine.  But the point is that *architecturally* and *conceptually*,
the result of HTTP GET is just as much "about" the resource as any other
RDF statement.



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.