• To: Jeff.Lowery@c... (Jeff Lowery)
• Subject: Re: RDF resources (was: many-to-many)
• From: John Cowan <jcowan@r...>
• Date: Mon, 27 Jan 2003 17:37:35 -0500 (EST)
• Cc: jcowan@r... ('John Cowan'), Jeff.Lowery@c... (Jeff Lowery), xml-dev@l...
• In-reply-to: <4827EC373E03DB44AC2AB3900430896B026585@w...> from "Jeff Lowery" at Jan 27, 2003 02:29:39 PM

Jeff Lowery scripsit:

> > The trick of using b-nodes is good in this respect: an RDF 
> > b-node represents
> > a non-retrievable (non-addressable) thing-in-the-world.
> 
> I'm not fluent on RDF,  but taking that statement at face value: is the
> existence of b-node an assertion of non-addressability, or just
> non-addressibility within a given context?

A b-node is an object you can make assertions about but that lacks a URI.
For example, I could have a b-node representing Simon St. Laurent, with
properties "hasMailbox", "isNamed", "withHomePage", etc. etc.  Much better
than identifying Simon with his mailbox, his name, or his home page.

-- 
John Cowan  jcowan@r...  www.reutershealth.com  www.ccil.org/~cowan
"It's the old, old story. Droid meets droid. Droid becomes chameleon.
Droid loses chameleon, chameleon becomes blob, droid gets blob back
again. It's a classic tale." (Kryten, Red Dwarf)

• References:
  • RDF resources (was: many-to-many)
    • From: Jeff Lowery <Jeff.Lowery@c...>

• Prev by Date: Re: many-to-many
• Next by Date: Re: many-to-many
• Previous by thread: RDF resources (was: many-to-many)
• Next by thread: Re: What is a "resource"? (Was: many-to-many)
• Index(es):
  • Date
  • Thread