Seating Plan Seat Context changes #813
Conversation
Changes from Netex meeting (a) Remove hasTray (b) Add blankRowEndNoAisle to seat context (c) Update example
Add further Seat contextenum values for facing window
…hub.com/nick-knowles/NeTEx into Seating-Plan-Revisions--Seating-Context
reanme roeend enumeration
ue71603
added
change-request
| </xsd:annotation> | ||
| </xsd:enumeration> | ||
| <xsd:enumeration value="inMiddleWindowInFront"/> | ||
| <xsd:enumeration value="inMiddleAisleInFront"/> |
There was a problem hiding this comment.
What does "WindowInFront" and "AisleInFront" mean?
There was a problem hiding this comment.
To me it's just that the aisle (or window) is facing the seat. Even if not frequent in trains, that common in ferries and boats for example.
There was a problem hiding this comment.
Thanks @Aurige, I see it is understandable in the ferry context. But then it would seem consequent to me to also have at least rowEndWindowInFront and rowEndAisleInFront - if not as well byWindowAisleInFront, byAisleWindowInFront, byAisleAisleInFront, etc. ... until the combinations become too strange. I share @JohanEntur's doubts whether this is the best approach. Might it be a discutable option to keep the SeatContext very basic and add a seating plan as an image in complex cases as ferries?
|
I thought we were going for an array kind of list of context. Now its going to be endless combinations of concatenated possibilities, just like TransportSubmode. |
|
UML Documentation update (1) Add Seating Plan Classifcation (2) Update to existing Seating Plan Model UML |
Changes from Netex meeting
(a) Remove hasTray
(b) Add blankRowEndNoAisle to seat context
(c) Update example