Changes between Version 15 and Version 16 of FCS-specification


Ignore:
Timestamp:
04/18/12 10:35:20 (12 years ago)
Author:
herste
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FCS-specification

    v15 v16  
    136136<indexInfo>
    137137<set identifier="isocat.org/datcat" name="isocat"/>
    138 <set identifier="clarin.eu/schema/ccs-v1.0" name="ccs"/>   
     138<set identifier="http://clarin.eu/fcs/1.0" name="fcs"/>   
    139139
    140140
     
    146146    <index id="?">
    147147      <title lang="en">Words</title>
    148       <map><name set="ccs">word</name></map>
     148      <map><name set="fcs">word</name></map>
    149149    </index>
    150150
    151151    <index id="?">
    152152      <title lang="en">Phonetics</title>
    153       <map><name set="ccs">phonetics</name></map>
     153      <map><name set="fcs">phonetics</name></map>
    154154    </index>         
    155155</indexInfo>
     
    157157
    158158The three indexes that are defined to be searchable on the collections/parts in this endpoint are then: isocat.partOfSpeech, ccs.word, and ccs.phonetics. An example query could for instance be ccs.word = child.
     159Note that the indexes given are completely dynamic, i.e., they can differ from endpoint to endpoint! We have a clear TODO here to agree on a common set of required/desirable indexes!
    159160
    160161The searchable indexes are used as a list in the “searchable tiers  / tier-types” in the user-interface.  It is up to the center to provide a complete list of searchable tier-types (e.g., full-text, transcription, morphological segmentation, part-of-speech annotation, semantic annotation, etc.) or searchable tier-names. We consider it obvious that selectable tier-types trumps tier-names, e.g., “tr1, tr, trans, trans1” as a list is worse than “transcription” as a list. However, if a subdivision of the tiers into tier-types is not available, the tier-names should be provided as the user might be familiar with the corpus and have some use for them.