You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to make a profile definition TypeOfFrame/ClassInFrameRef is an embedded way to describe a profile. What is currently lacking is the ability to describe the elements required in the profile.
If from this minimal definition a derived XML Schema (or Schematron) can be generated, every profile can be validated against an always up to date NeTEx upstream, without manual the manual labor of maintaining an extra XML Schema by hand (such as EPIP, Dutch, etc.)
The text was updated successfully, but these errors were encountered:
Yes, but not on ClassInFrameRef, but on something like an Element under it. For example passingTimes are required er required in ServiceJourney for EPIP and Nordic profile. I would like to see something like:
<ClassInFrameRefref="ServiceJourney">
<ObjectInClassRefref="Description"use="optional" /> <!-- minOccurs in root takes preference, hence this is redundant, but might be interesting to mention that the generic implementation would consider it -->
<ObjectInClassRefref="passingTimes"use="required" />
<ObjectInClassRefref="calls"use="prohibited" />
</ClassInFrameRef>
In order to make a profile definition TypeOfFrame/ClassInFrameRef is an embedded way to describe a profile. What is currently lacking is the ability to describe the elements required in the profile.
If from this minimal definition a derived XML Schema (or Schematron) can be generated, every profile can be validated against an always up to date NeTEx upstream, without manual the manual labor of maintaining an extra XML Schema by hand (such as EPIP, Dutch, etc.)
The text was updated successfully, but these errors were encountered: