Texts
Texts can roughly be defined as cohesive stretches of discourse in the object language. They are part of the Boasian trilogy, and fundamental to corpus-based language description.
In CLDF, it can be conceptualized as a list of Examples[^1]: the Text_ID column references the text, and two more columns (called Sentence_Number and Phrase_Number in lapollaqiang) store its position in the text.
The properties below should mostly be self-explanatory.
Type is intended to hold genres like 'personal narrative' or 'conversation'.
Metadata is a JSON field for things like tags, duration, etc.
[^1]: Of course, they only become examples when they are used as such, but this misnomer is not significant.
TextTable: texts.csv
| Name/Property | Datatype | Cardinality | Description |
|---|---|---|---|
| ID | string |
A unique identifier for a row in a table. To allow usage of identifiers as path components of URLs IDs must only contain alphanumeric characters, underscore and hyphen. Primary key |
|
| Name | string |
A title, name or label for an entity. |
|
| Description | string |
A description for an entity. |
|
| Comment | string |
A human-readable comment on a resource, providing additional context. |
|
| Source | list of string (separated by ;) |
List of source specifications, of the form <source_ID>[], e.g. http://glottolog.org/resource/reference/id/318814[34], or meier2015[3-12] where meier2015 is a citation key in the accompanying BibTeX file. |
|
Type |
string |
||
Metadata |
json |