Difference between revisions of "Tpso:Arc"

Latest revision as of 13:58, 20 June 2021

Pattern

This class has been associated with the following pattern:

Subclass Of

Description

An English description of the definition (what distinguishes this sense of the term?).

A tpso:Arc is distinct from the concepts that describe the physical infrastructure in a transportation network. An Arc represents the abstract constraints and attributes that exist independent of the physical characteristics. A tpso:Arc is a kind of Manifestation; it represents an Arc at a specific moment in time. To support a representation of change over time, the same Arc object (an Arc_TimeVariant) have multiple tpso:Arc Manifestations, as depicted in the simplified example below.

<uml> @startuml

title Example Arc Manifestations

object Arc1_t1 object Arc1_t2 object Arc1_TimeVariant

Arc1_TimeVariant --> Arc1_t1 : hasManifestation Arc1_TimeVariant --> Arc1_t2 : hasManifestation

Arc1_t1 : speed = 80kmph Arc1_t2 : speed = 100kmph

@enduml </uml>

Class Diagram Description

In figure "another caption" below, a class diagram illustrates...

Required by Use Case(s)

(why is this specialized definition needed?)

CDM References

What other classes or properties reference this term?

Interface Specification References

This class has been associated with the following interface specification items: ISO 5087-3 City Data Model Transportation Planning

Sources

Sources considered when developing the class:

Status

Approved

Has Subclass(es)

Annotations

Annotation	Value
rdfs:label	test label
rdfs:comment	test comment

Manchester Syntax Specification

Property	Restriction	Value
AccessesComplex	only	Tpso:RoadSegment
HasNetworkComponent	only	Node or Test
AccessesComplex	only	Tpso:Node

Supplementary Figures

Figure	Caption
	test caption 1
	test caption 2

@@ Line 1: / Line 1: @@
-{{Subclass Definition
+{{Class Definition
-|Class Name=Tpso:Arc
+|Description=A tpso:Arc is distinct from the concepts that describe the physical infrastructure in a transportation network. An Arc represents the abstract constraints and attributes that exist independent of the physical characteristics.
-|Subclass Of=Arc
+A tpso:Arc is a kind of [[Manifestation]]; it represents an Arc at a specific moment in time. To support a representation of change over time, the same Arc object (an [[Arc_TimeVariant]]) have multiple [[tpso:Arc]] Manifestations, as depicted in the simplified example below.
-|Namespace=http://ontology.eil.utoronto.ca/cdm/TransportationSystem/
-|Definition=<code>
-subClassOf inverse ([[hasNetworkComponent]]) only [[Network]]
-</code>
-<code>
-subClassOf [[accessesComplex]] only [[TransportationComplex]]
-</code>
-<code>
-subClassOf associatedLinkLength exactly 1 length
-</code>
-<code>
-subClassOf containsArc only Arc
-</code>
-<code>
-subClassOf Manifestation
-</code>
-<code>
-subClassOf supportsMode min 1 Mode
-</code>
-<code>
-subClassOf hasControl only AccessRestriction
-</code>
-<code>
+<uml>
-subClassOf hasFreeFlowSpeed max 1 speed
+@startuml
-</code>
-<code>
+title Example Arc Manifestations
-subClassOf hasLaneCapacity exactly 1 CapacityRate
-</code>
-<code>
+object Arc1_t1
-subClassOf hasLinkCapacity max 1 (quantity and
+object Arc1_t2
-        (value only ((denominator only ('Cardinality Unit'
+object Arc1_TimeVariant
-         and ( inverse ('unit of measure') only ( inverse (value) only (cardinality_of only (defined_by only Arc))))))
-     and ('unit of measure' only (numerator only CardinalityUnitPerTime)))))
-</code>
-<code>
-subClassOf hasNumLanes exactly 1 xsd:integer
-</code>
-<code>
+Arc1_TimeVariant --> Arc1_t1 : hasManifestation
-subClassOf hasPostedSpeed max 1 speed
+Arc1_TimeVariant --> Arc1_t2 : hasManifestation
-</code>
-<code>
-subClassOf hasToll only MonetaryValue
-</code>
-<code>
+Arc1_t1 : speed = 80kmph
-subClassOf hasTTI only TTI
+Arc1_t2 : speed = 100kmph
-</code>
-<code>
-subClassOf hasVDF max 1 quantity
-</code>
-<code>
+@enduml
-subClassOf inMunicipality only Municipality
+</uml>
-</code>
+|Class Diagram Description=In figure "another caption" below, a class diagram illustrates...
-|Description=A tpso:Arc is distinct from the concepts that describe the physical infrastructure in a transportation network. An Arc represents the abstract constraints and attributes that exist independent of the physical characteristics.
+|Interface Specification References=ISO 5087-3 City Data Model Transportation Planning
-|Use Case(s)=Arcs are a key concept (nodes being another) required for transportation planning. Arcs are used as input for routing engines as well as to describe and assess the connectivity of a transportation network(s).
+|Definition Status=Approved
-|Definition Status=Pending Approval
+}}
+{{Annotation Specification
+|Annotation Row={{Annotation Row
+|Annotation=rdfs:label
+|Value=test label
+}}{{Annotation Row
+|Annotation=rdfs:comment
+|Value=test comment
+}}
+}}
+{{Manchester Specification
+|Manchester Row={{Manchester Row
+|Property=AccessesComplex
+|Restriction=only
+|Value=Tpso:RoadSegment
+}}{{Manchester Row
+|Property=HasNetworkComponent
+|Restriction=only
+|Value=Node or Test
+}}{{Manchester Row
+|Property=AccessesComplex
+|Restriction=only
+|Value=Tpso:Node
+}}
+|Property=AccessesComplex
+|Restriction=only
+|Value=TransportationComplex
+}}
+{{Supplementary Figures
+|Figure Row={{Figure Row
+|Figure=Test image arcs.png
+|Caption=test caption 1
+}}{{Figure Row
+|Figure=route_class_diagram.png
+|Caption=test caption 2
+}}
+|Figure=Test image arcs.png,route_class_diagram.png,
+|Caption=test caption
 }}