Component: Concept

Element: Concept / info

Namespace	http://schemas.google.com/dspl/2010
Annotations	Textual information, such as the name and description of the concept.
Diagram
Type	ConceptInfo
Type hierarchy	Info ConceptInfo
Properties	content: complex
Model	name , description{0,1} , url{0,1} , pluralName{0,1} , totalName{0,1} , synonym*
Children	description, name, pluralName, synonym, totalName, url
Instance	<info> <name>{1,1}</name> <description>{0,1}</description> <url>{0,1}</url> </info>
Source	<xs:element name="info" type="ConceptInfo"> <xs:annotation> <xs:documentation>Textual information, such as the name and description of the concept.</xs:documentation> </xs:annotation> </xs:element>

Element: Concept / topic

Namespace	http://schemas.google.com/dspl/2010
Annotations	A topic the concept is associated with.
Diagram
Properties	content: complex minOccurs: 0 maxOccurs: unbounded
Attributes	QName Type Fixed Default Use Annotation ref xs:QName optional The unique identifier of the topic this concept is associated with. The referenced topic may be defined in the same dataset or externally, i.e., in another dataset. A reference to an external topic must be of the form "prefix:other_topic_id", where "prefix" is the prefix used for the namespace of the external dataset (see XML namespaces).
Source	<xs:element name="topic" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>A topic the concept is associated with.</xs:documentation> </xs:annotation> <xs:complexType> <xs:attribute name="ref" type="xs:QName"> <xs:annotation> <xs:documentation>The unique identifier of the topic this concept is associated with. The referenced topic may be defined in the same dataset or externally, i.e., in another dataset. A reference to an external topic must be of the form "prefix:other_topic_id", where "prefix" is the prefix used for the namespace of the external dataset (see XML namespaces).</xs:documentation> </xs:annotation> </xs:attribute> </xs:complexType> </xs:element>

Element: Concept / type

Namespace	http://schemas.google.com/dspl/2010
Annotations	The data type of the concept. A concept must provide a type declaration or extend another concept. In the case where it's extending a concept, it may also provide a type declaration. The type of the extended concept must be less restrictive than the type of the concept extending it. "Less restrictive than" (LRT) is a partial order defined as follows: string LRT float float LRT integer string LRT date string LRT boolean
Diagram
Properties	content: complex minOccurs: 0
Attributes	QName Type Fixed Default Use Annotation ref DataType required
Source	<xs:element name="type" minOccurs="0"> <xs:annotation> <xs:documentation>The data type of the concept. A concept must provide a type declaration or extend another concept. In the case where it's extending a concept, it may also provide a type declaration. The type of the extended concept must be less restrictive than the type of the concept extending it. "Less restrictive than" (LRT) is a partial order defined as follows: string LRT float float LRT integer string LRT date string LRT boolean</xs:documentation> </xs:annotation> <xs:complexType> <xs:attribute name="ref" type="DataType" use="required"/> </xs:complexType> </xs:element>

Element: Concept / attribute

Namespace	http://schemas.google.com/dspl/2010
Annotations	An attribute of the concept. Attributes represent additional information about the concept (e.g., GDP is a percentage).
Diagram
Type	Attribute
Properties	content: complex minOccurs: 0 maxOccurs: unbounded
Model	info{0,1} , type{0,1} , (value* | conceptValue{0,1})
Children	conceptValue, info, type, value
Instance	<attribute concept="" id=""> <info>{0,1}</info> <type format="" ref="">{0,1}</type> </attribute>
Attributes	QName Type Fixed Default Use Annotation concept xs:QName optional A reference to a concept that corresponds to the values of the attribute. If the attribute specifies a type, then the type must match the type of the referenced concept. A reference to an external concept must be of the form "prefix:other_concept_id", where "prefix" is the prefix used for the namespace of the external dataset (see XML namespaces). id LocalId optional The id of the concept attribute. This identifier must be unique within the concept (across attributes and properties). The id may be omitted if the concept attribute is specified. In that case, an id is implicity created with value the local name of the referenced concept. For instance <attribute concept="unit:currency"/> is equivalent to <attribute id="currency" concept="unit:currency"/>
Source	<xs:element name="attribute" type="Attribute" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>An attribute of the concept. Attributes represent additional information about the concept (e.g., GDP is a percentage).</xs:documentation> </xs:annotation> </xs:element>

Element: Concept / property

