Changes between Version 60 and Version 61 of Taskforces/FCS/FCS-Specification-Draft

Timestamp:

06/13/17 11:49:47 (7 years ago)

Author:

Leif-Jöran

Comment:

Adding Advanced ADV Data View Description

Taskforces/FCS/FCS-Specification-Draft

@@ -582 +582 @@
 ||=XML Schema                   =|| [source:FederatedSearch/schema/Core_2/DataView-Advanced.xsd DataView-Advanced.xsd] ([source:FederatedSearch/schema/Core_2/DataView-Advanced.xsd?format=txt download]) ||
 
-{{{
-#!div style="border: 1px solid #000000; font-size: 75%"
-TODO: describe!
-}}}
-
+The ''Advanced (ADV)'' Data View serves as the natual serialization of search results for ''Advanced Search'' queries. The ADV Data View supports structured information in one or more annotation layers. The annotations are streams (ranges) over the signal in a stand-off like format with start and end offsets. The list of `Segment` elements building a stream can be of type `item` for character-based streams or `timestamp` for audio streams (granularity up to 0.001s). The Endpoint is responsible for choosing the proper offsets for the segments. The segments `MUST` be possible to align over all annotation layers. For character streams the recommendation is Unicode Normalization Form ''KC''. Segments `MAY` also have an endpoint specific reference indicated by an URI that could be shown in the Aggregator,e.g. to open an audio player or other viewer with contents from the Search Engine. The list of `Layer` elements contains `Span` elements making references to the segments. A Span inherits the start and end offsets from its segments and contains the actual annotation as its content. It `MAY` also carry information about the original annotation value in an `@alt-value` attribute. The document order of the `Layer` elements define the view order in the Aggregator. Each Layer has a ''Layer Type Identifier'' and a ''Layer Identifier''.  The Endpoint `SHOULD` at least resturn all layers that were referenced in the query. It `MAY` return more layers. The attribute `@highlight` is used to mark Spans as hits. Multiple hit markers are supported and the Aggregator `MAY` display them visually distinct. It is up to the Endpoint to decide what should be marked as a hit, but the recommendation is to mark everything referenced in the query.
+
+{{{#!comment
  - ADV Data View allows to return structured information for Advanced Search queries
  - organized in one or more annotation layers
@@ -604 +602 @@
    - Hit Makers are added by marking Spans as hits (add `@highlight` attribute); multiple hit-makers are supported and Aggregator may display them visually distinct
      - where to add hit markers is up to the endpoint; generally "things" that where referenced in the query should be marked.
-
+}}}
 
 Example: a sentence interpreted as a character stream