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  January 2015

BIBFRAME January 2015

Subject:

Re: What will things and strings look like?

From:

Ed Jones <[log in to unmask]>

Reply-To:

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

Date:

Wed, 21 Jan 2015 16:35:33 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (57 lines)

One workaround for names (in many, if not most cases) would be (1) to use ISNIs in those cases where a name authority record does not exist for an author and (2) to make sure that newly created name authority records routinely include ISNIs. Especially in the realm of scholarly information, it is much more likely that an ISNI will exist for an author (because he/she is recorded, for example, in Scholar Universe as the author of an article). All ISNIs have persistent URIs in the form http://isni.org/isni/[isni]. While ISNI records may include minimal identifying information, they will typically include links to sources (like Scholar Information) with sufficient information to identify the individual.

There are drawbacks, of course--more than on ISNI record may have been created for a person, and ISNI identities don't always correspond to RDA persons, etc.--but I think the advantages far outweigh the disadvantages in terms of linking data.

ISNIs can be searched at http://www.isni.org/search

Ed Jones
National University (San Diego, Calif.) 

-----Original Message-----
From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Karen Coyle
Sent: Wednesday, January 21, 2015 8:00 AM
To: [log in to unmask]
Subject: Re: [BIBFRAME] What will things and strings look like?

That is "kind of" true although there are workarounds, some of which are already used in BIBFRAME - create a blank node that can have a URI and/or a label.

You can also mix things and strings in OWL, using something called an annotation property, but what you end up with is something that is not very usable.

This type of restriction isn't actually new, it just takes a different form. For example, if you have a date field, in most programming languages it needs to be either a structured string (yyyy-mm-dd) or a free text field, but if you mix those you cannot take advantage of the structured dates in applications. Things and strings are pretty much the same - strings aren't "application friendly".

I agree with Kelley and others that we will need a way to punt on nearly every place in our data where a URI would be desirable. The perfect world where a drop-down provides the "fill-in" precisely when you need it does not exist. It would be great to hear from anyone developing BIBFRAME input flows on how they are handling this.

kc


On 1/20/15 10:07 PM, Shlomo Sanders wrote:
> I agree.
> But, as far as I understand, Either a value in a triple is a "string" or it is a URI, and  never the 2 shall mix.
>
> Thanks,
> Shlomo
>
> Sent from my iPad
>
>> On Jan 20, 2015, at 19:31, Bowers, Kate A. <[log in to unmask]> wrote:
>>
>> One of the problems with making all relationships "URI" is that this is hugely time-consuming. Keying "Ken Smith, producer; Joe Jones, director; Emily Simms, presenter" is easy.  Finding a record for "Ken Smith" if one doesn't already exist?  Impossible level of work.  We need to be able to say things in strings because we cannot possibly make all the metadata into data.  Only for "traced" headings would this be possible, and we don't typically trace these all these pieces of data.
>>
>> Kate
>>
>> Kate Bowers
>> Collections Services Archivist for Metadata, Systems, and Standards 
>> Harvard University Archives [log in to unmask]
>> 617.496.2713
>> voice: (617) 384-7787
>> fax: (617) 495-8011
>> web: http://nrs.harvard.edu/urn-3:hul.eresource:archives
>> Twitter: @k8_bowers
>>

--
Karen Coyle
[log in to unmask] http://kcoyle.net
m: +1-510-435-8234
skype: kcoylenet/+1-510-984-3600

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

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