This wiki has undergone a migration to Confluence found Here
Difference between revisions of "OO CR051-680 Additional Segment DST in EAC Message"
Jump to navigation
Jump to search
(Additional Segment DST (Destination/Route) in EAC Message) |
Hbuitendijk (talk | contribs) |
||
| Line 25: | Line 25: | ||
== Discussion == | == Discussion == | ||
| − | + | *12-Jan-2011 | |
| − | + | **Question raised on how PRT could address the same capability. | |
| − | + | ***PRT would yield more segments, but still express the same using Instance ID, Location, and Participation | |
| − | + | ***DST would yield less, more compact segments where waypoints to a destination are included in the segment | |
| − | + | **Motion to accept as proposed. Andrzej Knafel, Patrick Loyd. Against: 0, Abstain: 0; In Favor: 7 | |
| − | |||
| − | |||
Revision as of 17:25, 24 February 2011
Return to OO Change Requests page.
| Submitted by: Andrzej J. Knafel | Revision date: <<Revision Date>> |
| Submitted date: January 4th, 2011 (as replacement of the CR 663 from 25th Sep 2010 withdrawn in Dec 2010) | Change request ID: OO CR051-680 |
| Standard/IG: 2.8 Standard | Artifact ID, Name: <<Artifact ID, Name>> |
Contents
Issue
See 2.8 change request File:OO CR051-680.doc for problem definition and proposal.
Recommendation
Rationale
Discussion
- 12-Jan-2011
- Question raised on how PRT could address the same capability.
- PRT would yield more segments, but still express the same using Instance ID, Location, and Participation
- DST would yield less, more compact segments where waypoints to a destination are included in the segment
- Motion to accept as proposed. Andrzej Knafel, Patrick Loyd. Against: 0, Abstain: 0; In Favor: 7
- Question raised on how PRT could address the same capability.
