Re: RDF resources (was: many-to-many)
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)
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format