LISTSERV mailing list manager LISTSERV 16.0

Help for ID Archives


ID Archives

ID Archives


[email protected]


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

ID Home

ID Home

ID  May 2010

ID May 2010

Subject:

Re: skos:Concept AND rdf:Property : what is the rationale?

From:

"Summers, Ed" <[log in to unmask]>

Reply-To:

Authorities and Vocabularies Service Discussion List <[log in to unmask]>

Date:

Sat, 29 May 2010 11:28:29 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (53 lines)

Personally, I'm not a fan of the relators being defined as both skos:Concept and as rdf:Property. I believe that this was done to accommodate earlier use of MARC Relators as refinements of dc:contributor [1], and the desire to express them as skos:Concept. I'm not exactly sure what the advantage of having them as skos:Concept. So I'd like to see some examples of how it is supposed to be used as well. I'm also not directly involved in the project anymore, so I imagine someone from the Network Development and MARC Standards Office might have more information.

//Ed

[1] http://dublincore.org/usage/documents/relators/

________________________________________
From: Authorities and Vocabularies Service Discussion List [[log in to unmask]] On Behalf Of Bernard Vatant [[log in to unmask]]
Sent: Thursday, May 27, 2010 6:32 AM
To: Summers, Ed; [log in to unmask]
Subject: skos:Concept AND rdf:Property : what is the rationale?

Hi all

I've suscribed to this list following a today exchange on Twitter between
Gautier Poupeau and Ed Summers regarding the new vocabularies published at
id.loc.gov, and in particular at http://id.loc.gov/vocabulary/relators,
where all "relators" are defined both as instances of skos:Concept and
rdf:Property.

I understand the idea behind this.
Any relator (aka "role") is by nature ambiguous in natural language.

"Composer" can be viewed as a class ...

<http://dbpedia.org/page/Wolfgang_Amadeus_Mozart> rdf:type  "composer"

(Mozart is a Composer)

.. or as a property ...

http://dbpedia.org/page/Don_Giovanni "composer"
<http://dbpedia.org/page/Wolfgang_Amadeus_Mozart> ...

or as a Concept

<http://opera.stanford.edu/composers/> dc:subject "composers".

It is considered good practice for a semantic web vocabulary when it comes
to representing such ambiguous concepts, to make a choice, based on the
functional target of the vocabulary, in order to avoid driving logical tools
(and human ontologists) crazy, and to control the functional use of the
concept (classifying things, declaring relationships, or indexing resources).
But another (supportable IMO) viewpoint could be to declare ambiguity in the
vocabulary, and let the applications sort the ambiguity out. Seems that this
is the option taken by the relators vocabulary.

Since people have frowned at this, could soemeone (Ed, I guess) explain the
rationale, and maybe document examples of use of a relator as a skos:Concept
and as a rdf:Property.

Bernard

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 2024
January 2024
March 2023
January 2023
July 2022
June 2022
May 2022
April 2022
February 2022
November 2021
September 2021
August 2021
July 2021
June 2021
May 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
March 2020
February 2020
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
April 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2017
July 2016
February 2016
January 2016
December 2015
November 2015
September 2015
August 2015
June 2015
March 2015
February 2015
October 2014
August 2014
July 2014
June 2014
March 2014
January 2014
November 2013
September 2013
August 2013
June 2013
May 2013
April 2013
March 2013
December 2012
November 2012
October 2012
September 2012
August 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
April 2011
March 2011
February 2011
January 2011
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
November 2009
June 2009
May 2009

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager