Proposal for an extension of ClassInFrameRef

[ue71603]

Addesses: https://github.com/NeTEx-CEN/NeTEx/issues/649

[ue71603]

@Aurige epip used mixed=true in their profile. I know undo it... Was bad practice anyhow.

[skinkie]

At this moment the following is part of the EPIP example by @Aurige. The part that I don't understand is now the ClassInFrame nameOfClass is introduced. That entire nameOfClass does not exists.

<TypeOfFrame version="epip:1.0" id="epip:EU_PI_LINE_OFFER">
        <Name>Network and schedule data for a single line.</Name>
        <FrameClassRef nameOfClass="CompositeFrame"/>
        <classes>
                <ClassInFrameRef nameOfClass="DataManagedObject">Use Common definitions</ClassInFrameRef>
                <ClassInFrameRef nameOfClass="VersionFrame">Use Common definitions</ClassInFrameRef>
                <ClassInFrameRef nameOfClass="ResourceFrame">Use Common definitions</ClassInFrameRef>
                <!-- Specific -->
                <ClassInFrame nameOfClass="EU_PI_LINE_OFFER.SiteFrame-EU_PI_STOP">
                        <ClassRefType>all</ClassRefType>
                        <Mandatory>required</Mandatory>
                </ClassInFrame>

I think the question is if nameOfClass here should be something like:

<ClassInFrame nameOfClass="SiteFrame" typeOfFrameRef="epip:EU_PI_STOP" version="epip:1.0">

[Aurige]

I don't really remember that example (it must be pretty old, over 10 years, since NEPTUNE is not used any-more for quite long.. it was the equivalent of the UK TransXChange... so not NeTEx, but we did a mapping to NeTEx in 2013/14). I agree that ClassInFrameRef can be a misleading name, it's initial intention was to refer a Class in the Frame...so more a ClassRefInFrame ... so initially no need for a ClassInFrame since the Class itself (Element in XSD) is really defined at XSD level. The ClassInFrame was added later (can't remember when/why... or maybe just in this set of commits ?)

[ue71603]

@skinkie do we need more levels? Or can you do with one?

[ue71603]

@skinkie does this fit you primary needs (when we don't implement full schematron).