W3C home > Mailing lists > Public > public-swd-wg@w3.org > December 2006

RE: Call for Use Cases: Simple Knowledge Organization Systems (SKOS)

From: Barker, Sean \(UK\) <Sean.Barker@baesystems.com>
Date: Fri, 8 Dec 2006 15:37:48 -0000
Message-ID: <ABD8E85379D2D44D8D9B4BDAD5F693F304F61C7B@glkms0005>
To: <public-swd-wg@w3.org>
Cc: "Johnson, Julian \(UK\)" <Julian.Johnson@baesystems.com>, "Chris Holmes" <C.K.Holmes@lboro.ac.uk>, "Chris Holmes" <chris.k.holmes@btinternet.com>


Sean Barker
0117 302 8184

-----Original Message-----
From: Johnson, Julian (UK) 
Sent: 08 December 2006 09:35
To: Chris Holmes; Barker, Sean (UK); Chris Holmes
Subject: FW: Call for Use Cases: Simple Knowledge Organization Systems

I don't know if this may be of interest... Certainly in the STEP domain,
it seems the issue of mapping between different (e.g. discipline)
vocabularies is an important issue (or alternative strategy to forcing
common vocabulary across all disciplines).

Regards, Julian. 
Dr Julian Johnson
Executive Scientist
Systems Engineering Innovation Centre / BAE SYSTEMS Warton tel  : +44
1772 852963 Warton fax  : +44 1772 855715 SEIC tel : +44 1509 635227
SEIC Fax : +44 1509 635231
mobile: +44 7974 428 697
email: julian.johnson@baesystems.com
www.seic-loughborough.com <http://www.seic-loughborough.com> 

-----Original Message-----
From: public-swd-wg-request@w3.org [mailto:public-swd-wg-request@w3.org]
On Behalf Of Antoine Isaac
Sent: 06 December 2006 11:58
To: public-esw-thes@w3.org; public-semweb-lifesci@w3.org;
semantic-web@w3.org; public-swd-wg@w3.org
Subject: Call for Use Cases: Simple Knowledge Organization Systems

[Apologies for cross-postings. Please forward this mail to anyone

W3C Semantic Web Deployment Working Group

Call for Use Cases: Simple Knowledge Organization Systems (SKOS)

Are you currently using SKOS, or considering using SKOS in the near
future? If so, please tell us more by filling in the questionnaire below
and sending it back to us or to , preferably before January 14th, 2007. 

The information you provide will be influential in guiding the further
development of SKOS towards W3C Recommendation status.

We understand that your time is precious, so please don't feel you have
to answer every question. However, the more information you can provide,
the easier it will be for the Working Group to understand your
requirements. Questions marked with an asterix (*) are more important.
And, of course, please do not hesitate to contact us if you have any
trouble answering our questions. A FAQ page will be maintained on
http://www.w3.org/2006/07/SWD/wiki/UCFAQ, and a description example is
available at http://www.w3.org/2006/07/SWD/wiki/ManuscriptsCase.

We are particularly interested in use cases describing the use of
controlled structured vocabularies in distributed, metadata-driven
applications. This includes the use of thesauri, classification schemes,
subject heading systems and taxonomies to facilitate discovery and
retrieval of information. This also includes situations where two or
more vocabularies must be "mapped" or "linked" in order to provide
applications using heterogeneous metadata from different sources.

However, we're not ruling anything out at this stage, and the Working
Group will carefully consider all submissions we receive.

On behalf of the Working Group, thanks in advance for your time,

Antoine Isaac (aisaac@few.vu.nl), Jon Phipps (jphipps@madcreek.com) and
Daniel Rubin (dlrubin@stanford.edu) 


Questions marked with an asterix (*) are more important.

Section 0. Contact and confidentiality

Contact e-mail: S. Barker

Do you mind your use case being made public on the working group website
and documents : No

Section 1. Application

In this section we ask you to provide some information about the
application for which the vocabulary(ies) and or vocabulary mappings are
being used.

Please note:
 -- If your use case does not involve any specific application, but
consists rather in the description of a specific vocabulary, skip
straight to Section 2.
 -- If your application makes use of links between different
vocabularies, do not forget to fill in Section 3!

  1.1. What is the title of the application? 
	a) Product Life Cycle Support
	b) Tactical Situation Object

  1.2. What is the general purpose of the application?
       What services does it provide to the end-user?
	a) Through life support of complex products, including
configuration definition, maintenance definition,
maintenance planning and scheduling, maintenance and usage recording
(including configuration change)
	b) lightweight protocol for situation awareness in emergency

 *1.3. Provide some examples of the functionality of the application.
Try to illustrate all of the functionalities in which the
vocabulary(ies) and/or vocabulary mappings are involved.
	a) Probably several hundred separate functions, including
classification of items, classification of information usages (e.g.
types of part identifier), classification of entity roles (e.g. date as
start date), classification of relationships (e.g. supersedes). See PLCS
on Sourceforge.net and Oasis.open
	b) all attribute values are table driven, including types of
action, types of resource, relationships between items, etc. See TSO
either at CEN or Afnor

  1.4. What is the architecture of the application?
       What are the main components?
       Are the components and/or the data distributed across a network,
or across the Web?
	a) n/a - this is a data exchange mechanism between multiple
applications or multiple instances of the same application
	b) ditto

  1.5. Briefly describe any special strategy involved in the processing
of user actions, e.g. query expansion using the vocabulary structure.
	a) out of scope for data exchange
	b) out of scope for data exchange

  1.6. Are the functionalities associated with the controlled
vocabulary(ies) integrated in any way with functionalities provided by
other means? (For example, search and browse using a structured
vocabulary might be integrated with free-text searching and/or some sort
of social bookmarking or recommender system.)
	a) out of scope for data exchange
	b) out of scope for data exchange

  1.7. Any additional information, references and/or hyperlinks.
	See also the vocabularies for C2IEDM at the NATO MIP site

Section 2. Vocabulary(ies)

In this section we ask you to provide some information about the
vocabulary or vocabularies you would like to be able to represent using

Please note:
 -- If you have multiple vocabularies to describe, you may repeat this
section for each one individually or you may provide a single
description that encompasses all of your vocabularies.
 -- If your use case describes a generic application of one or more
vocabularies and/or vocabulary mappings, you may skip this section.
 -- If your vocabulary case contains cross-vocabulary links (between the
vocabularies you presented or to external vocabularies), please fill in
section 3!

  2.1. What is the title of the vocabulary? If you're describing
multiple vocabularies, please provide as many titles as you can.

  2.2. Briefly describe the general characteristics of the vocabulary,
e.g. scope, size...
	a) Vocabulary is in OWL, and contains an upper ontology of
several hundred items, with many terms defined below the upper ontology.
In some cases the upper ontology terms are place holders for local
	b) Currently as tabular document, with some tens of tables. Some
tables have tens of entries. 

  2.3. In which language(s) is the vocabulary provided?
       In the case of partial translations, how complete are these?
	a) definitions in English
	b) Base definitions in English.

 *2.4. Please provide below some extracts from the vocabulary. Use the
layout or presentation format that you would normally provide for the
users of the vocabulary. Please ensure that the extracts you provide
illustrate all of the features of the vocabulary.
a) Following is a paste an extract from one of the XML views:

The following classes of reference data are required for this

An Identification_code is an identifier_type which is encoded according
to some convention. Typically but not necessarily concatenated from
parts each with a meaning. E.g. tag number, serial number, package
number and document number. 
A Part_indentfication_code is a Identification_code that identifies the
types of parts. For example, a part number. CONSTRAINT: An
Identification_assignment classified as a Part_identification_code can
only be assigned to Part

Error RDL2: The class Organization_name is defined in more than one OWL
plcs-rdl-rbn.owl:Organization_name plcs-rdl-pmh.owl:Organization_name 
The definition shown is from: plcs-rdl-rbn.owl 

An Organization_name is a Name by which an organization is known. E.g.
"OntologiesRus Ltd"
An Owner_of is an Organization_or_person_in_organization_assignment that
is assigning a person or organization to something in the role of owner.
For example, the owner of the car.
A Date_actual is a Date_or_date_time_assignment that assigns a date or
date_time to something where the date is when something actually
happened as opposed to when it was planned or predicted to happen.

b) From Word

2.5	URGENCY element
This is a proposal, consistent with OASIS description of the civil
protection domain. It is consistent with the CAP protocol v1.0
(cap.alertinfo.urgency.code). The code denotes the urgency of the
subject event of the alert message.

Acronym	Level	Definition
IMMEDI	Immediate	Responsive action should be taken immediately
EXPECT	Expected	Responsive action should be taken soon (within
next hour)
FUTURE	Future	Responsive action should be taken in the near future
PAST	Past	Responsive action is no longer required
UNKNWN	Unknown	Urgency not known

  2.5. Describe the structure of the vocabulary.
       What are the main building blocks?
       What types of relationship are used? If you can, provide examples
by referring to the extracts given in paragraph 2.4.

  2.6. Is a machine-readable representation of the vocabulary already
available (e.g. as an XML document)? If so, we would be grateful if you
could provide some example data or point us to a hyperlink.
	a) Yes, See sourceforge
	b) Yes, See afnor

  2.7. Are any software applications used to create and/or maintain the
       Are there any features which these software applications
currently lack which are required by your use case?
	a) Protege
	b) Word

  2.8. If a database application is used to store and/or manage the
vocabulary, how is the database structured? Illustration by means of
some table sample is welcome.

  2.9. Were any published standards, textbooks or written guidelines
followed during the design and construction of the vocabulary?
       Did you decide to diverge from their recommendations in any way,
and if so, how and why?
a) No
b) Inherited from MIP

  2.10. How are changes to the vocabulary managed?
a) Formal Change Process
b) Early stage of development, so no formal process

  2.11. Any additional information, references and/or hyperlinks.

Section 3. Vocabulary Mappings

In this section we ask you to provide some information about the
mappings or links between vocabularies you would like to be able to
represent using SKOS.

Please note:
 -- If your use case does not involve vocabulary mappings or links, you
may skip this section!

  3.1. Which vocabularies are you linking/mapping from/to?

 *3.2. Please provide below some extracts from the mappings or links
between the vocabularies. Use the layout or presentation format that you
would normally provide for the users of the mappings. Please ensure that
the examples you provide illustrate all of the different types of
mapping or link.

  3.3. Describe the different types of mapping used, with reference to
the examples given in paragraph 3.2.

  3.4. Any additional information, references and/or hyperlinks. 

This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
Received on Friday, 8 December 2006 23:39:46 UTC

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