Re: MiniSKOS proposal: add Topic, an equivalentClass to skos:Concept, and relate schema properties to it.

On Tue, Nov 19, 2013 at 9:22 PM, Dan Brickley <> wrote:

> "MiniSKOS proposal for"
> This is a greatly minimized proposal for <-> SKOS
> integration. I didn't make a wiki entry for it yet; maybe it's best to
> add it to than make a separate
> writeup?
> Essentially, we add one type 'Topic', we say it is an equivalent class
> to W3C skos:Concept, and then we focus on identifying properties in
> where it can be an expected type.

 +1 Seems like a good move!

> Test build:
> We add a range of 'Topic' to these properties: about,
> occupationalCategory, targetUrl, applicationCategory,
> applicationSubCategory, category, mentions, serviceType.

Off the top of my head, I think <> should also have
a Topic range.

This would be our way of saying that (sometimes) the values of these
> properties would take links into existing controlled vocabularies,
> typically but not necessarily documented using W3C SKOS in (hopefully)
> RDFa. By doing so, we make it easier for data to use
> hierarchies of controlled codes, alternate and multilingual labels,
> and links between such vocabularies.
> All other information about a Topic would be expressed in
> vocabulary (broader etc.), most likely SKOS.

Sounds very sensible. I suppose at this point it would be advisable to add
the Topic type (and e.g. name alongside skos:prefLabel) to published data,
to ensure that consumers in general (e.g. the search engines)
can make sense of it?

(Of course, it would be great if, over time, consumers would also make use
of the OWL equivalencies to other schemas' classes and properties in
general, in order to leverage existing data as is.)


> Dan

Received on Tuesday, 19 November 2013 21:58:55 UTC