W3C home > Mailing lists > Public > public-vocabs@w3.org > October 2013

Re: SKOS proposal - labels and notes

From: Karen Coyle <kcoyle@kcoyle.net>
Date: Sun, 20 Oct 2013 09:30:33 -0700
Message-ID: <52640529.30406@kcoyle.net>
To: public-vocabs@w3.org

On 10/20/13 7:25 AM, Antoine Isaac wrote:

> Would this imply that the recommendation would be to have only one
> schema:name, for the preferred label, and use altLabel and hiddenLabel
> for variants? It may be conflicting with the possibility (already used?)
> to have several schema:name for something.

Hi, Antoine. Thanks for the detailed explication of this issue.

As someone with a library background, I perhaps have a particularly 
strict interpretation of SKOS. In my field, thesauri exist in equal part 
to create a map of concepts and to control the terminology used for 
those concepts. This latter function is less common in today's web 
environments, where discovery is done on natural language, not 
controlled terms. Because there are still KOS systems that use 
controlled terms as concept identifiers, I would hate to see SKOS 
preflabel re-used in a less precise manner.

I believe this supports maintaining a distinction between schema:name 
and skos:prefLabel, and not equating the two.


> Anyway, I strongly support the proposal to 'upgrade' altLabel and
> hiddenLabel (and prefLabel if it's minted as a schema.org property) to
> Thing.
> Actually the current version of the W3C ORG ontology uses it for
> Organizations [3] (well, they use prefLabel, in fact). This would make
> the ORG data compatible with schema.org.
> On notes: I am mildly in favor of "[For] skos:definition use
> schema:description." There's quite some difference here. But perhaps a
> good side effect of having more annotation properties on Thing would be
> to allow cleaning of schema.org's approach to notes. There might be many
> note-like properties deep down in the schema.org hierarchy, they should
> be at the highest level possible! (if just to help us decide whether
> it's appropriate to bring it more notes from SKOS's namespace).
> I am not a great fan of using one single 'hasNote' property in
> combination with a 'Note' class and subclasses of it. This is in fact
> quite in line with some patterns allowed by SKOS, where notes are
> 'related resources' [4]. But in a schema.org scenario it's perhaps too
> complex!
> Best,
> Antoine
> [1]http://lists.w3.org/Archives/Public/public-vocabs/2013Sep/0195.html
> [2] http://www.w3.org/TR/vocab-dcat/
> [3] http://www.w3.org/TR/vocab-org/
> [4] http://www.w3.org/TR/skos-primer/#secadvanceddocumentation
> http://lists.w3.org/Archives/Public/public-vocabs/2013Oct/0142.html
> Thad this is awesome!

Karen Coyle
kcoyle@kcoyle.net http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet
Received on Sunday, 20 October 2013 16:31:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:32 UTC