W3C home > Mailing lists > Public > www-rdf-interest@w3.org > March 2001

Re: Again: Anonymous Resources

From: Seth Russell <seth@robustai.net>
Date: Mon, 12 Mar 2001 09:33:46 -0800
Message-ID: <007701c0ab1a$98d26ac0$b17ba8c0@c1457248a.sttls1.wa.home.com>
To: <www-rdf-interest@w3.org>, "Lee Jonas \(by way of \"Ralph R. Swick\" <swick@w3.org>\)" <ljonas@acm.org>
From: "Lee Jonas (by way of "Ralph R. Swick" <swick@w3.org>)"

> Although this can also be viewed at a superficial level as *naming*
> anonymous resources, it can more acurately be viewed as bootstrapping XML,
> N3, SemEnglish, etc. into more abstract RDF model constructs (e.g.
> of Java classes) that are not associated with a particular URI-reference.
> Again IMHO, serialisation is only of interest to RDF parser developers,
> RDF application developers.  RDF applications can fully utilise anonymous
> resources as intended in the current RDF spec, and parsers are free to use
> far simpler identifier generation schemes, as these ids don't have to be
> reproducable by them (or any other parser) in a globally unique fashion.

I'm glad to hear implementors finally saying this ... imho it cannot be said
enough .. let me hang some of my own words and terms on that concept.  RDF
applications that store knowledge (triples/quadrapules) in internal memory
(db) need some internal identification for each node (set of statements with
the same subject) for the purposes of implementing vance (see below)... my
sem (semantic memory) application will just use serial numbers.  I doubt
that any implementors will find  URIs themselves to be practical for
internal identification of nodes.  So that the URIs that come from the
outside world via RDF will probably just be stored as a property like any
other property of the node ... for example:

    uri http://robustai.net/People/#Seth ;
    email mailto:seth@robustai.net ;
    label "Seth" ;
    (is developing) SEM;
    (is soliciting collaboraton on) SEM.
    label "SEM" ;
    acronymOf "SEmantic Memory".
    label "is developing".
    label "is soliciting collaboraton on".
    label "vance";
    description "to follow a reference to that which is referenced - ie
    a Method.

So that whether an internal node has a uri property on it or not, is fairly

Received on Monday, 12 March 2001 12:36:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:29 UTC