/[volute]/trunk/projects/vocabularies/doc/vocabularies.xml
ViewVC logotype

Diff of /trunk/projects/vocabularies/doc/vocabularies.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 63 by norman.x.gray, Thu Feb 14 17:43:23 2008 UTC revision 64 by norman.x.gray, Sat Feb 16 03:21:46 2008 UTC
# Line 261  Line 261 
261  <p>The most immediate high-level motivation for this work is the  <p>The most immediate high-level motivation for this work is the
262  requirement of the VOEvent standard <span class='cite'  requirement of the VOEvent standard <span class='cite'
263  >std:voevent</span> for a controlled vocabulary usable in the  >std:voevent</span> for a controlled vocabulary usable in the
264  VOEvent's <code>&lt;why/&gt;</code> and <code>&lt;what/&gt;</code>  VOEvent's <code>&lt;Why/&gt;</code> and <code>&lt;What/&gt;</code>
265  elements, which describe what  elements, which describe what
266  sort of object the VOEvent packet is describing, in some broadly  sort of object the VOEvent packet is describing, in some broadly
267  intelligible way.  For example a `burst' might be a gamma-ray burst  intelligible way.  For example a `burst' might be a gamma-ray burst
# Line 310  Line 310 
310  supports interoperability, building on the investments which  supports interoperability, building on the investments which
311  institutions and users have made in existing vocabularies]</li>  institutions and users have made in existing vocabularies]</li>
312    
313    <li>A user receives a VOTable of results from a VO application – for
314    example a catalogue of objects or observations – and wants to search a
315    database of old FITS files for potential matches.  Because the UCDs
316    labeling the columns of the tables are expressed in well-documented
317    SKOS, both the official descriptions of the UCDs and their semantic
318    matches to a variety of other plain-text vocabularies (such as the IAU
319    or AOIM thesauri) are available to the VO application, provide a basis
320    for massive searches for all kinds of FITS keyword values.</li>
321    
322  </ul>  </ul>
323    
324  <p>It is not a goal of this standard, as it is not a goal of SKOS, to  <p>It is not a goal of this standard, as it is not a goal of SKOS, to
# Line 335  Line 344 
344  less rich or less coherent than we might prefer, but widely enough  less rich or less coherent than we might prefer, but widely enough
345  deployed to be useful.</p>  deployed to be useful.</p>
346    
347    <p>The purpose of this document is not to produce new vocabularies but
348    to show how vocabularies can be easily expressed in a internationally
349    standardized, computer-manipulable format.  Four example vocabularies
350    that have previously been expressed using non-standardized formats –
351    namely the A&amp;A keyword list, the IAU and AOIM thesauri, and UCD1 –
352    are included below as an illustration of how simple it is to publish
353    them in SKOS.  In all cases, one can easily express all of the
354    information of the original source vocabularies.  It is true, that
355    complex vocabularies can be expensive to produce, maintain, and
356    deploy, and it will take a while until VO applications will be able to
357    use them to full advantage.  However, the example vocabularies should
358    make it fairly easy to boot-strap the process by providing useful
359    vocabularies that can be used `out of the box'.</p>
360    
361  </div>  </div>
362    
363  <div class="section">  <div class="section">
# Line 936  Line 959 
959    
960  <p>The vocabularies described below are included, as SKOS files, in  <p>The vocabularies described below are included, as SKOS files, in
961  the distributed version of this standard.  These vocabularies have  the distributed version of this standard.  These vocabularies have
962  stable URLs <span class='todo' >Format TBD, see  stable URLs <span class='todo' >Format TBD, see <a
963  <a href='@DISTURI@/issues#versioning-3' >[versioning-3]</a></span>, and  href='@DISTURI@/issues#versioning-3' >[versioning-3]</a></span>, and
964  may be cited and used indefinitely.  These vocabularies will not,  may be cited and used indefinitely.  These vocabularies will not,
965  however, be developed as part of the maintenance of this standard.  however, be developed as part of the maintenance of this standard.
966  Interested groups, within and outwith the IVOA, are encouraged to take  Interested groups, within and outwith the IVOA, are encouraged to take
967  these as a starting point and absorb them within an existing  these as a starting point and absorb them within existing
968  process.</p>  processes.</p>
969    
970  <p>The exception to this is the IVOA-T (see <span class='xref'  <p>The exceptions to this rule are the constellation vocabulary,
971  >vocab-ivoat</span>), which will be developed as part of a process  provided here mainly for didactic purposes, and the proposed IVOA
972  which has already begun.  <span class='todo' >Clarify wording here;  Thesaurus, which is being developed as a separate project and whose
973  include reference to forthcoming IVOA-T document; ??include snapshot  aim is to provide a corrected, more user-friendly, more complete, and
974  of vocabulary in the distribution??</span>.</p>  updated version of the 1993 IAU thesaurus.  Although work on the IVOA
975    Thesaurus is on-going, the fact that it is largely based on the IAU
976    thesaurus means that it is already a very useful resource, so a usable
977    snapshot of this vocabulary will be published with the other
978    examples.</p>
979    
980  <p>We provide a set of SKOS files representing the vocabularies which  <p>We provide a set of SKOS files representing the vocabularies which
981  have been developed, and mappings between them.  These can be  have been developed, and mappings between them.  These can be

Legend:
Removed from v.63  
changed lines
  Added in v.64

msdemlei@ari.uni-heidelberg.de
ViewVC Help
Powered by ViewVC 1.1.26