ComponentBaseType
- https://purl.semanticip.org/linked-data/sdmx/ML/structure/ComponentBaseType
TTL - owl:Class
- Component Base Type
- http://www.sdmx.org/resources/sdmxml/schemas/v3_1/structure
- structure
- complexType
ComponentBaseType is an abstract type that only serves the purpose of forming the base for the actual ComponentType. It only restricts the format of the id attribute to the NCNameIDType.
- SDMXStructureBase.xsd
<xs:complexType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="ComponentBaseType" abstract="true">
<xs:annotation>
<xs:documentation>ComponentBaseType is an abstract type that only serves the purpose of forming the base for the actual ComponentType. It only restricts the format of the id attribute to the NCNameIDType.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="common:IdentifiableType">
<xs:sequence>
<xs:element ref="common:Annotations" minOccurs="0" />
<xs:element ref="common:Link" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
<xs:attribute name="id" type="common:NCNameIDType" use="optional">
<xs:annotation>
<xs:documentation>The id attribute holds an explicit identification of the component. If this identifier is not supplied, then it is assumed to be the same as the identifier of the concept referenced from the concept identity. Because structures require that every component be given a unique identifier, it may be necessary to assign an explicit identifier when more than one component in a structure reference concepts with same identifier. It is important to note that this applies strictly to the identifier of concept and not the URN. Therefore if two concepts with the same identifier from different concept schemes are referenced in the same structure, one of the components will have to provide a unique explicit identifier. The type of this identifier is restricted to the common:NCNameIDType. This is necessary, since component identifiers are used to create XML elements and attributes in data and metadata structure specific schemas and therefore must be compliant with the NCName type in XML Schema (see common:NCNameIDType for further details).</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:restriction>
</xs:complexContent>
</xs:complexType>rdfs:subClassOf sip-sdmx-ML-common:IdentifiableType ;
rdfs:subClassOf [
a owl:Restriction ;
owl:onProperty sip-sdmx-ML-common:Annotations ;
owl:allValuesFrom xsd:string
] ;
rdfs:subClassOf [
a owl:Restriction ;
owl:onProperty sip-sdmx-ML-common:Annotations ;
owl:maxQualifiedCardinality 1 ;
owl:onDataRange xsd:string
] ;
rdfs:subClassOf [
a owl:Restriction ;
owl:onProperty sip-sdmx-ML-common:Link ;
owl:allValuesFrom xsd:string
] ;
rdfs:subClassOf [
a owl:Restriction ;
owl:onProperty sip-sdmx-ML:id ;
owl:allValuesFrom sip-sdmx-ML-common:NCNameIDType
] ;
rdfs:subClassOf [
a owl:Restriction ;
owl:onProperty sip-sdmx-ML:id ;
owl:maxQualifiedCardinality 1 ;
owl:onDataRange sip-sdmx-ML-common:NCNameIDType
] ;