This is an archive of an inactive wiki and cannot be modified.

Section 0. Contact and confidentiality

Contact e-mail: 

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

We'd be very glad if you'll publish our use case.

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.

SKOS representation of LOINC

 2.2. Briefly describe the general characteristics of the vocabulary, e.g. scope, size...

LOINC, a Universal Standard for Identifying Laboratory Observations. Please refer to for further information.

 2.3. In which language(s) is the vocabulary provided?

The vocabulary is provided as a database see

      In the case of partial translations, how complete are these?

We provide an almost complete translation. We excluded from the translation only the semi-structured part.

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

Please refer to:

 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.

See: RucLoinc/MachineReadable

 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?

No, the vocabulary maintenance is performed through an RDF/SKOS/OWL editor.

 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.

Standard RDF databases can be used

 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?

We made use of the "Quick Guide to Publishing a Thesaurus on the Semantic Web" ( and the "SKOS Core Guide" (

 2.10. How are changes to the vocabulary managed?

The vocabulary maintenance is performed manually.

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