LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


BIBFRAME@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  September 2015

BIBFRAME September 2015

Subject:

Re: BIBFRAME Identifier, Role, and Authority Proposals

From:

Steven Folsom <[log in to unmask]>

Reply-To:

Bibliographic Framework Transition Initiative Forum <[log in to unmask]>

Date:

Wed, 9 Sep 2015 03:01:31 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Jeff,

Thanks for the response (and all that OCLC has done to progress the linked data agenda in the library community). I didn’t mean to call anyone out.

I agree the RWO/authority conversation is difficult, perhaps the hardest thing to wrap heads around when we’re so used to talking/modeling in terms of authorities… especially now that RDA allows us to say more explicitly about the RWO. I’m happy that OCLC uses separate URIs for the different entity types, but it seems like a big concession not to maintain consistent semantics. [An aside, everyone should read Jean Godby, Shenghui Wang, and Jeff Mixter’s book on linked data. It has the most accessible description of how authorities and RWOs differ.]

One of the motivations for migrating to linked data/RDF is to benefit from the formal logic that RDFS and OWL provide; we want to benefit from inferred data. The sameAs assertion between a person and authority means if we run reasoning over our data we’re going to end up with triples like:

<Some person> madsrdf:editorialNote "Non-Latin script references not evaluated.” .

(I’m sure someone can come up with more awkward examples; that’s not a challenge. :)

LOC has blank nodes for RWOs see: http://id.loc.gov/authorities/names/n94112934.rdf. They are even typed appropriately with FOAF persons, organizations, etc. now!!! It would be great if VIAF authorities could have reciprocating relationships with LC authorities, and VIAF RWOs could have reciprocating relationships with LOC RWOs.



Thanks,
Steven

————
Steven Folsom
Metadata Strategist and Standards Advocate
Cornell University Library







On 9/8/15, 2:06 PM, "Bibliographic Framework Transition Initiative Forum on behalf of Young,Jeff (OR)" <[log in to unmask] on behalf of [log in to unmask]> wrote:

>Picking up a thread from a couple of weeks ago...
>
>On Aug 26, 2015, at 11:44 AM, Steven Folsom wrote:
>> I noticed throughout this thread
>> (and in the VIAF data) authority URIs being used as the objects of 
>> properties where instead person, places, etc. URIs should be. For 
>> example, (as previously
>> mentioned) VIAF has separate URIs 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.
>
>Here's a rationalization of VIAF's RDF treatment of *real-world entity* vs. *authority* ("sameAs" vs. "focus" vs. "identifiedBy", etc.)
>
>- The VIAF URI (e.g. http://viaf.org/viaf/36997809) identifies the *real-world entity*
>	- To maximize cross-domain interoperability, VIAF uses Schema.org vocabulary as much as possible to describe the entity. 
>		- E.g. http://bit.ly/1NKEvOa
>		- These VIAF entities are not dependent on preconceptions of "authority".
>	- VIAF entities use schema:sameAs rather than owl:sameAs/madsrdf:isIdentifiedBy to avoid splitting the entity/authority hair when linking to external URIs.
>		- The use of schema:sameAs "tends to blur distinctions which are important to OWL users, such as URIs for entities versus the pages that describe them". In VIAF's case, the blurring effect is between *entity* vs. *authority*. This blurring is intentional because most consumers of VIAF entities won't understand or care about the difference.
>			- http://www.w3.org/wiki/WebSchemas/sameAs
>		- For use cases that *do* understand and care about the entity/authority difference, VIAF uses foaf:focus instead of schema:sameAs in the reverse direction.
>			- E.g. http://bit.ly/1LInbWN
>			- Unlike the VIAF *entities*, which use Schema.org vocabulary to maximize cross-domain interoperability, these *authorities* are mainly described using SKOS.
>
>Hopefully this outline clarifies some of the details behind VIAF's RDF. If not, I can try to elaborate.
>
>Jeff

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
July 2011
June 2011

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager