JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DC-GENERAL Archives


DC-GENERAL Archives

DC-GENERAL Archives


DC-GENERAL@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DC-GENERAL Home

DC-GENERAL Home

DC-GENERAL  December 2006

DC-GENERAL December 2006

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

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

From:

Antoine Isaac <[log in to unmask]>

Reply-To:

Antoine Isaac <[log in to unmask]>

Date:

Wed, 13 Dec 2006 22:15:37 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (176 lines)

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

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 [log in to unmask], 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 ([log in to unmask]), Jon Phipps ([log in to unmask]) and 
Daniel Rubin ([log in to unmask])

================================================================
================================================================


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

================================================================
Section 0. Contact and confidentiality
================================================================

Contact e-mail:

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

================================================================
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?
 1.2. What is the general purpose of the application?
      What services does it provide to the end-user?

*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.

 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?

 1.5. Briefly describe any special strategy involved in the processing 
of user actions, e.g. query expansion using the vocabulary structure.

 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.)

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

================================================================
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 
SKOS.

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...

 2.3. In which language(s) is the vocabulary provided?
      In the case of partial translations, how complete are these?

*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.

 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.

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

 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?

 2.10. How are changes to the vocabulary managed?

 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.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager