cd
cd copied to clipboard
tdwg
Decide and document how data types are used wrt LtC
Data types - audience first, then specificity on how it should be used If not intended to be restrictive/validatable format, provide usage If it is / For machine, need to accommodate for implementation-language E.g. Date = string + format on top in json-schema = primitive data type in xsd (https://www.w3.org/TR/xmlschema-2/#built-in-primitive-datatypes)
Note - w3c standard from meeting: https://www.w3.org/TR/xmlschema-2/#scope
From Ben Norton:
Here's an extended set if data type definitions that are based on json schema.
Data Type Definition
enumerated A list of predefined values
Integer Numeric values without decimal places that range 32 bits from -2^31 to 2^31.
float Double-precision floating-point numbers with up to 17 significant digits
boolean Values that may be represented by a binary data set (true/false, 1/0) and stored as 1 bit. Properties with boolean data types may not be null.
date A value that contains a date (without time) that conforms to ISO 8601 and follows the format YYYY-MM-DD
datetime A value that contains a single date and time that conforms to ISO 8601 and follows the format YYYY-MM-DD HH:MM:SS
string String values may contain letters, numbers, puncutation mark, or symbols (including whitespaces). Text values are also referred to as literals, strings, or varchar. Text values are limited to 255 characters except where explicitly denotted otherwise. Text values may be subject to specific formats (character patterns) or set of valid characters.
datatypes currently used in the the termlist: https://json-schema.org/draft/2020-12/json-schema-core.html#name-instance-data-model
Data types are a level of specificity above the bag of terms in a TDWG standard. As a result, data types are not included in the core documentation files. A separate effort to standardize data types across TDWG is in progress as part of a larger set of TDWG recommendations. I recommend tabling this task for now until that effort is complete.