Namespace	http://schemas.google.com/dspl/2010
Annotations	A property of the concept. Properties represent additional information about instances of the concept (e.g., a concept "city" may have a property "country").
Diagram
Type	ConceptProperty
Properties	content: complex minOccurs: 0 maxOccurs: unbounded
Model	info{0,1} , type{0,1}
Children	info, type
Instance	<property concept="" id="" isMapping="false" isParent="false"> <info>{0,1}</info> <type ref="">{0,1}</type> </property>
Attributes	QName Type Fixed Default Use Annotation concept xs:QName optional A reference to a concept that corresponds to the values of the property. If the property specifies a type, then the type must match the type of the referenced concept. A reference to an external concept must be of the form "prefix:other_concept_id", where "prefix" is the prefix used for the namespace of the external dataset (see XML namespaces). id LocalId optional The id of the concept property. This identifier must be unique within the concept (across attributes and properties). The id may be omitted if the concept property is specified. In that case, an id is implicitly created with value the local name of the referenced concept. For instance <property concept="geo:country"/> is equivalent to <property id="country" concept="geo:country"/> isMapping xs:boolean false optional If true, then this property must reference a concept, and this property denotes a mapping (1-to-1) relationship between this concept and the referenced concept. Each instance of the referenced concept is referenced by at most one instance of this concept. isParent xs:boolean false optional If true, then this property must reference a concept, and this property denotes a hierarchical relationship between this concept and the referenced concept (e.g., the continent of a country).
Source	<xs:element name="property" type="ConceptProperty" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>A property of the concept. Properties represent additional information about instances of the concept (e.g., a concept "city" may have a property "country").</xs:documentation> </xs:annotation> </xs:element>

Element: Concept / defaultValue

Namespace	http://schemas.google.com/dspl/2010
Annotations	A default value for the concept, to be used by applications when they need to pick one of the possible values of the concept.
Diagram
Type	Values
Properties	content: complex minOccurs: 0
Model	value* | conceptValue{0,1}
Children	conceptValue, value
Instance	<defaultValue> <value lang="">{0,unbounded}</value> <conceptValue concept="">{0,1}</conceptValue> </defaultValue>
Source	<xs:element name="defaultValue" type="Values" minOccurs="0"> <xs:annotation> <xs:documentation>A default value for the concept, to be used by applications when they need to pick one of the possible values of the concept.</xs:documentation> </xs:annotation> </xs:element>

Element: Concept / table

Namespace	http://schemas.google.com/dspl/2010
Annotations	A reference to a table that contains all the possible values for the concept and its non-constant properties.
Diagram
Type	ConceptTableMapping
Properties	content: complex minOccurs: 0
Model	mapConcept{0,1} , mapProperty*
Children	mapConcept, mapProperty
Instance	<table ref=""> <mapConcept toColumn="">{0,1}</mapConcept> <mapProperty lang="" ref="" toColumn="">{0,unbounded}</mapProperty> </table>
Attributes	QName Type Fixed Default Use Annotation ref LocalId required The id of the table that contains data for the concept.
Source	<xs:element name="table" type="ConceptTableMapping" minOccurs="0"> <xs:annotation> <xs:documentation>A reference to a table that contains all the possible values for the concept and its non-constant properties.</xs:documentation> </xs:annotation> </xs:element>

Complex Type: Concept

