PhysicalSegmentLocation¶

Fully qualified class name: DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalSegmentLocation

Definition¶

Location of a data point in a physical segment.

Examples¶

A segment of text in a plain text file beginning at character 3 and ending at character 123. The location of the representation of a variable in a text file.

Explanatory notes¶

While this has no properties or relationships of its own, it is useful as a target of relationships where its extensions may serve. This is an extension point since there are many different ways to describe the location of a segment - character counts, start and end times, etc.

Attributes

Name

Inherited from

Description

Data Type

Multiplicity

Default value

catalogDetails

- own class -

Bundles the information useful for a data catalog entry.

Examples would be creator, contributor, title, copyright, embargo, and license information

A set of information useful for attribution, data discovery, and access. This is information that is tied to the identity of the object. If this information changes the version of the associated object changes.

CatalogDetails

0..1

identifier

- own class -

Identifier for objects requiring short- or long-lasting referencing and management.

Identifier

0..1

Associations

Direction	Association	Description	Multiplicity of PhysicalSegmentLocation	Package of Other Class	Other Class	Multiplicity of other class	Aggregation Kind	Inherited from
to	ValueMapping uses PhysicalSegmentLocation	Uses a physical segment location to describe where in the physical record a segment representing the data point is. This could be, for example, described as a start position and end position value for characters in a text record via the segment by text extension of physical segment location.	0..1	- own package -	ValueMapping	0..*	none	- own class -

Syntax representations / encodings

All syntax representations except the Canonical XMI are provided as reference points for specific implementations, or for use as defaults if sufficient in the form presented.

Canonical XMI

Fragment for the class PhysicalSegmentLocation (entire model as XMI)

<packagedElement xmlns:StandardProfile="http://www.eclipse.org/uml2/5.0.0/UML/Profile/Standard"
                 xmlns:uml="http://www.eclipse.org/uml2/5.0.0/UML"
                 xmlns:xmi="http://www.omg.org/spec/XMI/20131001"
                 xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation"
                 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation"
                 xmi:type="uml:Class">
   <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-ownedComment"
                 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-ownedComment"
                 xmi:type="uml:Comment">
      <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation"/>
      <body>Definition 
============ 
Location of a data point in a physical segment.  

Examples 
========== 
A segment of text in a plain text file beginning at character 3 and ending at character 123. The location of the representation of a variable in a text file.  

Explanatory notes 
=================== 
While this has no properties or relationships of its own, it is useful as a target of relationships where its extensions may serve. This is an extension point since there are many different ways to describe the location of a segment - character counts, start and end times, etc.</body>
   </ownedComment>
   <name>PhysicalSegmentLocation</name>
   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-catalogDetails"
                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-catalogDetails"
                   xmi:type="uml:Property">
      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-catalogDetails-ownedComment"
                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-catalogDetails-ownedComment"
                    xmi:type="uml:Comment">
         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-catalogDetails"/>
         <body>Bundles the information useful for a data catalog entry. 

Examples would be creator, contributor, title, copyright, embargo, and license information

A set of information useful for attribution, data discovery, and access.
This is information that is tied to the identity of the object. If this information changes the version of the associated object changes.</body>
      </ownedComment>
      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-catalogDetails-lowerValue"
                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-catalogDetails-lowerValue"
                  xmi:type="uml:LiteralInteger"/>
      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-catalogDetails-upperValue"
                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-catalogDetails-upperValue"
                  xmi:type="uml:LiteralUnlimitedNatural">
         <value>1</value>
      </upperValue>
      <name>catalogDetails</name>
      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CatalogDetails"/>
   </ownedAttribute>
   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-identifier"
                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-identifier"
                   xmi:type="uml:Property">
      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-identifier-ownedComment"
                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-identifier-ownedComment"
                    xmi:type="uml:Comment">
         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-identifier"/>
         <body>Identifier for objects requiring short- or long-lasting referencing and management.</body>
      </ownedComment>
      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-identifier-lowerValue"
                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-identifier-lowerValue"
                  xmi:type="uml:LiteralInteger"/>
      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-identifier-upperValue"
                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-identifier-upperValue"
                  xmi:type="uml:LiteralUnlimitedNatural">
         <value>1</value>
      </upperValue>
      <name>identifier</name>
      <isID>true</isID>
      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-Identifier"/>
   </ownedAttribute>
</packagedElement>

XML Schema

Fragment for the class PhysicalSegmentLocation (entire XML Schema)

