Changes between Version 1 and Version 2 of FCS-specification
- Timestamp:
- 04/11/12 08:15:31 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FCS-specification
v1 v2 24 24 = Global Design Thoughts / The Aggregator = 25 25 26 == Overview==26 == Overview == 27 27 28 28 The design of the federated search system consists of two major parts: … … 42 42 2 Those CMDI records should contain a unique identifier. 43 43 3 The endpoints need to understand their own, corresponding unique identifiers. 44 44 45 == Queries == 45 46 … … 149 150 Below we also cover a second topic related to the searchRetrieve operation, the expansion of search queries. 150 151 151 == = Return formats (DataView) ===152 == Return formats (DataView) == 152 153 153 154 There are several dataviews agreed upon. Each dataView will have an attribute “type”, which has as value the type of dataView contained. It is possible to, in the future, add different dataviews if required. It is mandatody to support the KWIC dataview (as this type is fairly straightforward to show as a list of results). … … 170 171 3 TCF: this dataView contains the TCF format as specified for the WEBLICHT program. By having data available in TCF (where applicable) we create a more integrated search architecture, where search results can be further processed in a weblicht toolchain. 171 172 172 == = Query Expansion ===173 == Query Expansion == 173 174 174 175 For many search tasks the problem persists that resources are differently annotated. For instance, in case of sign language data several resources use different encodings for the observed signs and gestures. Regardless, when using a search infrastructure it should be possible to locate all (and only the) relevant examples. … … 180 181 For example the ISOcat category for nouns can be found at the following url: http://www.isocat.org/datcat/DC-1333. 181 182 182 == = Restricting the search ===183 == Restricting the search == 183 184 184 185 It is possible to restrict the search to a list of PIDs that match resources. These are passed in the x-cmd-context parameter. We note that this list can get extensive, however we foresee two ways to deal with this problem.
