PhysicalSegmentLocation#
Fully qualified class name of the UML model DDI-CDI 1.0: 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.
Diagram#
Diagram
Inheritance#
Inheritance
FormatDescription::PhysicalSegmentLocation
Attributes#
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. |
0..1 |
||
identifier |
- own class - |
Identifier for objects requiring short- or long-lasting referencing and management. |
0..1 |
Associations#
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 - |
0..* |
none |
own class |
Encodings#
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.
Fragment for the class PhysicalSegmentLocation (entire model as XMI)
1<packagedElement xmlns:StandardProfile="http://www.omg.org/spec/UML/20131001/StandardProfile"
2 xmlns:uml="http://www.omg.org/spec/UML/20131001"
3 xmlns:xmi="http://www.omg.org/spec/XMI/20131001"
4 xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation"
5 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation"
6 xmi:type="uml:Class">
7 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-ownedComment"
8 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-ownedComment"
9 xmi:type="uml:Comment">
10 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation"/>
11 <body>Definition
12============
13Location of a data point in a physical segment.
14
15Examples
16==========
17A 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.
18
19Explanatory notes
20===================
21While 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>
22 </ownedComment>
23 <name>PhysicalSegmentLocation</name>
24 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-catalogDetails"
25 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-catalogDetails"
26 xmi:type="uml:Property">
27 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-catalogDetails-ownedComment"
28 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-catalogDetails-ownedComment"
29 xmi:type="uml:Comment">
30 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-catalogDetails"/>
31 <body>Bundles the information useful for a data catalog entry.
32
33Examples would be creator, contributor, title, copyright, embargo, and license information
34
35A set of information useful for attribution, data discovery, and access.
36This is information that is tied to the identity of the object. If this information changes the version of the associated object changes.</body>
37 </ownedComment>
38 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-catalogDetails-lowerValue"
39 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-catalogDetails-lowerValue"
40 xmi:type="uml:LiteralInteger"/>
41 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-catalogDetails-upperValue"
42 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-catalogDetails-upperValue"
43 xmi:type="uml:LiteralUnlimitedNatural">
44 <value>1</value>
45 </upperValue>
46 <name>catalogDetails</name>
47 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CatalogDetails"/>
48 </ownedAttribute>
49 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-identifier"
50 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-identifier"
51 xmi:type="uml:Property">
52 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-identifier-ownedComment"
53 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-identifier-ownedComment"
54 xmi:type="uml:Comment">
55 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-identifier"/>
56 <body>Identifier for objects requiring short- or long-lasting referencing and management.</body>
57 </ownedComment>
58 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-identifier-lowerValue"
59 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-identifier-lowerValue"
60 xmi:type="uml:LiteralInteger"/>
61 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-FormatDescription-PhysicalSegmentLocation-identifier-upperValue"
62 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#PhysicalSegmentLocation-identifier-upperValue"
63 xmi:type="uml:LiteralUnlimitedNatural">
64 <value>1</value>
65 </upperValue>
66 <name>identifier</name>
67 <isID>true</isID>
68 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-Identifier"/>
69 </ownedAttribute>
70</packagedElement>
Fragment for the class PhysicalSegmentLocation (entire XML Schema)
1<xs:element name="PhysicalSegmentLocation"
2 type="PhysicalSegmentLocationXsdType"
3 xml:id="PhysicalSegmentLocation">
4 <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalSegmentLocation -->
5 <xs:annotation>
6 <xs:documentation>Definition
7 ============
8 Location of a data point in a physical segment.
9
10 Examples
11 ==========
12 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.
13
14 Explanatory notes
15 ===================
16 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>
17 </xs:annotation>
18</xs:element>
19<xs:complexType name="PhysicalSegmentLocationXsdType"
20 xml:id="PhysicalSegmentLocationXsdType">
21 <xs:annotation>
22 <xs:documentation>Definition
23 ============
24 Location of a data point in a physical segment.
25
26 Examples
27 ==========
28 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.
29
30 Explanatory notes
31 ===================
32 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>
33 </xs:annotation>
34 <xs:sequence>
35 <xs:element name="catalogDetails"
36 type="CatalogDetailsXsdType"
37 minOccurs="0"
38 maxOccurs="1"
39 xml:id="PhysicalSegmentLocation-catalogDetails">
40 <xs:annotation>
41 <xs:documentation>Bundles the information useful for a data catalog entry.
42
43 Examples would be creator, contributor, title, copyright, embargo, and license information
44
45 A set of information useful for attribution, data discovery, and access.
46 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>
47 </xs:annotation>
48 </xs:element>
49 <xs:element name="identifier"
50 type="IdentifierXsdType"
51 minOccurs="0"
52 maxOccurs="1"
53 xml:id="PhysicalSegmentLocation-identifier">
54 <xs:annotation>
55 <xs:documentation>Identifier for objects requiring short- or long-lasting referencing and management.</xs:documentation>
56 </xs:annotation>
57 </xs:element>
58 </xs:sequence>
59</xs:complexType>
Fragment for the class PhysicalSegmentLocation (entire JSON Schema)
1"cls-PhysicalSegmentLocation": {
2 "description": "http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/PhysicalSegmentLocation",
3 "type": "object",
4 "properties": {
5 "@context": {
6 "$ref": "#/defs/at-context"
7 },
8 "@id": {
9 "type": "string",
10 "format": "iri-reference"
11 },
12 "@type": {
13 "const": "PhysicalSegmentLocation"
14 },
15 "catalogDetails": {
16 "$comment": "cardinality 0..1 – from cdi:PhysicalSegmentLocation",
17 "$ref": "#/defs/dt-CatalogDetails"
18 },
19 "identifier": {
20 "$comment": "cardinality 0..1 – from cdi:PhysicalSegmentLocation",
21 "$ref": "#/defs/dt-Identifier"
22 },
23
24 "uses_PhysicalSegmentLocation_OF_ValueMapping": {
25 "description": "ValueMapping_uses_PhysicalSegmentLocation",
26 "$comment": "cardinality 0..-1",
27 "anyOf": [
28 {
29 "$ref": "#/defs/target-ValueMapping"
30 },
31 {
32 "type": "array",
33 "items": {
34 "$ref": "#/defs/target-ValueMapping"
35 }
36 }
37 ]
38 },
39 "sameAs": {
40 "$ref": "#/defs/owl:sameAs"
41 }
42 },
43 "required": ["@type"],
44 "additionalProperties": false
45},
46"target-PhysicalSegmentLocation": {
47 "description": "all subclasses of http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/PhysicalSegmentLocation",
48 "anyOf": [
49 { "$ref": "#/defs/cls-PhysicalSegmentLocation" },
50 { "$ref": "#/defs/cls-SegmentByText" },
51 { "type": "string", "format": "iri-reference" }
52 ]
53},
Fragment for the class PhysicalSegmentLocation (main ontology)
1# class PhysicalSegmentLocation
2# based on the UML class DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalSegmentLocation
3cdi:PhysicalSegmentLocation
4 a rdfs:Class, owl:Class, ucmis:Class;
5 rdfs:label "PhysicalSegmentLocation";
6 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;
7
8.
9
10cdi:PhysicalSegmentLocation-catalogDetails
11 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
12 rdfs:label "catalogDetails";
13 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;
14 rdfs:domain cdi:PhysicalSegmentLocation;
15 rdfs:range cdi:CatalogDetails;
16.
17
18cdi:PhysicalSegmentLocation-identifier
19 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
20 rdfs:label "identifier";
21 rdfs:comment "Identifier for objects requiring short- or long-lasting referencing and management."@en;
22 rdfs:domain cdi:PhysicalSegmentLocation;
23 rdfs:range cdi:Identifier;
24.
Fragment for the class PhysicalSegmentLocation (entire JSON-LD)
1{
2 "@context": [
3 {
4 "cdi": "http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/",
5 "xsd": "http://www.w3.org/2001/XMLSchema#",
6
7 "catalogDetails": {
8 "@id": "cdi:PhysicalSegmentLocation-catalogDetails",
9 "@type": "@id",
10 "@context": "CatalogDetails.jsonld"
11 },
12 "identifier": {
13 "@id": "cdi:PhysicalSegmentLocation-identifier",
14 "@type": "@id",
15 "@context": "Identifier.jsonld"
16 },
17
18 "uses_PhysicalSegmentLocation_OF_ValueMapping": {
19 "@reverse": "cdi:ValueMapping_uses_PhysicalSegmentLocation",
20 "@type": "@id",
21 "@context": "ValueMapping.jsonld"
22 },
23 " comment ": "tag:json-should-support-trailing-commas"
24 }
25 ],
26 "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2025-08-29 14:34:53.",
27 "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalSegmentLocation"
28}
Fragment for the class PhysicalSegmentLocation (entire SHACL - Shapes Constraint Language)
1# class PhysicalSegmentLocation
2# based on the UML class DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalSegmentLocation
3<#PhysicalSegmentLocation> a sh:NodeShape;
4 sh:targetClass cdi:PhysicalSegmentLocation;
5 sh:message "See http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/PhysicalSegmentLocation";
6 sh:closed true;
7 sh:ignoredProperties ( owl:sameAs );
8 sh:property [
9 sh:path rdf:type;
10 sh:in ( cdi:PhysicalSegmentLocation
11 cdi:SegmentByText
12 ) ;
13 ];
14 # attributes
15 sh:property <#PhysicalSegmentLocation-catalogDetails>;
16 sh:property <#PhysicalSegmentLocation-identifier>;
17 # associations from PhysicalSegmentLocation
18 # associations to PhysicalSegmentLocation
19 sh:property <#rev_ValueMapping_uses_PhysicalSegmentLocation>;
20
21
22
23.
24
25<#PhysicalSegmentLocation-catalogDetails> a sh:PropertyShape ;
26 sh:path cdi:PhysicalSegmentLocation-catalogDetails;
27 sh:node [ sh:property [ sh:path rdf:type; sh:minCount 1; sh:in (
28 cdi:CatalogDetails
29
30 ) ]];
31 sh:maxCount 1;
32.
33<#PhysicalSegmentLocation-identifier> a sh:PropertyShape ;
34 sh:path cdi:PhysicalSegmentLocation-identifier;
35 sh:node [ sh:property [ sh:path rdf:type; sh:minCount 1; sh:in (
36 cdi:Identifier
37
38 ) ]];
39 sh:maxCount 1;
40.
Fragment for the class PhysicalSegmentLocation (entire ShEx - Shape Expressions)
1# class PhysicalSegmentLocation
2# based on the UML class DDICDIModels::DDICDILibrary::Classes::FormatDescription::PhysicalSegmentLocation
3cdi:PhysicalSegmentLocationShape CLOSED {
4 a [cdi:PhysicalSegmentLocation];
5 $cdi:PhysicalSegmentLocationProperties (
6 cdi:PhysicalSegmentLocation-catalogDetails @cdi:CatalogDetailsShape?;
7 cdi:PhysicalSegmentLocation-identifier @cdi:IdentifierShape?;
8 ^cdi:ValueMapping_uses_PhysicalSegmentLocation @cdi:ValueMappingShape *;
9 );
10}