W3C home > Mailing lists > Public > www-rdf-interest@w3.org > July 2004

Re: InverseFunctional properties are the new URI?

From: Damian Steer <damste@hplb.hpl.hp.com>
Date: Fri, 30 Jul 2004 11:35:02 +0100
Message-ID: <410A2456.7030500@hplb.hpl.hp.com>
To: Dan Brickley <danbri@w3.org>
Cc: Sandro Hawke <sandro@w3.org>, www-rdf-interest@w3.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dan Brickley wrote:

| * Damian Steer <damste@hplb.hpl.hp.com> [2004-07-30 10:26+0100]
|

| Sandro Hawke wrote: |>Actually, I think I'll disagree with myself
| before anyone else does. |>Taking Dan's point, the ordering could
| well be IFP > no URI/IFP > URI |>because the URI is in no way a
| property of the described object whereas |>all other properties
| are. | | | Why isn't something's URI an IFP property of the thing?
| TimBL calls | that property log:uri, I think.   For a while, I
| generalized it | slightly to u:uname [1]. | |      -- sandro | |
| [1] http://www.w3.org/2001/12/uname/
|
| Hmm. Why not use rdf:resource and rdf:about (being samePropertyAs)?
|
|
| Backwards compatible, and parsers will just need to de-bless those
| attributes. For example:
|
| <rdf:Description newrdf:about="http://ex.com/1"> ~  <a:prop
| newrdf:resource="http://ex.com/2"/>
|
|
|> If newrdf:resource is unblessed, ie. 'just a property' this is
|> same as
|
|> <a:prop> <rdf:Description>
|> <newrdf:resource>http://ex.com/2</newrdf:resource>
|> </rdf:Description> </a:prop>
|
|> ...which isn't quite what you want, I think.

Sorry, just to be clear this was wrt Sandro's uname, where the object
is a literal. I guess (though I'm not sure) that Sandro would have
just literals and bnodes -- is that right? -- so I suggest calling it
"the revenge of OWL full". It also reminds me of a discussion on
#rdfig about the statement <uri> dc:identifier "uri"^^xsd:anyURI .

You could also semi-bless, as in rdf:type.

| You'd also run into
|> back-compatibility problems since properties can repeat, while
| rdf:about
|> can't. Also if rdf:resource is a property, it would appear in a
|> different syntactic role, ie. as an element. And rdf:about could
|> appear there too. Thinking about it, it'd be total chaos :)

Free your western mind and embrace the chaos, Dan :-)

Actually I meant forwards compatible (stupid brain). All existing data
would be fine.

I'm embracing this new world as we speak. Changing all those rdf ns
decls to point elsewhere leaves rapper (alarmingly) unconcerned (arp
is more tetchy - rdf:RDF causes an issue). Suddenly my rdf is entirely
bnodes and literals :-) Add in the ifp bits and it's complete. Who's
with me?

(Apologies for thunderbird's idiot quoting)

Damian

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBCiRVAyLCB+mTtykRAlj1AKDXwjCMm09n53bxo03sNrBYJ2yvlACePii2
vJ55gK4tgsrsVpoVjLJHVn8=
=2ube
-----END PGP SIGNATURE-----
Received on Friday, 30 July 2004 06:44:54 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:14:58 UTC