Christophe Duquesne

That's probably a point where we need best practice rules (I know that some will systematically search for ServiceJourney.dayTypes )

Yes, bit fields are the recommended way for EPIP too The question is where to put it (and we need to be careful with Transmodel here) and how to articulate...

there was "group decision needed" + "to be discussed" ... only the first has been cleaned after the discussion ... => Cleaning labels and updating the doc

Part 1 doc was updated

Update the documentation accordingly (SP or Q of BP mandatory) + XSD ANNOTATION

The group asked to postpone the work on DUTY ... so we can keep the PR open for later work (an new PR will need to be drafted from this...

Initially the _MultilingualString_ was initially designed to carry the lang (any lang) information associated with a text but not for translations. The translations are expected to be provided by _AlternativeName_...

it depends on where in Belgium you are ;-) but in any case, this is not the "official" language, just the one used as default (you need a default one),...

@JohanEntur Doesn't Nick's answer/example provide what you are looking for ? Every single DataManagedObject (so most of NeTEx entities) can carry alternativeTexts (for translations, but also all other possible uses)...

you need to use _AlternativeText_ as in Nick's example ``` _< FareScheduledStopPoint id="uic:6050a" version="01" > < alternativeTexts> .... < !-- Translations for FareScheduledStopPoint.Description --> < AlternativeText useForLanguage="en" attributeName="Description"> < Text...