Changes between Version 32 and Version 33 of FCS-spec

Timestamp:

06/05/11 10:40:31 (13 years ago)

Author:

vronk

Comment:

added alternative SearchResult?-format

FCS-spec

@@ -63 +63 @@
         /* this is for metadata provided directly by the content provider 
          * NOT the CMD  metadata.  */
-      <ccs:f key="{any metadata-key}">{any metadata value}</ccs:f>
+      <ccs:f key="{any metadata-key}">{any metadata value}</ccs:f> /* is this any useful? */
+        /* or rather direct metadata-fields like: */
+       <dc:title></dc:title>
+       <dc:author></dc:author>
+       ....
     </ccs:Metadata>
     <ccs:ResourceFragment pid="{offset relative to the parent resource PID}“>           
@@ -69 +73 @@
        </ccs:Metadata>
 
+      <ccs:DataView type="kwic">Some text with <kw>keyword</kw> highlighted</ccs:DataView>              
+    
       <ccs:DataView type="text/xml"><meertens:any/>     
       </ccs:DataView>           
@@ -95 +101 @@
   It can carry an optional parameter `cmd-link` with the PID of a CMD-record. (This only makes sense for `Resource/Metadata`)
 
+  Although the original idea was to "serialize" all such metadata-fields in a `<f key="{field-name}">`-element, I now prefer reusing existing namespaces. 
+
+  `<dc:title>` seems preferable to `<f key="dc:title">`, right?
+
+However this nested approach seems not directly compatible with the established SRU-based systems, that rather work on flat fields.
+And while this can be overcome by providing converter XSL-stylesheets, the information we need seems expressable in a flat structure as well, that makes the more complex (nested) approach questionable:
+
+{{{
+<sru:recordData>
+   <ccs:ResourcePID>{PID of the resource}</ccs:ResourcePID> 
+   <ccs:ResourceFragmentPID>{identifier of the resource-fragment (relative to Resource-PID?)}</ccs:ResourcePID> 
+   <ccs:CMDPID>{PID of the CMD-record}</ccs:CMDPID>  /* optional */
+
+   <dc:title>{title of the resource}</dc:title>  
+     /* basically any metadata-fields as is standard in SRU-world */
+   ... 
+  
+   <ccs:DataView type="kwic">Some text with <kw>keyword</kw> highlighted</ccs:DataView>         
+   <ccs:DataView type="text/xml"><meertens:any/>     
+    </ccs:DataView>             
+   <ccs:DataView type="image/jpeg" href="{optional link  to the data}" ></ccs:DataView>  
+</sru:recordData>
+}}}
+
 
 === Data Views ===