Added the missing CR from Adrian as PullRequest to next#250
Conversation
ue71603
added
the
needs documentation update
|
Should we have a discussion on the definition? https://en.wikipedia.org/wiki/Tactile_paving |
|
Can certainly add it to the list for the next meeting... You think it is underspecified? |
| <xsd:group ref="ZoneGroup"/> | ||
| </xsd:sequence> | ||
| <xsd:group ref="PlaceGroup"/> | ||
| <xsd:element ref="AccessibilityAssessment" minOccurs="0"/> |
There was a problem hiding this comment.
This is a different issue and can be tagged as "bug" since the current version is not aligned with the model and the document.
However, to conform the Model, we just need to add
<xsd:group ref="SiteElementGroup"/>
<xsd:group ref="SiteComponentGroup"/>
It should be a separate PR to "master" tha we can approuve an merge right away
There was a problem hiding this comment.
I think we did that already in a different setting.
Can be ignored. ./netex_part_1/part1_ifopt/netex_ifopt_path_version.xsd: <xsd:element name="TactileGuidingStrip" type="xsd:boolean" minOccurs="0"> |
|
We may also consider "TactileWarningStrip" which is more and more requested by associations here in France |
|
Both appear as variant. We should not diverge on naming. ./netex_part_1/part1_ifopt/netex_ifopt_path_version.xsd: <xsd:element name="TactileWarningStrip" type="TactileWarningStripEnumeration" minOccurs="0"> |
|
yes we have both (TactileWarningStrip and TactileGuidingStrip) for 2 different purposes: one is a continuous line to guide people along the path and the other just some tactile marking (usually a line to cross) at some specific places (just before a crossing, entrance, etc.) to warn about the change/obstacle on the path |
| <xsd:element ref="EscalatorFreeAccess" minOccurs="0"/> | ||
| <xsd:element ref="LiftFreeAccess" minOccurs="0"/> | ||
| <xsd:element ref="RampFreeAccess" minOccurs="0"/> | ||
| <xsd:element ref="GuideDogAccess" minOccurs="0"/> |
There was a problem hiding this comment.
already existing in EIAP branch. but in SensoryLimitationGroup
| <xsd:element ref="StepFreeAccess" minOccurs="0"/> | ||
| <xsd:element ref="EscalatorFreeAccess" minOccurs="0"/> | ||
| <xsd:element ref="LiftFreeAccess" minOccurs="0"/> | ||
| <xsd:element ref="RampFreeAccess" minOccurs="0"/> |
There was a problem hiding this comment.
exsits in EIPAP branch
| <xsd:documentation>Whether a PLACE has audible signals for the visually impaired.</xsd:documentation> | ||
| </xsd:annotation> | ||
| </xsd:element> | ||
| <xsd:element ref="TactileGuidingStripsAvailable" minOccurs="0"> |
There was a problem hiding this comment.
Ordered a bit differently and the name is TactileGuidanceAvailable
| <xsd:documentation>Whether a PLACE has lift free access.</xsd:documentation> | ||
| </xsd:annotation> | ||
| </xsd:element> | ||
| <xsd:element name="RampFreeAccess" type="LimitationStatusEnumeration" default="unknown"> |
There was a problem hiding this comment.
Part of the MobilityLimitationGroup
| <xsd:complexContent> | ||
| <xsd:extension base="Place_VersionStructure"> | ||
| <xsd:sequence> | ||
| <xsd:element ref="AccessibilityAssessment" minOccurs="0"/> |
|
What is in this PR is Ok for me (provided that it goes to 'next' so it can be discussed/validated by the group during the incoming revision)... and if it has been split in different PR's that's OK (which one are now managing RampFreeAccess and GuidedDogAccess ? and TactileWarningStrip and TactileGuidingStrip ?) |
|
@Aurige I have seen the things already in the EPIAP branch. Except the distinction between TactileWarningStrip and TactileWarningStrip. It is only TactileGuidanceAvailable |
|
Ok... I would favour having both TactileGuidanceStrip and TactileWarningStrip (it's 2 different features, and it's weird to mention one without the other) |
|
Everything done in other PR. |
|
Removing "needs documentation update" label since closed without having been merged. |
trurlurl
removed
the
needs documentation update
4 participants
Added the missing Accessibility elements we think we should use for modeling the accessibility fully.