Difference between revisions of "Tpso:NodePD"
Megankatsumi (talk | contribs) (Created page with "{{Subclass Definition |Class Name=Tpso:NodePD |Subclass Of=Node TimeVariant |Namespace=http://ontology.eil.utoronto.ca/cdm/TransportationSystem/ |Definition=equivalentClass ([...") |
Megankatsumi (talk | contribs) |
||
| Line 1: | Line 1: | ||
{{Subclass Definition | {{Subclass Definition | ||
| − | |||
|Subclass Of=Node TimeVariant | |Subclass Of=Node TimeVariant | ||
|Namespace=http://ontology.eil.utoronto.ca/cdm/TransportationSystem/ | |Namespace=http://ontology.eil.utoronto.ca/cdm/TransportationSystem/ | ||
| Line 12: | Line 11: | ||
|Description=A [[tpso:Node]] is distinct from the concepts that describe the physical infrastructure in a transportation network. A Node represents the abstract constraints and attributes that exist independent of the physical characteristics. | |Description=A [[tpso:Node]] is distinct from the concepts that describe the physical infrastructure in a transportation network. A Node represents the abstract constraints and attributes that exist independent of the physical characteristics. | ||
The tpso:NodePD class allows for the representation of an individual object that is subject to change, and thus has multiple manifestations (instances of [[tpso:Node]]) over time that instantiate these changes. | The tpso:NodePD class allows for the representation of an individual object that is subject to change, and thus has multiple manifestations (instances of [[tpso:Node]]) over time that instantiate these changes. | ||
| + | |Required by Use Cases=Routes for Transportation Planning Travel Demand | ||
| + | |Definition Status=Pending Approval | ||
| + | |Class Name=Tpso:NodePD | ||
|Use Case(s)=Nodes are a key concept (arcs being another) required for transportation planning. Nodes are used to define Arcs in more detail in terms of their start and end and connection to other Arcs. They are used as input for routing engines as well as to describe and assess the connectivity of a transportation network(s). | |Use Case(s)=Nodes are a key concept (arcs being another) required for transportation planning. Nodes are used to define Arcs in more detail in terms of their start and end and connection to other Arcs. They are used as input for routing engines as well as to describe and assess the connectivity of a transportation network(s). | ||
| − | |||
}} | }} | ||
Latest revision as of 19:28, 25 May 2020
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:Node is distinct from the concepts that describe the physical infrastructure in a transportation network. A Node represents the abstract constraints and attributes that exist independent of the physical characteristics. The tpso:NodePD class allows for the representation of an individual object that is subject to change, and thus has multiple manifestations (instances of tpso:Node) over time that instantiate these changes.
Class Diagram Description
Required by Use Case(s)
(why is this specialized definition needed?) Routes for Transportation Planning Travel Demand
CDM References
What other classes or properties reference this term?
Interface Specification References
This class has been associated with the following interface specification items:
Sources
Sources considered when developing the class:
Status
Pending Approval
Has Subclass(es)