This is one of InLOC's direct properties.
|property of||LOCdefinition, LOCstructure, LOCassociation, subject, scheme, object|
|note||ids must be unique, and should be as persistent as possible|
In every case, InLOC recommends, but does not require, an HTTP URI for the form of the identifier. For conciseness and clarity for human checking, abbreviations may be introduced using well-known and recognised approaches. For instance: prefixes in Turtle; CURIEs for RDFa.
Within any particular InLOC document, file, package, etc. that is communicated, any one identifier must be given in exactly the same form throughout, with no resolution or expansion necessary to determine equality.
Any LOCstructure or LOCdefinition must only be referred to elsewhere in an InLOC document using its id. If it is desired to represent other identifiers for an element, these must be represented as extraID elements.
- relationships (where the LOCassociation type is always "LOCrel")
- compound properties where the LOCassociation type is "by" (but not for other compound properties).