Changes between Version 6 and Version 7 of FCS-specification

Timestamp:

04/17/12 12:43:56 (12 years ago)

Author:

dietuyt

Comment:

--

FCS-specification

@@ -55 +55 @@
 This is the issue of tag expansion. If “no-expansion” has been chosen, then the query should be taken literally and no available relations should be used. If “expansion” has been chosen then relations should be used. We argue that that expansion of the tag to all locally applicable tags by making use of RELcat  should happen locally at the endpoint. After all, endpoints are meant to be used programmatically by many clients, not just our demonstrator. It’s the local repository who best understand how things can be extended in a useful way. Having only the relevant expansion happen at the endpoint would make using them in infrastructures easier and more attractive..
 
+== Technical details aggregator ==
+
+=== Input for the aggregator ===
+
+
+
+=== Referring to an SRU endpoint from a CMDI file ===
+
+This can be done with a ResourceProxy where:
+ * ResourceType = Resource
+ * mimetype = application/sru+xml
+
+{{{#!xml
+ <ResourceProxy id="d55">
+   <ResourceType mimetype="application/sru+xml">Resource</ResourceType>
+   <ResourceRef>http://cqlservlet.mpi.nl/</ResourceRef>
+ </ResourceProxy>
+}}}
+
+For a complete example file see: http://www.clarin.eu/cmd/example/example-cgn-sru.cmdi
+
 == Return format ==
 We have defined the use of several return formats.
@@ -74 +95 @@
 === Explain ===
 
-This basic request serves to announce server's capabilities and should allow the client to configure itself automatically. The explain response should, ideally, provide a list of ISOcatted indexes as possible search indexes. If there is no ISOcat equivalent the ccs-context set is to be used. We provide a telling example (as seen within the context of the explain response as defined on the SRU/CQL website):
+This basic request serves to announce server's capabilities and should allow the client to configure itself automatically. The explain response should, ideally, provide a list of ISOcatted indexes as possible search indexes. If there is no ISOcat equivalent the CCS-context*  set is to be used. We provide a telling example (as seen within the context of the explain response as defined on the SRU/CQL website):
 
 {{{#!xml