<xs:element name="PhysicalSegmentLocation"
            type="PhysicalSegmentLocationXsdType"
            xml:id="PhysicalSegmentLocation">
  <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalSegmentLocation -->
  <xs:annotation>
    <xs:documentation>Definition 
          ============ 
          Location of a data point in a physical segment.  
          
          Examples 
          ========== 
          A segment of text in a plain text file beginning at character 3 and ending at character 123. The location of the representation of a variable in a text file.  
          
          Explanatory notes 
          =================== 
          While this has no properties or relationships of its own, it is useful as a target of relationships where its extensions may serve. This is an extension point since there are many different ways to describe the location of a segment - character counts, start and end times, etc.</xs:documentation>
  </xs:annotation>
</xs:element>
<xs:complexType name="PhysicalSegmentLocationXsdType"
                xml:id="PhysicalSegmentLocationXsdType">
  <xs:annotation>
    <xs:documentation>Definition 
          ============ 
          Location of a data point in a physical segment.  
          
          Examples 
          ========== 
          A segment of text in a plain text file beginning at character 3 and ending at character 123. The location of the representation of a variable in a text file.  
          
          Explanatory notes 
          =================== 
          While this has no properties or relationships of its own, it is useful as a target of relationships where its extensions may serve. This is an extension point since there are many different ways to describe the location of a segment - character counts, start and end times, etc.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="catalogDetails"
                type="CatalogDetailsXsdType"
                minOccurs="0"
                maxOccurs="1"
                xml:id="PhysicalSegmentLocation-catalogDetails">
      <xs:annotation>
        <xs:documentation>Bundles the information useful for a data catalog entry. 
  
  Examples would be creator, contributor, title, copyright, embargo, and license information
  
  A set of information useful for attribution, data discovery, and access.
  This is information that is tied to the identity of the object. If this information changes the version of the associated object changes.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="identifier"
                type="IdentifierXsdType"
                minOccurs="0"
                maxOccurs="1"
                xml:id="PhysicalSegmentLocation-identifier">
      <xs:annotation>
        <xs:documentation>Identifier for objects requiring short- or long-lasting referencing and management.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>

Ontology (Turtle)

Fragment for the class PhysicalSegmentLocation (main ontology)

# class PhysicalSegmentLocation
# based on the UML class DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalSegmentLocation
cdi:PhysicalSegmentLocation
  a rdfs:Class, owl:Class, ucmis:Class;
  rdfs:label "PhysicalSegmentLocation";
  rdfs:comment "Definition \n============ \nLocation of a data point in a physical segment.  \n\nExamples \n========== \nA segment of text in a plain text file beginning at character 3 and ending at character 123. The location of the representation of a variable in a text file.  \n\nExplanatory notes \n=================== \nWhile this has no properties or relationships of its own, it is useful as a target of relationships where its extensions may serve. This is an extension point since there are many different ways to describe the location of a segment - character counts, start and end times, etc."@en;
  
.

cdi:PhysicalSegmentLocation-catalogDetails
  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
  rdfs:label "catalogDetails";
  rdfs:comment "Bundles the information useful for a data catalog entry. \n\nExamples would be creator, contributor, title, copyright, embargo, and license information\n\nA set of information useful for attribution, data discovery, and access.\nThis is information that is tied to the identity of the object. If this information changes the version of the associated object changes."@en;
  rdfs:domain cdi:PhysicalSegmentLocation;
  rdfs:range cdi:CatalogDetails;
.

cdi:PhysicalSegmentLocation-identifier
  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
  rdfs:label "identifier";
  rdfs:comment "Identifier for objects requiring short- or long-lasting referencing and management."@en;
  rdfs:domain cdi:PhysicalSegmentLocation;
  rdfs:range cdi:Identifier;
.

JSON-LD

Fragment for the class PhysicalSegmentLocation (main JSON-LD)

{
  "@context": [
    {
      "cdi": "http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/",
      "xsd": "http://www.w3.org/2001/XMLSchema#",
      "PhysicalSegmentLocation": "cdi:PhysicalSegmentLocation",
      "catalogDetails": {
        "@id": "cdi:PhysicalSegmentLocation-catalogDetails",
        "@type": "@id",
        "@context": "CatalogDetails.jsonld"
      },
      "identifier": {
        "@id": "cdi:PhysicalSegmentLocation-identifier",
        "@type": "@id",
        "@context": "Identifier.jsonld"
      },
      
      "uses_OF_ValueMapping": {
        "@reverse": "cdi:ValueMapping_uses_PhysicalSegmentLocation",
        "@type": "@id"
      },
      " comment ": "tag:json-should-support-trailing-commas" 
    }
  ],
  "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2024-09-23 21:52:59.",
  "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalSegmentLocation"
}