Branding/ContactDetails
Considering a Brand already has a URL. @JohanEntur and I wonder why it does not host ContactDetails. Since the Brand is known to the user, and typically the Operator is not known.
Thanks for creating the issue Stefan.
Yes, I was thinking 2 things:
- For what reason would Brand ONLY allow the Url. Why couldnt it have a phone number for example... or fax number 😏
- Since ContactDetails HAS Url, why not re-use the same structures on Branding as well. Makes NeTEx more uniform.
The Branding is initially something totally different from a company or organisation. It's more a generic name associated to a set of services. For example, in Ile De France, we have Noctilien (https://www.iledefrance-mobilites.fr/noctilien or https://en.wikipedia.org/wiki/Noctilien) or TZen (https://en.wikipedia.org/wiki/T_Zen). In most case there is not contact point (contact points are the operators operating the services... so it can be quite a lot). So it's mainly a kind of named classification. Technicaly it is just a generic TypeOfValue (that has a URL, that's why you found it). It is not a Transmodel concept... but if we want to change it so it has its specific structure (with ContactDetails, etc.) then it becomes a real independent concept and therefore should be shared with Transmodel. We can discuss thin on the 25th
Ok. It makes more sense now with the URL coming from ToV.
I'll have to rethink my usecases a bit. Its difficult to know when to use Branding, and on what. Often because the companys that create "brands" do not do this in a structured way. We can talk at the next meeting.
@JohanEntur Can this issue be closed then? Docu update needed?
I think that... yes, for now. Branding is such an open concept that its very difficult to find a proper use for. If a "Brand" is something that shows a new name, and CAN show a new URL, it only makes sense that it should also show other types of contact information.
We can come back to this at another time if it allows progress in the current PR-backlog.
update doc