Use SBOID as Business Identifier rather than NetEx Object ID

[FlourishingData]

• Fix all examples so that Operator and ResponsibilitySet use the sboid in the @id when they are not foreign operators.
• Fix in templates.

The current Swiss Profile draft indicates that Operator objects are identified using the SBOID and that the same organisation may also need to be referenced through AuthorityRef. A comment in the specification already highlights a potential issue:
_

"We will use this organisation also in AuthorityRef. The problem is that the sboid can be used only once."

_
This shows that the SBOID is currently used as the NetEx object identifier (@id) for organisation-related entities.

Proposal
Separate:

• NetEx technical object identifiers
• Swiss business identifiers (SBOID)

We could store all SID4PT in PrivateCodes?

                <organisations>
                    <GeneralOrganisation></GeneralOrganisation>
                    <Operator id="ch:1:Operator:PAG" version="1">
                        <Name>PostAuto AG</Name>
                        <ShortName>PAG</ShortName>
                        <privateCodes>
                            <PrivateCode type="SBOID">ch:1:sboid:100602</PrivateCode>
                            <PrivateCode type="GO_NUMBER">801</PrivateCode>
                        </privateCodes>
                    </Operator>
                    <Authority id="ch:1:Authority:PAG" version="1">
                        <Name>PostAuto AG</Name>
                        <ShortName>PAG</ShortName>
                        <privateCodes>
                            <PrivateCode type="SBOID">ch:1:sboid:100602</PrivateCode>
                            <PrivateCode type="GO_NUMBER">801</PrivateCode>
                        </privateCodes>
                    </Authority>
                </organisations>

[ue71603]

@FlourishingData after analysing we don't use AuthorityRef. The "Konzessionär" is now in the OperatorRef and in responsibiltySet in the EntityLegalOwnership part.

[ue71603]

@FlourishingData We want to allow in future that for all elements where there is a SID4PT id (and therefore Atlas is the master system) that they are replaced during import with the content of Atlas. We only can do this in a simple way, when the id is the correct element. That's why we want to do it the way it is described. We will clarify this in the document

• Matthias do improved description
• Adrian: Make sure that in the examples and tempaltes the id are SID4PT where it is possible:StopPlace, Quay, ScheduledStopPoint, Line, Operator. @aschmid-code

[FlourishingData]

@ue71603 Thanks for the clarification. I fully agree with the approach of using the SID4PT identifiers as the NetEx object IDs and enriching the corresponding objects from Atlas during import.

A question on versioning: since the SID4PT identifiers are versioned in Atlas, does this also mean that the resulting NetEx elements are versioned accordingly?

[ue71603]

Currently in INFO+ everything is flattened in the export process. So there is only one version of everything in thefile.
Otherwise we would need to address this on a very fundamental level with INFO+. @soleluna83

[ue71603]

Raphael: Dieselbe Sboid auch Versionen. Die richtige id muss geliefert.
Thomas: Wir verwenden bei den SID4PT alles, und nehmen es auch als Atlas. Die Version ist daher für uns nicht relevant. Wir überschreiben dann auch die relevante Version.
Raphael: Unter dem Jahr ändert die Koordinate. Das wechselt erst auf das Stichdatum. Ich kann nicht in die Zukunft schauen.
Thomas: Wenn Du das machen willst, musst Du Atlas anbinden.