I am describing media elements and I don't know whether to use skos:subject or dc:subject to describe a topic of a media item. I want to use a class in the range of the relation to be able to find media items of the same topic and to describe the topic. I read that skos:subject is deprecated, and dc:subjct has a text field as range (right?). Could I still use dc:subject or there is any other vocabulary to describe this? Thanks!
|
2
1
|
|
|
|
|
3
|
I would strongly recommend the following pattern:
dcterms:subject is intended to be used to refer to entries in a controlled vocabulary and SKOS is the best practice way to publish those. foaf:topic (and related terms) are for relating together resources. Dan Brickley has a nice diagram that illustrates this usage: http://www.flickr.com/photos/danbri/3282565132/ I drew on that whilst putting together this presentation: |
||
|
|
|
2
|
skos:subject is indeed deprecated in favour of dc:subject. With the modern version of DC, DC Terms, http://purl.org/dc/terms/subject, then using a resource as the value of dc:subject is fine. Using a class rather than a skos:Concept as the classification can be OK but there is a difference between the class of say Lions and the class of media that are about Lions. See the Semantic Web Best Practice note for a discussion on this: http://www.w3.org/TR/swbp-classes-as-values/ |
||
|
|
|
2
|
Dublin Core was updated in 2008, and has (happily) moved away from the ubiquitous literals of dc10 and dc11. In your case move to using the current namespace |
||||||
|
|
1
|
maybe foaf:topic could also be of interest, since it has a foaf:Document as domain, and a owl:Thing as range |
||
|
|
|
0
|
dcterms:subject is definately a good choice, however it's worth considering sioc:topic too, in general usage dcterms:subject is often used with literal values by the broader web community, whereas sioc:topic is a subclass of dcterms:subject and generally used only with URIs. |
||
|
|