Changes between Version 15 and Version 16 of FCS-specification
- Timestamp:
- 04/18/12 10:35:20 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FCS-specification
v15 v16 136 136 <indexInfo> 137 137 <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"/> 139 139 140 140 … … 146 146 <index id="?"> 147 147 <title lang="en">Words</title> 148 <map><name set=" ccs">word</name></map>148 <map><name set="fcs">word</name></map> 149 149 </index> 150 150 151 151 <index id="?"> 152 152 <title lang="en">Phonetics</title> 153 <map><name set=" ccs">phonetics</name></map>153 <map><name set="fcs">phonetics</name></map> 154 154 </index> 155 155 </indexInfo> … … 157 157 158 158 The 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. 159 Note 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! 159 160 160 161 The 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.