[metadataLibrarians] SKOS question

Tue Jan 31 16:52:39 PST 2006

Jenn:

As you know, we're building a registry that will focus first on 
controlled vocabularies, using SKOS.  One of the real challenges for 
us in doing this is attempting to figure out what kind of services 
vocabulary users might need, as they manage projects or applications. 
You seem to us to be in a good position to help us think about that, 
since you are clearly intending to do some fairly intense work with 
vocabularies.

Are you and your group considering what kinds of registry-based 
services might support your work? We have some ideas, primarily 
revolving around the notions of providing updates to vocabulary users 
when changes occur and usage information to vocabulary owners.  We'd 
love to hear what you might have in mind, and now's a good time to 
affect our planning as we're still in early stages.

Regards,
Diane

>Hi Diane-
>
>Whether or not statuses *should* be part of SKOS I'll defer to others
>on, not knowing that much about the initiative. I do know that we need
>this functionality in whatever language we end up choosing, even if we
>have to extend that language to get it.
>
>You asked about what statues we want. They're very similar to what
>you've outlined, but there are a few more with slightly different shades
>of meaning to help us manage a workflow whereby we'd be importing terms
>(& references!) from some existing vocabularies, and entering other ones
>manually. We need to be able to track what was imported on purpose and
>what got created because it was a reference from something else that was
>imported. We may or may not end up wanting that reference as a term in
>the thesaurus for this particular project.
>
>Jenn
>
>>  -----Original Message-----
>>  From: metadatalibrarians-bounces at lists.monarchos.com
>>  [mailto:metadatalibrarians-bounces at lists.monarchos.com] On
>>  Behalf Of Diane I. Hillmann
>>  Sent: Wednesday, January 18, 2006 10:31 AM
>>  To: A listserv for Metadata Librarians
>>  Cc: uw-cornell at u.washington.edu
>>  Subject: Re: [metadataLibrarians] SKOS question
>>
>>  Jenn:
>>
>>  I forwarded your original message to my colleagues working
>>  with me on the NSDL Registry, since we'd also been talking
>>  about our need for status information. From the point of view
>>  of a registry, 'status' is both administrative information
>>  for the operation of the registry, but also information that
>>  we'd need to expose in our output to other services and end users.
>>
>>  Whether or not the notion of status needs to be a part of the
>>  SKOS standard itself is kind of an open question, it seems to
>>  me. In Dublin Core, we spent a lot of time talking about
>>  administrative data, and found that we could not agree on
>>  what was needed, so gave it up.  SKOS is new and has few real
>>  implementations yet, so I suspect we'll be using a local
>>  extension for status until there's enough experience in the
>>  field to propose something firmer for SKOS.
>>
>>  That said, below is what we've come up with so far:
>>
>>  Draft
>>       The state of a schema (element set or member property)
>>  or a scheme (vocabulary and or member vocabulary term) that
>>  has been created in the registry by a Maintainer but that has
>>  not been submitted to the Registry Manager (or delegate)
>>
>>  Submitted
>>       The state of a schema (element set) or a scheme
>>  (vocabulary and vocabulary terms) that has been submitted by
>>  a Maintainer and is under review by the Registry Manager (or delegate)
>>
>>  Published
>>       The state of a schema (element set or member properties)
>>  or a scheme (vocabulary and member vocabulary terms) that has
>>  been exposed to external human and machine agents through the registry
>>
>>  Deprecated
>>       The state of a schema (i.e., element set or member
>>  property) or a scheme (i.e., vocabulary or member vocabulary
>>  term) the use of which is no longer advised, most often
>>  because it has been withdrawn or replaced. Deprecation is
>>  used to indicate that a particular schema (i.e., element set
>  > or member property) or scheme (i.e., vocabulary or member
>>  vocabulary term) is preserved for purposes of
>>  backward-compatibility, but should be phased out in the
>>  creation of future instance metadata. Deprecated schemas and
>>  schemes are never deleted.
>>
>>  What statuses were you considering?
>>
>>  Diane
>>
>>
>>  >Hi everyone-
>>  >
>>  >As a follow-up to my recent query regarding languages for storing
>>  >thesaurus structures, I'm looking more carefully at the most
>>  promising
>>  >options and comparing them to the specific functionality we need. In
>>  >looking at SKOS <http://www.w3.org/2004/02/skos/>, I don't see right
>>  >offhand how one would indicate the "status" of a term. We need a
>>  >language that can support the building of a thesaurus over
>>  time, so we
>>  >need to be able to say a term is approved for use, or is
>>  preliminary in
>>  >some way and needs more investigation before it should be used. (We
>>  >actually have a series of 5 statuses we want to use, but you get the
>>  >idea...) Has someone successfully done this in SKOS and can
>>  point me in
>>  >the right direction as to how one would do this?
>>  >
>>  >Jenn
>>  >
>>  >========================
>>  >Jenn Riley
>>  >Metadata Librarian
>>  >Digital Library Program
>>  >Indiana University - Bloomington
>>  >Wells Library E170
>>  >(812) 856-5759
>>  >www.dlib.indiana.edu
>>  >
>>  >Inquiring Librarian blog: www.inquiringlibrarian.blogspot.com
>>  >_______________________________________________
>>  >metadatalibrarians mailing list
>>  >metadatalibrarians at lists.monarchos.com
>>  >http://lists.monarchos.com/listinfo.cgi/metadatalibrarians-mo
>>  narchos.co
>>  >m
>>  _______________________________________________
>>  metadatalibrarians mailing list
>>  metadatalibrarians at lists.monarchos.com
>>  http://lists.monarchos.com/listinfo.cgi/metadatalibrarians-mon
>>  archos.com
>>
>_______________________________________________
>metadatalibrarians mailing list
>metadatalibrarians at lists.monarchos.com
>http://lists.monarchos.com/listinfo.cgi/metadatalibrarians-monarchos.com