Showing:

Annotations
Attributes
Diagrams
Facets
Model
Properties
Source
Used by
Complex Type ObjectRelationships
Namespace No namespace
Annotations
 
The relationships of the current object to another object. Objects MAY have one or more relationships. Each relationship SHALL point to an object of the same nature. Examples include: datasets can relate to datasets, concepts can relate to concepts, value sets can relate to value sets. Note that relationships are implicit, and unchecked. They are a hint to the reader.
Diagram
DiagramDECOR_xsd_Complex_Type_ObjectRelationships.tmp#ObjectRelationships_typeDECOR_xsd_Complex_Type_ObjectRelationships.tmp#ObjectRelationships_refDECOR_xsd_Complex_Type_ObjectRelationships.tmp#ObjectRelationships_flexibilityDECOR_xsd_Attribute_Group_InheritCompilationAttributes.tmp#InheritCompilationAttributes
Used by
Model
ANY element from ANY namespace
Attributes
QName Type Use Annotation
datasetEffectiveDate optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the dataset effectiveDate for the inherited concept
datasetExpirationDate optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the dataset expirationDate for the original concept
datasetId optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the dataset id for the original concept
datasetStatusCode optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the dataset statusCode for the inherited concept
datasetVersionLabel optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the dataset versionLabel for the original concept
flexibility StaticOrDynamicFlexibility optional 
Reference to the objects @effectiveDate. Default is unspecified which means 'latest available version'.
iEffectiveDate optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the effectiveDate for the inherited concept
iExpirationDate optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the expirationDate for the inherited concept
iStatusCode optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the statusCode for the inherited concept
iType optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the type for the original concept
iVersionLabel optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the versionLabel for the inherited concept
localInherit optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains a boolean for whether or not the relationship 'lives' in the same project or not
originalEffectiveDate optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the concept effectiveDate for the original concept, if the inherited concept was itself an inheriting/containing concept
originalExpirationDate optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the concept expirationDate for the original concept, if the inherited concept was itself an inheriting/containing concept
originalId optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the concept id for the original concept, if the inherited concept was itself an inheriting/containing concept
originalPrefix optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the concept project prefix for the original concept, if the inherited concept was itself an inheriting/containing concept
originalStatusCode optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the concept statusCode for the original concept, if the inherited concept was itself an inheriting/containing concept
originalVersionLabel optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the concept versionLabel for the original concept, if the inherited concept was itself an inheriting/containing concept
prefix optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the project prefix for the original concept
ref BasicIdOrOid required 
Reference to the objects id or name. Note that while reference by name is supported, it is also discouraged and should only be used when the object is not a DECOR object, but still needs referencing.
refdisplay xs:string optional 
Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the calculated display name for the value in @ref
type RelationshipTypes required 
The @type of the relationship, at this point in time something like "SPEC", "GEN", "EQUIV", "VERSION", etc.
Source
 
<xs:complexType name="ObjectRelationships">
  <xs:annotation>
    <xs:documentation xml:lang="en-US">The relationships of the current object to another object. Objects MAY have one or more relationships. Each relationship SHALL point to an object of the same nature. Examples include: datasets can relate to datasets, concepts can relate to concepts, value sets can relate to value sets. Note that relationships are implicit, and unchecked. They are a hint to the reader.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##any" processContents="skip">
      <xs:annotation>
        <xs:documentation xml:lang="en-US">Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains name and description of the referred object in relationship</xs:documentation>
      </xs:annotation>
    </xs:any>
  </xs:sequence>
  <xs:attribute name="type" type="RelationshipTypes" use="required">
    <xs:annotation>
      <xs:documentation xml:lang="en-US">The @type of the relationship, at this point in time something like "SPEC", "GEN", "EQUIV", "VERSION", etc.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="ref" type="BasicIdOrOid" use="required">
    <xs:annotation>
      <xs:documentation xml:lang="en-US">Reference to the objects id or name. Note that while reference by name is supported, it is also discouraged and should only be used when the object is not a DECOR object, but still needs referencing.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="flexibility" type="StaticOrDynamicFlexibility" use="optional">
    <xs:annotation>
      <xs:documentation xml:lang="en-US">Reference to the objects @effectiveDate. Default is unspecified which means 'latest available version'.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <!-- attribute added in compilation -->
  <!--<xs:attribute ref="refdisplay" use="optional"/>-->
  <!-- Only relevant after compilation -->
  <xs:attributeGroup ref="InheritCompilationAttributes"/>
</xs:complexType>
Attribute ObjectRelationships / @type
Namespace No namespace
Annotations
 
The @type of the relationship, at this point in time something like "SPEC", "GEN", "EQUIV", "VERSION", etc.
Type RelationshipTypes
Properties
use required
Facets
enumeration REPL 
This template replaces @template
enumeration SPEC 
This template specializes @template
enumeration GEN 
This template generalizes @template
enumeration COPY 
This template is a design copy of @template
enumeration ADAPT 
This template is an adaptation of @template
enumeration EQUIV 
This template is equivalent to @template regarding design
enumeration VERSION 
This template is a version of @template
enumeration BACKWD 
This template is backward compatible of @template
enumeration DRIV 
For future use: This template is derived from model or other artifact expressed or specified in the @template attribute
Used by
Complex Type ObjectRelationships
Source
 
<xs:attribute name="type" type="RelationshipTypes" use="required">
  <xs:annotation>
    <xs:documentation xml:lang="en-US">The @type of the relationship, at this point in time something like "SPEC", "GEN", "EQUIV", "VERSION", etc.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute ObjectRelationships / @ref
Namespace No namespace
Annotations
 
Reference to the objects id or name. Note that while reference by name is supported, it is also discouraged and should only be used when the object is not a DECOR object, but still needs referencing.
Type BasicIdOrOid
Properties
use required
Used by
Complex Type ObjectRelationships
Source
 
<xs:attribute name="ref" type="BasicIdOrOid" use="required">
  <xs:annotation>
    <xs:documentation xml:lang="en-US">Reference to the objects id or name. Note that while reference by name is supported, it is also discouraged and should only be used when the object is not a DECOR object, but still needs referencing.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Attribute ObjectRelationships / @flexibility
Namespace No namespace
Annotations
 
Reference to the objects @effectiveDate. Default is unspecified which means 'latest available version'.
Type StaticOrDynamicFlexibility
Properties
use optional
Used by
Complex Type ObjectRelationships
Source
 
<xs:attribute name="flexibility" type="StaticOrDynamicFlexibility" use="optional">
  <xs:annotation>
    <xs:documentation xml:lang="en-US">Reference to the objects @effectiveDate. Default is unspecified which means 'latest available version'.</xs:documentation>
  </xs:annotation>
</xs:attribute>
XML Schema documentation generated by ® XML Editor.