SituationExchange - add optional list of keywords in PassengerInformationAction #137
Conversation
haeckerbaer
requested review from
DohmenClaus,
Ulf9,
prirey,
skinkie,
tim-rivett and
ue71603
haeckerbaer
changed the title
|
Is related to the discussion about replacing nmtoken in IDs. Alternatively we change the type to xsd:string. |
|
If we want to move away from NMToken we need to inform people. Using additional characters may break legacy systems. |
TuThoThai
added
Needs CEN documentation Update
|
@ue71603 See my comment above about compatibility. I would like to add an example but need to ask on UmS side first as i'm not the initiator. By the way, the initial proposal from UmS didn't include special symbols as mentioned above (hence it's a new requirement from SG7)! |
|
@haeckerbaer Just telling. If UTF-8 is allowed for identifiers, then very strange id need to be consumable by the it systems. |
|
@ue71603 what we could also do is xsd:list with <xsd:restriction base="xsd:string"> and <xsd:pattern value="[A-Za-z0-9._:-#]+"/> plus whatever characters we need. Would that be better? The question is what characters we have to add |
|
I guess then we will have to change all the time. I informed NAPCore X 2.4. They should think about it also a bit. |
|
10.11.2025: SG7 decided to discuss it in the SX task force since there might be a need to also integrate into ActionData |
|
As per TaskForce decision on 24.11: moved new keywords element to ParameterisedActionStructure (from PassengerInformationActionStructure) so that it is also available in all of the "classical" actions (such as PushedAction). |
xsd/siri_model/siri_situation.xsd
Outdated
| <xsd:element name="Keywords" minOccurs="0"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Arbitrary application specific classifiers.</xsd:documentation> | ||
| <xsd:documentation>A whitespace-separated list of arbitrary application specific classifiers, tags or message categories for filtering or display, for example as icons on a situation map. Can be overwritten in an individual PassengerInformationAction.</xsd:documentation> |
There was a problem hiding this comment.
PassengerInformationAction to be changed to ParametrisedActionStructure
There was a problem hiding this comment.
i replaced PassengerInformationAction with "action". is that Ok? I wouldn't reference abstract xsd structures but rather elements actually present in a "finished" xml. However, this would require a reference of multiple elements.. I chose the conceptual "action" for this reason but maybe ParametrisedActionStructure is still better suited. What do you think?
|
As per group decision of 19 December 2025: agreement to have Keywords in ParametrisedActionStructure and keep the type as NMTOKENS |
See https://3.basecamp.com/3256016/buckets/9672657/messages/7107289955