Adding attribute on Entity for publication meta-information (e.g. for public, or restricted dataset-filtering purposes) #899
Conversation
… filtering purposes)
xsd/netex_framework/netex_responsibility/netex_version_support.xsd
Outdated
Show resolved
Hide resolved
….xsd Co-authored-by: Matthias Günter <matthias.guenter@sbb.ch>
|
Is "future use" something that is in scope or out scope, because for example a ValidityBetween should have been provided. |
|
where are you quoting from? |
The ideas in my mind after reviewing this addition. |
|
aha well. yes and no. our customers keep requesting "send file import later"-features so that they are able to sync their real-time systems (which have a much slower turnover than our import), but.... I dont know. As you say, it could be a validty date too but it requires so much from the various system to a) know about the value b) know what it means c) implement logic for it. I dont think the world is ready for such advanced syncronized data activation. But, maybe this is not the usecase you were thinking of. |
|
My use case is basically, there will be renovated station in the future. But obviously the planned state is available. I think people are interested in knowing what the station looks like in the future. |
|
so its a stopplace with versions |
ue71603
added
enhancement
| <xsd:documentation>Whether ENTITY is currently in use. Default is "active".</xsd:documentation> | ||
| </xsd:annotation> | ||
| </xsd:attribute> | ||
| <xsd:attribute name="publication" type="PublicationEnumeration" use="optional" default="public"> |
There was a problem hiding this comment.
Suggestions for a more precise name: publicationSharingPolicy, publicationVisibility
Aurige
added
the
needs documentation update
6 participants
Once more I am clicking buttons on behalf of Entur.
This was created ages ago by people in Entur but it was never merged up to CEN.