Slot: id_prefixes
An allowed list of prefixes for which identifiers must conform. The identifier of this class or slot must begin with the URIs referenced by this prefix
URI: linkml:id_prefixes
Alias: id_prefixes
Applicable Classes
| Name |
Description |
Modifies Slot |
| EnumDefinition |
an element whose instances must be drawn from a specified set of permissible ... |
no |
| ClassDefinition |
an element whose instances are complex objects that may have slot-value assig... |
no |
| TypeDefinition |
an element that whose instances are atomic scalar values that can be mapped t... |
no |
| SlotDefinition |
an element that describes how instances are related to other instances |
no |
| Definition |
abstract base class for core metaclasses |
no |
| SubsetDefinition |
an element that can be used to group other metamodel elements |
no |
| SchemaDefinition |
A collection of definitions that make up a schema or a data model |
no |
| Element |
A named element in the model |
no |
Properties
Type and Range
Cardinality and Requirements
| Property |
Value |
| Multivalued |
Yes |
In Subsets
- Order of elements may be used to indicate priority order
- If identifiers are treated as CURIEs, then the CURIE must start with one of the indicated prefixes followed by
: (should start if the list is open)
- If identifiers are treated as URIs, then the URI string must start with the expanded for of the prefix (should start if the list is open)
See Also
Schema Source
Mappings
| Mapping Type |
Mapped Value |
| self |
linkml:id_prefixes |
| native |
linkml:id_prefixes |
LinkML Source
name: id_prefixes
description: An allowed list of prefixes for which identifiers must conform. The identifier
of this class or slot must begin with the URIs referenced by this prefix
comments:
- Order of elements may be used to indicate priority order
- If identifiers are treated as CURIEs, then the CURIE must start with one of the
indicated prefixes followed by `:` (_should_ start if the list is open)
- If identifiers are treated as URIs, then the URI string must start with the expanded
for of the prefix (_should_ start if the list is open)
in_subset:
- SpecificationSubset
- BasicSubset
from_schema: https://w3id.org/linkml/meta
see_also:
- https://github.com/linkml/linkml-model/issues/28
rank: 1000
domain: element
alias: id_prefixes
domain_of:
- element
range: ncname
multivalued: true