trurlurl

Given the very detailed modelling including the definition of wheelchair types, I had a look at the AccessibilityAssessment. In `Deck-Plans-Example_trains.xml` I found *WheelchairAccess* == true together with *StepFreeAccess* == false....

> Added to the guidance document in 5.9. so only André's stuff left @ue71603 Can you please point me to the guidance document mentioned?

I added the following text to the version attribute documentation of `EntityInVersion`, in part 1 and part 4: "Allowed values are "any", or a string adhering to agreed-upon formatting and...

@skinkie A bit less elegant, but would the following be sufficiently clear? I find the word "string" useful here, but I'll try to think of a further alaternative. "With the...

What about this? The value may be "any" or a VERSION number adhering to agreed-upon formatting and interpretation rules (representing, e.g., numbers or dates). Consecutive VERSION numbers should be strictly...

I checked for EPIAP, are some of the following observations useful? EquipmentPlace-placeEquipments and SitePathLink-placeEquipments may refer any Equipment, so probably: - EquipmentRef - LuggageLockerEquipmentRef - PlaceLightingEquipmentRef - QueueingEquipmentRef - WaitingEquipmentRef...

Based on the discussion so far, PR #979 adds constraints for the following: From the first list: - FacilitySet - FlexibleLinkProperties - FlexiblePointProperties - GeneralFrameMember - GenericNavigationPath - GenericPathJunction -...

No objections...

This is in master, I'm not sure about the implications for the documentation. Is the same change also somewhere for next, or will this one be merged before V2.0?

I cannot judge whether everything is really obsolete, so I don't dare approving. Taking the example of *LiftCallEquipmentRefStructure*: I guess this is removed because element *LiftCallEquipmentRef* refers to the more...