NeTEx-CEN/NeTEx

AccessRightParameterAssignment - TypeOfProofRef

Closed this issue · 3 comments

janosu commented

Hi,

I needed to specify the TypeOfProofs in the UserProfile in addition to the predefined ProofOfIdentifyListOfEnum, so I updated the model to version 1.2.2. However, I noticed that in the case of fare products, I cannot refer to this in the AccessRightParameterAssignment validityParameters (only TypeOfConcessionRef is possible). I believe that, like TypeOfConcession, TypeOfProof is needed to indirectly define UserProfiles.

Aurige commented

You have an example (for new mode Car Club) in NeTEx\examples\functions\newModes\NewModes-CarClubExample.xml
I hope it can help

<GenericParameterAssignment order="1" id="my_car@membership@eligibility" version="any">
		<TypeOfAccessRightAssignmentRef versionRef="EXTERNAL" ref="fxc:eligible"/>
		<limitations>
			<!---  ===ELIGIBILITY USAGE PARAMETERS =========    -->
			<UserProfile version="any" id="adult_driver">
		         <Name>Qualified driver</Name>
			<UserType>adult</UserType>
			<MinimumAge>18</MinimumAge>
			**<typesOfProofRequiredRef>
				<TypeOfProofRef versionRef="external" ref="driving_licence"/>
			</typesOfProofRequiredRef>**
			</UserProfile>
		</limitations>
</GenericParameterAssignment>

As Christophees exampel suggests, in principle a fare GENERIC PARAMETER ASSIGNMENT would normally specify the eligible USER PROFILE, and the USER PROFILE would define what the TYPE(s) OF PROOF required are. However it is possible to conceive circumstances where the type of proof might be a relevant parameter assignment for a rule, for example if proof of identity must be presented alongside the ticket .
So we should add TYPE OF PROOF as a parameter

UML for Transmodel
image

UML For NeTEx
image

=========================
Also, iIn checking the UML I noticed that the documentation of USER PROFILE needs changing to show the change to allow USER PROFILEs to have multiple TYPEs OF PROOF

(1) Transmodel
image

fixed in #599
Perhaps still some TM adaption needed.