Namespace	http://schemas.google.com/dspl/2010
Annotations	A concept is a definition of a type of data that appears in the dataset (e.g., "GDP" or "County"). A concept may be associated with an enumeration of all its possible values or not. A concept defined in some dataset may be referenced in other datasets.
Diagram
Used by	Element dspl/concepts/concept
Model	info , topic* , type{0,1} , attribute* , property* , defaultValue{0,1} , table{0,1}
Children	attribute, defaultValue, info, property, table, topic, type
Attributes	QName Type Fixed Default Use Annotation extends xs:QName optional The unique identifier of a concept that this concept extends. The referenced concept may be defined in the same dataset or externally, i.e., in another dataset. A reference to an external concept must be of the form "prefix:other_concept_id", where "prefix" is the prefix used for the namespace of the external dataset (see XML namespaces). id Id required The unique identifier of the concept, which must be globally unique within the dataset.
Source	<xs:complexType name="Concept"> <xs:annotation> <xs:documentation>A concept is a definition of a type of data that appears in the dataset (e.g., "GDP" or "County"). A concept may be associated with an enumeration of all its possible values or not. A concept defined in some dataset may be referenced in other datasets.</xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="info" type="ConceptInfo"> <xs:annotation> <xs:documentation>Textual information, such as the name and description of the concept.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="topic" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>A topic the concept is associated with.</xs:documentation> </xs:annotation> <xs:complexType> <xs:attribute name="ref" type="xs:QName"> <xs:annotation> <xs:documentation>The unique identifier of the topic this concept is associated with. The referenced topic may be defined in the same dataset or externally, i.e., in another dataset. A reference to an external topic must be of the form "prefix:other_topic_id", where "prefix" is the prefix used for the namespace of the external dataset (see XML namespaces).</xs:documentation> </xs:annotation> </xs:attribute> </xs:complexType> </xs:element> <xs:element name="type" minOccurs="0"> <xs:annotation> <xs:documentation>The data type of the concept. A concept must provide a type declaration or extend another concept. In the case where it's extending a concept, it may also provide a type declaration. The type of the extended concept must be less restrictive than the type of the concept extending it. "Less restrictive than" (LRT) is a partial order defined as follows: string LRT float float LRT integer string LRT date string LRT boolean</xs:documentation> </xs:annotation> <xs:complexType> <xs:attribute name="ref" type="DataType" use="required"/> </xs:complexType> </xs:element> <xs:element name="attribute" type="Attribute" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>An attribute of the concept. Attributes represent additional information about the concept (e.g., GDP is a percentage).</xs:documentation> </xs:annotation> </xs:element> <xs:element name="property" type="ConceptProperty" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>A property of the concept. Properties represent additional information about instances of the concept (e.g., a concept "city" may have a property "country").</xs:documentation> </xs:annotation> </xs:element> <xs:element name="defaultValue" type="Values" minOccurs="0"> <xs:annotation> <xs:documentation>A default value for the concept, to be used by applications when they need to pick one of the possible values of the concept.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="table" type="ConceptTableMapping" minOccurs="0"> <xs:annotation> <xs:documentation>A reference to a table that contains all the possible values for the concept and its non-constant properties.</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> <xs:attribute name="id" type="Id" use="required"> <xs:annotation> <xs:documentation>The unique identifier of the concept, which must be globally unique within the dataset.</xs:documentation> </xs:annotation> </xs:attribute> <xs:attribute name="extends" type="xs:QName" use="optional"> <xs:annotation> <xs:documentation>The unique identifier of a concept that this concept extends. The referenced concept may be defined in the same dataset or externally, i.e., in another dataset. A reference to an external concept must be of the form "prefix:other_concept_id", where "prefix" is the prefix used for the namespace of the external dataset (see XML namespaces).</xs:documentation> </xs:annotation> </xs:attribute> </xs:complexType>

Attribute: Concept / topic / @ref

Namespace	No namespace
Annotations	The unique identifier of the topic this concept is associated with. The referenced topic may be defined in the same dataset or externally, i.e., in another dataset. A reference to an external topic must be of the form "prefix:other_topic_id", where "prefix" is the prefix used for the namespace of the external dataset (see XML namespaces).
Type	xs:QName
Properties	content: simple
Used by	Element Concept/topic
Source	<xs:attribute name="ref" type="xs:QName"> <xs:annotation> <xs:documentation>The unique identifier of the topic this concept is associated with. The referenced topic may be defined in the same dataset or externally, i.e., in another dataset. A reference to an external topic must be of the form "prefix:other_topic_id", where "prefix" is the prefix used for the namespace of the external dataset (see XML namespaces).</xs:documentation> </xs:annotation> </xs:attribute>

Attribute: Concept / type / @ref

Namespace	No namespace
Type	DataType
Properties	use: required
Facets	enumeration string enumeration float enumeration integer enumeration boolean enumeration date enumeration concept
Used by	Element Concept/type
Source	<xs:attribute name="ref" type="DataType" use="required"/>

Attribute: Concept / @id

Namespace	No namespace
Annotations	The unique identifier of the concept, which must be globally unique within the dataset.
Type	Id
Properties	use: required
Facets	maxLength 64
Used by	Complex Type Concept
Source	<xs:attribute name="id" type="Id" use="required"> <xs:annotation> <xs:documentation>The unique identifier of the concept, which must be globally unique within the dataset.</xs:documentation> </xs:annotation> </xs:attribute>

Attribute: Concept / @extends

Namespace	No namespace
Annotations	The unique identifier of a concept that this concept extends. The referenced concept may be defined in the same dataset or externally, i.e., in another dataset. A reference to an external concept must be of the form "prefix:other_concept_id", where "prefix" is the prefix used for the namespace of the external dataset (see XML namespaces).
Type	xs:QName
Properties	use: optional
Used by	Complex Type Concept
Source	<xs:attribute name="extends" type="xs:QName" use="optional"> <xs:annotation> <xs:documentation>The unique identifier of a concept that this concept extends. The referenced concept may be defined in the same dataset or externally, i.e., in another dataset. A reference to an external concept must be of the form "prefix:other_concept_id", where "prefix" is the prefix used for the namespace of the external dataset (see XML namespaces).</xs:documentation> </xs:annotation> </xs:attribute>

Created using the oXygen XML Editor.