W3C home > Mailing lists > Public > public-esw-thes@w3.org > December 2009

Re: Dinamic hasTopConcept property

From: Thomas Bandholtz <thomas.bandholtz@innoq.com>
Date: Thu, 03 Dec 2009 23:11:59 +0100
Message-ID: <4B1837AF.7060309@innoq.com>
To: Juan Antonio Pastor Sánchez <pastor@um.es>
CC: public-esw-thes@w3.org
Hi Juan,

as far as I see you are perfectly right as long as you have only one
skos:ConceptScheme, and as long as you just think about it.

In an open world there are many skos:ConceptScheme instances.

If you make use of the skos:inScheme property for each of your
skos:Concept instances, you might say something like:

"Any concept within my scheme which has no broader in the same scheme is
a topConcept of this scheme."

(Someone might state that your concept has a broaderMatch to another
concept in a different scheme, why not? remember broaderMatch is
subProptery of broader ...)

I think the difference is about whether you have a decision that some
concepts shall be the top concepts of your scheme, or you just leave
this to the editor (who might accidently forget to add some broader to a
concept ... never trust in editorial staff too much ... ;-)

In the first case, link from your scheme to some dedicated topConcepts
just to make sure about this.
In the second case, you may be right, but there is no explicit inference
rule in the current skos rec which would safely result in some tops.

Looking forward to discussion, as I think Juan is basically right, and
this has not been clarified so far.

Kind regards,

Juan Antonio Pastor Sánchez schrieb:
> Hello everyone,
> I am developing an application to manage concept schemes, based on
> SKOS. My question is about the hasTopConcept property. In my opinion
> this property should be generated dynamically (by inference) during
> the query of the concept scheme (only for viewing and browsing
> purposes). As indicated in SKOS-Reference:
> "The property skos: hasTopConcept is, by convention, used to link a
> concept to the SKOS concept scheme (s) which are topmost in the
> hierarchical relations for that scheme."
> That is, a Top concept would be a concept of a hierarchy that did not
> have any one broader concept. Therefore, It is not necessary to
> explicitly define a concept such as Top concept. Thus, the tasks of
> managing the scheme concept could be simplified.
> This interpretation would be correct?
> Regards
> -- 
> Ph.D. Juan Antonio Pastor Sánchez
> Senior Lecturer - Dep. Information and Documentation
> Faculty Communication and Documentation
> University of Murcia
> phone: +34 868 88 8780
> http://webs.um.es/pastor - http://skos.um.es/
> pastor@um.es <mailto:pastor@um.es>

Thomas Bandholtz, thomas.bandholtz@innoq.com, http://www.innoq.com 
innoQ Deutschland GmbH, Halskestr. 17, D-40880 Ratingen, Germany
Phone: +49 228 9288490 Mobile: +49 178 4049387 Fax: +49 228 9288491
Received on Thursday, 3 December 2009 22:12:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:45:59 UTC