agencyId conflict between AdditionalAgencyLogEvent and base LogEvent
Opened this issue · 2 comments
Required agencyId declared under AdditionalAgencyLogEvent conflict/obstruct the also required agencyId from the base LogEvent component. In the state the schema is in, AdditionalAgencyLogEvent is not useable.
agencyId declared under AdditionalAgencyLogEvent should be renamed so it does not conflict with LogEvent and to make clear if is identifying the AdditionalAgency this log event is about. e.g. additionalAgencyId
Note that i3 document will need to be updated to reflect the change in the schema.
Was there ever an Errata form filed for this? Someone else just reported a similar problem with "incidentId" in the LogEvents used for Merge, Link, and Split events, and also in some LogEvents added by the EIDO Conveyance WG. If I understand the problem correctly, you'd get an error when you tried to create any of these LogEvents because you'd have two elements with the same name at the same level in the object. I think we should submit a Errata form.
Errata was filed (ADM-007) on this issue by me. The issue was then added to the ADM-007 for version 3f by Steve O'Conor, superseding the ADM-007 I filed. The pull request is currently pending.