W3C home > Mailing lists > Public > public-esw-thes@w3.org > April 2010

Réf : Re: Status of thesaural resources (stable, testing etc)

From: Richard Parent <richard.parent@msg.gouv.qc.ca>
Date: Tue, 27 Apr 2010 16:09:56 -0400
To: public-esw-thes <public-esw-thes@w3.org>
Message-ID: <OFBACAD7F2.386F7328-ON85257712.006E0FBD-85257712.006EC5DA@sct.gouv.qc.ca>



ebXML defines a registry object status (extract from regrep-rim-3.0-os May
2, 2005. Page 23 of 78) :

2.5.9.1 Pre-defined RegistryObject Status Types

Approved : Status of a RegistryObject that catalogues content that has been
submitted to the registry and has been subsequently approved.
Deprecated : Status of a RegistryObject that catalogues content that has
been submitted to the registry and has been subsequently deprecated.
Submitted : Status of a RegistryObject that catalogues content that has
been submitted to the registry.
Withdrawn : Status of a RegistryObject that catalogues content that has
been withdrawn from the registry. A repository item has been removed
but its ExtrinsicObject still exists.




                                                                           
             public-esw-thes@w                                             
             3.org                                                         
             Envoyé par :                                                A 
             public-esw-thes-r         Dan Brickley <danbri@danbri.org>    
             equest@w3.org                                              cc 
                                       Bernard Vatant                      
                                       <bernard.vatant@mondeca.com>, Marc  
             27/04/10 03:51 PM         Wick <marc@geonames.org>, Dublin    
                                       Core                                
                                       <DC-ARCHITECTURE@jiscmail.ac.uk>,   
                                       SKOS <public-esw-thes@w3.org>,      
                                       Leigh Dodds                         
                                       <leigh.dodds@talis.com>, Libby      
                                       Miller <Libby.Miller@bbc.co.uk>,    
                                       Dominique Vanpée                    
                                       <dominique.vanpee@poisoncentre.be>, 
                                       Wim Daeleman                        
                                       <wim.daeleman@poisoncentre.be>      
                                                                     Objet 
                                       Re: Status of thesaural resources   
                                       (stable, testing etc)               
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Funny, I was asked this morning to add a "validated y/n" attribute to
our application based on SKOS concepts.

Interesting to see that experience proven statuses are:

'unstable'
    The meaning, deployment practices, documentation (or important
    associated software/services) associated with this term are liable
    to change arbitrarily at some point in the future. They may not, but
    stability is not guaranteed. Use with caution.
'testing'
    The meaning, deployment practices, documentation and general
    understanding of this term are approaching some stability, but
    changes are still possible due to implementation experience or other
    unanticipated factors.
'stable'
    The term is relatively stable, and its documentation and meaning are
    not expected to change substantially.
'archaic'
    This term is marked as old-fashioned; although used, it is not
    considered typical of current best practice and alternative
    expressions may be preferable.

Completed by ( http://www.w3.org/2003/06/sw-vocab-status/ns ):

moreinfo
    A property of a class which contains additional information about
the term's status and intended for human usage, typically used to
explain why the term is unstable.
    For example, <vs:moreinfo>a possible conflict exists, see
http://www.example.com for more info</vs:moreinfo>

userdocs
    A property of a class which contains information about the term's
usage and intended for human usage.
    For example, <vs:userdocs>used to indicate the term is
normative.</vs:userdocs>

Is this right for Belgium PoisonCentre thesaurus managers ?

Have a nice evening,

Christophe Dupriez

Dan Brickley a écrit :
> +cc: Leigh, Libby
>
> On Tue, Apr 27, 2010 at 6:56 PM, Bernard Vatant
> <bernard.vatant@mondeca.com <mailto:bernard.vatant@mondeca.com>> wrote:
>
>     Hello folks
>
>     We are currently revisiting the Geonames ontology (long overdue)
>     including feature codes, on which I would like to add some
>     Dublin-Core like annotations re. concepts. In particular some
>     concepts are going to be deprecated using dcterms:isReplacedBy,
>     some will be deprecated altogether without replace because they've
>     never be used, and quite a lot will be put in a status of
>     quasi-obsolescence or quasi-extinction. Those are feature codes
>     used less than one per million features, which means less than 7
>     times considering Geonames has over 7 millions features in store ....
>     I was wondering which vocabulary is the best for expressing that.
>     http://www.w3.org/2003/06/sw-vocab-status/ns is used by FOAF,
>     Bibontology and others. But it defines status as a data property,
>     I would prefer an object property with an enumerated range of
>     individual values. Of course I can define those in geonames data
>     space, but since this is not particular to geographical codes, I
>     was wondering if there was some vocabulary on some shelves I miss..
>     BTW I was amazed not to find any "status" property in Dublin Core..
>
>
> Yes, that is a limitation of the sw-vocab-status vocab. At the end of
> last year I started writing it up towards a W3C Note (after a 'go for
> it' from Ivan), with Libby Miller and Leigh Dodds. The effort is a
> little stalled but the draft is
> at http://www.w3.org/2003/06/sw-vocab-status/note.html
>
> If you think it's worthwhile, we could expand the note to include new
> more useful properties.
>
> Interested to help? :)
>
> (even encouraging us to put time into this counts as help!)
>
> Dan
>
>
>
>
>     Suggestions?
>
>     --
>     Bernard Vatant
>     Senior Consultant
>     Vocabulary & Data Engineering
>     Tel:       +33 (0) 971 488 459
>     Mail:     bernard.vatant@mondeca.com
>     <mailto:bernard.vatant@mondeca.com>
>     ----------------------------------------------------
>     Mondeca
>     3, cité Nollez 75018 Paris France
>     Web:    http://www.mondeca.com
>     Blog:    http://mondeca.wordpress.com
>     ----------------------------------------------------
>
>



graycol.gif
(image/gif attachment: graycol.gif)

pic07152.gif
(image/gif attachment: pic07152.gif)

ecblank.gif
(image/gif attachment: ecblank.gif)

Received on Wednesday, 28 April 2010 08:02:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:46:02 UTC