Print

Print


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

Am 26.08.2015 um 17:44 schrieb Steven Folsom:

> throughout this thread (and in the VIAF data) authority URIs being use
d
> as the objects of properties where instead person, places, etc. URIs
> should be. For example, (as previously mentioned) VIAF has separate UR
Is
> for the person and the authority, but then they go on to make a sameAs
> assertion between the VIAF *person* and an id.loc.gov *authority*. I
> hope this is just a mistake, and that they would be open to making the
> sameAs assertion between the VIAF foaf:Document and the id.loc.gov
> authority.

But VIAF uses schema:sameAs
"URL of a reference Web page that unambiguously indicates the item's
identity."

which is quite different from owl:sameAs.


> For example: https://viaf.org/viaf/36997809/rdf.xml has a URI for
> the document ("http://viaf.org/viaf/36997809/“) and another for Carl S
agan
> himself ("http://viaf.org/viaf/36997809”, without the trailing slash).

In the example I see schema:sameAs properties only attached to the
concept URI. E.g. the following document should be (tried to) retrieved
for identifying information:

http://id.loc.gov/authorities/names/n79064998

(and we have to retrieve that document in search for an LC identifier,
since the RDF representation of the VIAF cluster does not provide one).

I don't see any place where VIAF declares identity of different concept
URIs (as opposed to the GND behavior where it is stated

<http://d-nb.info/gnd/115873937>
          owl:sameAs <http://viaf.org/viaf/36997809>)


> The Person URI has sameAs assertions with both authorities and entitie
s
> modeled as persons.

can you elaborate on this? I'm not sure if VIAF contributors already
have a stringent (and stable) distinction between information resources
("authorities"?) and concept URIs (RWOs?). And use of schema:sameAs
somehow enforces the interpretation as information resouce URI even if
they smell of concept URIs as in the case of
http://data.bnf.fr/ark:/12148/cb12375841d#foaf:Person

So for an entity VIAF reports a number of *documents* which each
claym to (sufficiently) identify the entity in question. I'd consider
that a very careful approach, especially VIAF is in no position
to boldly declare identity of the concepts contributed by different
sources into one cluster.


Then, VIAF kind of declares its resolving functionality:

<http://viaf.org/viaf/sourceID/LC%7Cn++79064998#skos:Concept> [
 a <http://www.w3.org/2004/02/skos/core#Concept"> ;
 skos:inScheme <http://viaf.org/authorityScheme/LC> ;
 skos:prefLabel "Sagan, Carl, 1934-1996" ;
 foaf:focus <http://viaf.org/viaf/36997809"> ].

I interpret that as a "hook": Feel free to identify the LCAuth
concept URI of your choice with
http://viaf.org/viaf/sourceID/LC%7Cn++79064998#skos:Concept
and the graph above then serves the connection between "your" concept
and the RWO identified by the VIAF URI.



viele Gruesse
Thomas Berger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iJwEAQECAAYFAlXd7ecACgkQYhMlmJ6W47PmsgP9GCrSH5wugyK5RiJGNnd/nzby
8CEOKUARK48FFibgJLqtZPTu8jpJnq2FyV6BMcdCRwwEkbXsYE6dNUqpVfWe9ly4
WtdyvO89OITJLvJ+bgXYjdUan7W6j4rKhTg2nPw/aIxf+ZqToAIx++L8u3xZNfpz
/fraKaxUX6aNBJzicQM=
=oBUD
-----END PGP SIGNATURE-----