Just store changes

README.md

@@ -4,12 +4,12 @@ This repo contains AsciiDoc sources, images, examples and schema files for the C
 
 ## Specification Documents
 
-* [CLARIN Federated Content Search - FCS **Core 2.0**: `fcs-core-2.0/index.adoc`](fcs-core-2.0/index.adoc)
-* [CLARIN Federated Content Search - FCS **Core 1.0**: `fcs-core-1.0/index.adoc`](fcs-core-1.0/index.adoc)
-* [CLARIN Federated Content Search - FCS **Data Views 1.0**: `fcs-dataviews-1.0/index.adoc`](fcs-dataviews-1.0/index.adoc)
-* _WIP_ [CLARIN Federated Content Search - FCS **AAI 1.0**: `fcs-aai/index.adoc`](fcs-aai/index.adoc)
+- [CLARIN Federated Content Search - FCS **Core 2.0**: `fcs-core-2.0/index.adoc`](fcs-core-2.0/index.adoc)
+- [CLARIN Federated Content Search - FCS **Core 1.0**: `fcs-core-1.0/index.adoc`](fcs-core-1.0/index.adoc)
+- [CLARIN Federated Content Search - FCS **Data Views 1.0**: `fcs-dataviews-1.0/index.adoc`](fcs-dataviews-1.0/index.adoc)
+- _WIP_ [CLARIN Federated Content Search - FCS **AAI 1.0**: `fcs-aai/index.adoc`](fcs-aai/index.adoc)
 
-### Folder structure
+### Folder Structure
 
 All the specification documents are structured as follows in their sub folders:
 - `index.adoc` -- AsciiDoc entrypoint document that bundles and includes single chapters into one
@@ -55,6 +55,12 @@ docker run --rm -it -v $(pwd):/documents asciidoctor/docker-asciidoctor
 # then run your build commands
 ```
 
+## Tutorial Documents
+
+* [CLARIN Federated Content Search - FCS **Endpoint Developer's Tutorial**: `fcs-endpoint-dev-tutorial/index.adoc`](fcs-endpoint-dev-tutorial/index.adoc)
+
+For build instructions, see section [Specification Documents "How to build"](#how-to-build).
+
 ## Historical Resources
 
 To be found under [`historical/`](historical/):

fcs-endpoint-dev-tutorial/index.adoc

@@ -1,5 +1,5 @@
 = FCS 2.0 Endpoint Developer's Tutorial
-Oliver Schonefeld <schonefeld@ids-mannheim.de>; Erik Körner <koerner@saw-leipzig.de>
+Oliver Schonefeld <schonefeld@ids-mannheim.de>; Leif-Jöran Olsson <leif-joran[email protected]>; Erik Körner <koerner@saw-leipzig.de>
 v1.0, 2016-01
 // more metadata
 :description: This is a tutorial on how to develop CLARIN FCS endpoints.

fcs-endpoint-dev-tutorial/java/configuration.adoc

@@ -65,7 +65,7 @@ Makes sure capabilities and declared dataviews actually match otherwise it will
 * Supported Layers, checks that `<SupportedLayer>` elements have:
 
 ** a proper `@id` attribute and that the value is unique.
-** a proper `@result-id` attribute and that is is encoded as a proper URI, ant that the child text node is "text", "lemma", "pos", "orth", "norm", "phonetic", or other value starting with "x-".
+** a proper `@result-id` attribute and that is is encoded as a proper URI, and that the child text node is "text", "lemma", "pos", "orth", "norm", "phonetic", or other value starting with "x-".
 ** if a `@alt-value-info-uri` attribute that is encoded as proper URI, e.g. tag description
 ** if _advanced search_ is given in capabilities that it is also available.