Changes between Version 4 and Version 5 of FCS/Specification


Ignore:
Timestamp:
07/09/14 13:48:30 (10 years ago)
Author:
Dieter Van Uytvanck
Comment:

fixed typo in custom extension namespace URIs

Legend:

Unmodified
Added
Removed
Modified

  • FCS/Specification

    v4 v5  
    440440Endpoints can add custom extensions, i.e. custom data, to the Result Format. This extension mechanism can for example be used to provide hints for an (XSLT/XQuery) application that works directly on CLARIN-FCS, e.g. to allow it to generate back and forward links to navigate in a result set.
    441441
    442 An Endpoint `MAY` add arbitrary XML fragments to the extension hooks provided in the `<fcs:Resource>` element (see the XML schema for "Resource.xsd"). The XML fragment for the extension `MUST` use a custom XML namespace name for the extension. Endpoints `MUST NOT` use XML namespace names that start with the prefixes `http://clarin.eu`, `http://www.clarin.eu/`, `https://clarin.eu` or `http://www.clarin.eu/`.
     442An Endpoint `MAY` add arbitrary XML fragments to the extension hooks provided in the `<fcs:Resource>` element (see the XML schema for "Resource.xsd"). The XML fragment for the extension `MUST` use a custom XML namespace name for the extension. Endpoints `MUST NOT` use XML namespace names that start with the prefixes `http://clarin.eu`, `http://www.clarin.eu/`, `https://clarin.eu` or `https://www.clarin.eu/`.
    443443
    444444A Client `MUST` ignore any custom extensions it does not understand and skip over these XML fragments when parsing the Endpoint's response.