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  May 2013

BIBFRAME May 2013

Subject:

DC & Application Profiles (was: BIBFRAME and Open Annotation Discussion)

From:

Karen Coyle <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Fri, 10 May 2013 08:49:46 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (61 lines)

(Cross-posted to BIBFRAME and Open Annotation lists... may require a 
look at respective list archives.)

The Dublin Core community has been working on a concept of Application 
Profiles (also sometimes called Community Profiles) that would seem to 
fit the BIBFRAME/Open Annotation use case.

An Application Profile (AP) is a way for a particular community to 
define their use of an ontology or a standard in the case where they may 
be using only a portion of the standard, or may be extending it. The AP 
cannot change the underlying standard or model, but it can narrow or 
expand its usage. It should therefore be entirely compatible with the 
underlying model.

The purpose of an AP is 3-fold:
1. It gives a community a view that makes sense for its use cases, and 
is therefore easier for its members to understand
2. It can be used by targeted systems (such as the library ILS's) to 
integrate the aspects of the standard that will be used in the 
community's data, without having to program for the entire standard if 
it isn't needed
3. The AP can be used to enforce constraints that are not part of 
RDF/OWL, or that would have a negative effect on the sharing of data in 
the open. An AP could define cardinality (repeatable, mandatory, etc.), 
and could constrain values (e.g. require controlled authority lists for 
certain statements). These constraints are not fully compatible with the 
open world assumption of the Semantic Web, but are often desired for 
quality control within a community at the points of creation and use.

A simple example of an AP in the library world would be a system 
designed for small libraries that uses only a portion of the RDA data 
elements. Another example would be a special library, like a film 
archive, that selects the elements it needs from RDA but extends them 
for its special needs.

Note that #3 above could be used by the Open Annotation community to 
implement constraints that are in its standard but that cannot be 
defined in RDF/OWL. This includes pretty much everything in that 
standard that uses terms like "MUST", "MUST NOT", "REQUIRED", "SHALL", 
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 
"OPTIONAL". It is precisely these types of constraints that the Dublin 
Core AP work hopes to address.

There is a proposal for an AP structure [1], but as yet not a fully 
formed machine-actionable version. The Dublin Core annual meeting in 
September, 2013 [2], will have working session on this concept [3], and 
we hope that we can get some consensus on how to make this concept into 
a usable, actionable standard. It would be wonderful to have folks there 
from the Open Annotation community to join in this discussion.

[1] http://dublincore.org/documents/dc-dsp/
[2] http://dcevents.dublincore.org/index.php/IntConf/dc-2013
[3] http://dcevents.dublincore.org/IntConf/index/pages/view/APaltOO

-- 
Karen Coyle
[log in to unmask] http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet

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

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