Changeset 4650
- Timestamp:
- 03/07/14 15:15:44 (10 years ago)
- Location:
- cats/SCHEMAcat/trunk/data/schemata
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
cats/SCHEMAcat/trunk/data/schemata/s13/index.schemacat
r4638 r4650 3 3 <sc:name>avatech-multitier</sc:name> 4 4 <sc:version/> 5 <sc:description>Schema for an AVATecH multitier file, which allows to use independent 6 segmentations in different tiers within a single XML file. In a single tier format, it is 7 possible to store multiple tiers, but with only one time segmentation which had to be shared by 8 all tiers.each item describes a timespan, with start time and end time. Times in each tier item 9 have to be in ascending order and the timespans must not overlap. They can, however, be back to 10 back. Content can be free text, numerical values, text using a controlled vocabulary or similar. 11 Of course all spans must provide values (v) for all columns and the values must be given in the 12 same order as specified in the columns header attribute.</sc:description> 5 <sc:description>Schema for an AVATecH multitier file, which allows to use independent segmentations in different tiers within a single XML file. In a single tier format, it is possible to store multiple tiers, but with only one time segmentation which had to be shared by all tiers.each item describes a timespan, with start time and end time. Times in each tier item 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> 13 6 <sc:status>development</sc:status> 14 7 <sc:pid/> -
cats/SCHEMAcat/trunk/data/schemata/s5/index.schemacat
r4641 r4650 4 4 <sc:version/> 5 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 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> 7 7 <sc:status>production</sc:status> 8 8 <sc:tag type="group">AVATecH</sc:tag>
Note: See TracChangeset
for help on using the changeset viewer.