Changeset 4641


Ignore:
Timestamp:
03/07/14 10:23:50 (10 years ago)
Author:
andmor
Message:

Fixed indentation in descriptions

Location:
cats/SCHEMAcat/trunk/data/schemata
Files:
5 edited

Legend:

Unmodified
Added
Removed

  • cats/SCHEMAcat/trunk/data/schemata/s1/index.schemacat

    r4637 r4641  
    33  <sc:name>adelheid-charstream</sc:name>
    44  <sc:version/>
    5   <sc:description>Schema for an Adelheid Character Stream document. Such a document consists of a
    6     TEI Header, and a body of character streams for one or more manuscript.</sc:description>
     5  <sc:description>Schema for an Adelheid Character Stream document. Such a document consists of a TEI Header, and a body of character streams for one or more manuscript.</sc:description>
    76  <sc:status>production</sc:status>
    87  <sc:tag type="group">Adelheid</sc:tag>

  • cats/SCHEMAcat/trunk/data/schemata/s12/index.schemacat

    r4637 r4641  
    33  <sc:name>TEI-header</sc:name>
    44  <sc:version>2.1.0</sc:version>
    5   <sc:description>Schema for the TEI Header. This version of the schema is annotated with ISOcat
    6     Data Category references to make the semantics explicit and shareable, e.g., with CLARIN
    7     Component Metadata.</sc:description>
     5  <sc:description>Schema for the TEI Header. This version of the schema is annotated with ISOcat Data Category references to make the semantics explicit and shareable, e.g., with CLARIN Component Metadata.</sc:description>
    86  <sc:status>development</sc:status>
    97  <sc:pid/>

  • cats/SCHEMAcat/trunk/data/schemata/s2/index.schemacat

    r4637 r4641  
    33  <sc:name>adelheid-document</sc:name>
    44  <sc:version/>
    5   <sc:description>Schema for an Adelheid XML document consists of a TEI header followed by a body element,
    6     containing a sequence of manuscript elements. Each manuscript in turn consists of a sequence of
    7     line elements. A line element contains the actual text of each manuscript line.</sc:description>
     5  <sc:description>Schema for an Adelheid XML document consists of a TEI header followed by a body element, containing a sequence of manuscript elements. Each manuscript in turn consists of a sequence of line elements. A line element contains the actual text of each manuscript line.</sc:description>
    86  <sc:status>production</sc:status>
    97  <sc:tag type="group">Adelheid</sc:tag>

  • cats/SCHEMAcat/trunk/data/schemata/s5/index.schemacat

    r4637 r4641  
    33  <sc:name>avatech-timeseries</sc:name>
    44  <sc:version/>
    5   <sc:description>Schema for AVATecH timeseries. There can be one or more values per item, which can
    6     be numerical or text. All items (i) must have the same number of values (v). A columns header
    7     provides titles for the columns, as a space separated string. Numerical columns must have titles
    8     starting with the # character. Of course all items (i) must provide values (v) for all columns
    9     and the values must be given in the same order as specified in the columns header attribute.
    10     Note that any non-numerical string in a numerical field is just treated as not-a-number, the
    11     exact string does not matter.</sc:description>
     5  <sc:description>Schema for AVATecH timeseries. There can be one or more values per item, which can be numerical or text. All items (i) must have the same number of values (v). A columns header provides titles for the columns, as a space separated string. Numerical columns must have titles starting with the # character. Of course all items (i) must provide values (v) for all columns and the values must be given in the same order as specified in the columns header attribute.
     6    Note that any non-numerical string in a numerical field is just treated as not-a-number, the exact string does not matter.</sc:description>
    127  <sc:status>production</sc:status>
    138  <sc:tag type="group">AVATecH</sc:tag>

  • cats/SCHEMAcat/trunk/data/schemata/s6/index.schemacat

    r4637 r4641  
    33  <sc:name>avatech-tier</sc:name>
    44  <sc:version/>
    5   <sc:description>Schema for an AVATecH tier file where each item describes a timespan, with
    6     start time and end time. Item times have to be in ascending order and the timespans must not
    7     overlap. They can, however, be back to back. Content can be free text, numerical values, text
    8     using a controlled vocabulary or similar. Of course all spans must provide values (v) for all
    9     columns and the values must be given in the same order as specified in the columns header
    10     attribute.</sc:description>
     5  <sc:description>Schema for an AVATecH tier file where each item describes a timespan, with start time and end time. Item times have to be in ascending order and the timespans must not overlap. They can, however, be back to back. Content can be free text, numerical values, text using a controlled vocabulary or similar. Of course all spans must provide values (v) for all columns and the values must be given in the same order as specified in the columns header attribute.</sc:description>
    116  <sc:status>production</sc:status>
    127  <sc:tag type="group">AVATecH</sc:tag>
Note: See TracChangeset for help on using the changeset viewer.