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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  July 2014

BIBFRAME July 2014

Subject:

Re: Bibframe and Linked Data (Authorities)

From:

Stuart Yeates <[log in to unmask]>

Reply-To:

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

Date:

Fri, 11 Jul 2014 08:32:29 +1200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (81 lines)

In the spirit of expanding this example,
https://www.wikidata.org/wiki/Q5597 is the wikidata URI for
http://viaf.org/viaf/64055977/

As well as all sort of wikimedia-specific information (such as links to
encyclopedia articles in many languages, links to wikisource digital
copies of textual works by and about them and their name translated into
many languages), it contains asserts such as: their VIAF identifier
(plus many other identifiers), sex, dates of birth and death, places of
birth and death, occupations, etc. etc.

As a person implementing an RDF system, I'm not going to look at every
assertion and decide whether or not to import it into my core system,
I'm going to look at wide classes of assertions.

I might decide that the wikidata definition of sex is not one I'm happy
with and exclude that, for all people.

I might decide that I don't care about wikisource digital copies (which
are reachable via wikipedia anyway) and exclude those for all people.

I might decide that I only care about locally-relevant languages plus
the standard UN set, and exclude all the other labels.

I'm definitely going to decide that I'm going to exclude unattributed
notes that someone smelled badly.

This is conceptually no different to importing a large batch of MARC
records and looking at the various note and private fields and deciding
which to include and which to exclude.

cheers
stuart


On 07/11/2014 06:30 AM, Ford, Kevin wrote:
> Dear Karen,
>
> The complexity arises if someone other than OCLC (?) asserts something
> about a VIAF URI.
>
> So, for example (and, please note, I’ve used a different URI, because,
> well, the one your provided is problematic for my purpose here), what if
> /I/ asserted:
>
> http://viaf.org/viaf/64055977/ skos:note “He smelled very badly, all the
> time.”
>
> On the surface it looks like VIAF/OCLC said Raphael smelled badly, all
> the time because, provenance-wise, the domain tracks back to OCLC. In
> reality, I said it, but you cannot tell.
>
> If we use global URIs, and additional statements are made against those,
> then something like this could happen.
>
> Yours,
>
> Kevin
>
> *From:*Bibliographic Framework Transition Initiative Forum
> [mailto:[log in to unmask]] *On Behalf Of *Smith-Yoshimura,Karen
> *Sent:* Thursday, July 10, 2014 1:40 PM
> *To:* [log in to unmask]
> *Subject:* Re: [BIBFRAME] Bibframe and Linked Data (Authorities)
>
> Kevin –
>
> Re:
>
> >There's been lots of talk about provenance and the like in a global
> graph of data, but I feel most of those discussions rely on fairly
> technical mechanisms, the complexity of >which outweigh the simplicity
> of minting one's own URI. (Also, the provenance statements will need
> their own URIs!)
>
> Doesn’t http://viaf.org/viaf/54202464 show the provenance is VIAF?
> What’s complex about this?
>
> Karen S-Y
>

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

September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
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