OccupancyView also possible directly in ServiceFrame#784
OccupancyView also possible directly in ServiceFrame#784
Conversation
ue71603
added
enhancement
ue71603
requested review from
Aurige,
duexw,
skinkie,
syversenkr and
trurlurl
| </ScheduledStopPoint> | ||
| </scheduledStopPoints> | ||
| <occupancies> | ||
| <OccupancyView version="any" id="occinFrame"> |
There was a problem hiding this comment.
I don't see how a OccupancyView at this point. I think it must not be a view.
There was a problem hiding this comment.
No other elements available. It always was a View and never anything else. You wanted it here. Sorry.
There was a problem hiding this comment.
No I want to have an Occupancy here.
|
There exists currently only OccupancyView. So what do you want? Renaming? Wrapper? |
|
I want to see Occupancy to be a first class element. For this to work something more is required. At is point, nothing references to it. And it is also not describing itself what it is providing the occupancy for. |
|
Then this is no longer a small PR, but a full fledged one. And the question can be asked, why it supports only a part of what is possible in SIRI. |
ue71603
changed the title
|
The group discussion was for an OccupancyView (cf #605 ) so that looks fine to me ... Shall we discuss it again ? |
|
I was in that meeting, and the idea was to make Occupancy a first class object, not a view. |
|
The Full TM compliant Occupancy was identified as too rich and not fulfilling our more simple requirements, so a SIRI inspired view was decided ... but you can draft a fully TM compliant Occupancy for next release |
|
@skinkie currently set for 3.0. Do you need it before? |
|
is there any possible ref from Jouneys to that OccupancyView ? |
|
can be addressed in 3.0 |
trurlurl
removed
the
needs documentation update
4 participants
fixes #757