Conventions for naming things will be added here as needed.
- lowercase starting at http and until reaching the name of the class or property. This part is interchangeable with a short lowercase prefix.
- following the last ‘/’ please use camelCase. For properties the first letter is lowercase. For Classes the first letter is uppercase.
- When using # (hash) everything before the hash is interchangeable with the prefix and should be lower case. After the # please use camelCase.
- Do not use snakecase (this_is_snake_case)
- Do not use uppercase in the part that is replaced by the prefix (bad: http://example.com/resource/Place#Montreal)
- http://example.com/resource/ClassName or ex:ClassName
- http://example.com/resource/ontology#EventClass or exo:EventClass
- http://example.com/resource/ontology#propertyName or exo:propertyName
- http://example.com/extra-words/in-path#ClassName or exwp:ClassName
The following graph names are reserved:
All data must be imported using the Artsdata Databus. When data in imported using the databus, the graphs are automatically names as follows:
- account is a free Artsdata account setup for a specific user to upload data
- group is the general grouping of articats usually around a project or software that produces datasets
- artifact is the dataset name
- version is the version of the dataset
- Valid IRIs
- For the path after the last ‘/’ (front slash), use lowercase letters seperated by dash “-“
- Uppercase characters in scheme names (http) and domain names (example.com)
- Percent-encoding of characters where it is not required by IRI syntax
- Explicitly stated HTTP default port (http://example.com:80/); http://example.com/ is preferable
- Completely empty path in HTTP IRIs (http://example.com); http://example.com/ is preferable