W3C home > Mailing lists > Public > public-swd-wg@w3.org > January 2008

Re: ISSUE-84: ConstructionOfSystematicDisplaysFromGroupings

From: Antoine Isaac <aisaac@few.vu.nl>
Date: Wed, 23 Jan 2008 11:05:06 +0100
Message-ID: <47971152.5080107@few.vu.nl>
To: SWD WG <public-swd-wg@w3.org>

Dear all,

Regarding this issue, I would propose to OPEN it and CLOSE it very quickly.
The resolution for it (unless someone really wants to invest time in 
this) would be to keep the existing Primer as such, that is, not to 
propose an algorithm.

My motivations for this would be:
1. The algorithm could be quite complex if we want to consider all the 
possible cases of nested groupings. I feel such a level of complexity 
clearly out of scope for the Primer.
2. Certain applications might want to implement specific strategies, 
making our effort relatively pointless.

Or perhjaps we could just POSTPONE it to the writing of a note on the 
subject. But I don't know the formal implication of such a resolution

Cheers,

Antoine

> ISSUE-84: ConstructionOfSystematicDisplaysFromGroupings
>
> http://www.w3.org/2006/07/SWD/track/issues/84
>
> Raised by: Antoine Isaac
> On product: All
>
> >From [1]:
>
>   
>> I propose the following section of the SKOS Semantics wiki draft as resolution
>>     
> of ISSUE-33 "Grouping Constructs" [2]:
>   
>> http://www.w3.org/2006/07/SWD/wiki/SKOS/Semantics/Grouping?action=recall&rev=2>
>>
>> This section implements the "Minimal Fix" proposal [2], with a few additional
>> axiomatic triples to make explicit the OWL typing of properties and the
>> disjointness of skos:Collection and skos:ConceptScheme.
>>
>> Note that this section does not address the issue of constructing a systematic
>> hierarchical display, but delegates this responsibility to the SKOS Primer.
>> Note also that the SKOS Primer section on grouping constructs is yet to be 
>> done, and that in particular I have not met Antoine's concerns below regarding
>> nested collections.
>>
>> However, I suggest we accept this resolution for now (because it does fix the
>> actual issue), and raise a new issue regarding the representation and 
>> construction of systematic hierarchical displays.
>>     
>
> (Antoine's comment on nested collections are at [3])
>
> Now from [4] (no need to thank me Alistair ;-p)
>
>   
>> However, in the absence of any presentational information, there could be a
>> default method of constructing a systematic display. To handle SKOS grouping
>> constructs, this would require an algorithm which is *fairly* sophisticated -
>> certainly not straightforward to a novice hacker. The onus is on me to provide
>> a reference implementation :)
>>     
>
> This was reflected in [5]:
>
>   
>> (Statement 2) The SWDWG MAY publish an algorithm to generate a default 
>> thesaurus systematic display from an RDF graph using the SKOS vocabulary.
>> However, applications are not required to use the algorithm, and MAY use any
>> means to convey information required to construct a thesaurus systematic 
>> display.
>>     
>
> The current Primer [6] in its section on Collections of Concepts (4.1) does not
> propose anything:
>
>   
>>  A systematic (hierarchical) display can then be generated including the
>> concept grouping "milk by source animal", as presented in the example 
>> introducing this sub-section. The skos:broader hierarchy and the collection 
>> membership information can be used for this, but the process still requires a 
>> dedicated algorithm, the implementation of which is left to specific 
>> applications.
>>     
>
> Shall we change this? 
>
>
> [1] http://lists.w3.org/Archives/Public/public-esw-thes/2007Jun/0012.html
> [2] http://www.w3.org/2006/07/SWD/track/issues/33
> [3] http://lists.w3.org/Archives/Public/public-esw-thes/2007May/0010.html
> [4] http://lists.w3.org/Archives/Public/public-esw-thes/2007Jun/0016.html
> [5] http://www.w3.org/2006/07/SWD/wiki/SkosDesign/PresentationInformation
> [6] http://www.w3.org/2006/07/SWD/wiki/SKOS/DraftPrimer
>
>
>
>
>
>   
Received on Wednesday, 23 January 2008 10:05:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:07:52 UTC