Re: Ordering concepts in a Tree display / possibly more than a sort key

Hi Christophe,


> If SKOS community wants to go further than one concept attribute for what I would propose to call a "siblingKey" (a value used to sort sibling concepts), an attribute to the broader relation is therefore needed.
> This would be easy in XML (ISO 25954 but I do not see any ordering information in the HierarchicalRelationship element) or with TopicMaps but it requests reification of the RDF relation in SKOS.
>
> Knowing other problems (data about approval work-flow for relations for instance), may I suggest starting the definition of SKOS-XR (eXtended Relations) to open the design space to this kind of enhancement ?
> Who has the "authority" (interest!) to manage such a project?


It's indeed more a matter of interest than authority: there's nothing that prevents you from creating it in your own namespace, suggesting it for usage here and on the wiki, and waiting for community uptake!

Two comments if you embark on such a thing, though:

- if you want to maximize the chance for your extension to be re-used, you should really point out in some documentation its added value re. skos:OrderedCollection. One doubt I had, quickly parsing mails, is whether that fits or not situations where multiple inheritance happens...

- the "R" in "XR" sounds strange for your problem. I'd have expected an extension for relation to add new semantic relations, like broaderPartitive and others we did not include in the standard. An O for "Order" may fit better your situation. But well that's a matter of personal taste maybe :-)

Cheers,

Antoine

Received on Tuesday, 8 February 2011 07:46:09 UTC