Re: ISSUE-147: Last Call Comment: Notations as plain literals

Hi,

I think there is a misunderstanding here. "Notations" such as wee see 
them are just lexical properties of concepts that do represent classes 
in a classification schemes.
(see the presentation by Mickael Panzer on SKOSifying DDC [1])
In such a context I don't see the point of uncoupling the representation 
of the notation from the one its conceptual counterpart.
Further, Erik's solution just postpones the problem: once you've created 
your new concept for the pure notation, you still have to represent the 
code in some way. There will have to be a literal involved, whether 
plain (as for notations as prefLabels) or typed (as for notations as 
skos:notation).

But well you're right, that's already discussing the pattern, so I 
plainly support your answer :-)

Antoine

[1] 
http://www.oclc.org/news/events/presentations/2008/ISKO/20080805-deweyskos-panzer.ppt

>
>
> Hi all,
>
> Here's a draft response to Erik on [ISSUE-147], let me know what you 
> think. Note *this is just a draft, not the actual response* -- I'll 
> wait for feedback from the WG before replying formally to Erik. (Erik: 
> if you're lurking on this list feel free to post your thoughts at any 
> time.)
>
> ----------------------------------------------------------------------------- 
>
>
>
> Dear Erik,
>
> thanks for your comments [1,ISSUE-147]:
>
> """
> While it should certainly be possible to specify a datatype for a 
> notation,
> relying on the datatype to identify the classification scheme and thus
> effectively requiring the datatype seems complex and a barrier to 
> adoption.
>
> Would it be possible to use a distinct skos:ConceptScheme instead of a
> datatype to identify each notational classification scheme?  enumerating
> the notations with skos:Concepts?  Mapping properties could then 
> associate
> the concepts from the notational classification scheme with concepts 
> in the
> scheme that's the focus of interest.  The datatype could then be optional
> and used for validation of value format (as is commonly expected for XML
> Schema datatypes).
>
> The cost would be some indirection, but that could be mitigated by 
> minting
> URI identifiers for notational concepts in which the final step is a
> recognizable variant on the notation for the concept.  The benefit 
> would be
> consistency, simplicity, and a public, reusable SKOS definition of each
> notational classification scheme.
> """
>
> ------------------------------------------------------------
>
> The design pattern that you propose is consistent with the SKOS data 
> model
> and could be used to address the issue of notations.
>
> We welcome discussion of such patterns within the SKOS community, but 
> at this
> point propose to make no changes to the current document.
>
> Are you able to live with this?.
>
> Cheers,
>
>     Sean Bechhofer
>     Alistair Miles
>
> [ISSUE-148] http://www.w3.org/2006/07/SWD/track/issues/148
> [1] http://lists.w3.org/Archives/Public/public-swd-wg/2008Jun/0103.html
>
>
> -- 
> Sean Bechhofer
> School of Computer Science
> University of Manchester
> sean.bechhofer@manchester.ac.uk
> http://www.cs.manchester.ac.uk/people/bechhofer
>
>
>
>
>

Received on Monday, 10 November 2008 19:44:03 UTC