Handling of GlobalId

[ue71603]

Handling of keyList GlobalId In https://nap-1926.it/nap/mmtis/public/catalog/Asset/9677

This is a "hobby" of MENTZ. However, we also push for a GlobalID in GTFS and perhaps it makes sense, that we do a special treatment, if we find it.

What do you think?

                            </Quay>
                                <Quay id="it:apb:Quay:at-43-4848-10:" version="any">
                                    <keyList>
                                        <KeyValue>
                                            <Key>GlobalID</Key>
                                            <Value>at:43:4848:10</Value>
                                        </KeyValue>
                                    </keyList>

[skinkie]

I want Quay@id as global id ;-)

[ue71603]

In the end the master id of elements must be somewhere and it certainly is not the object id.

[skinkie]

I honestly disagree. The object id is unique and since the global id identifies a unique id, in my opinion that should be used.

[ue71603]

As the uniqueness of most scheduled public transport bases on operation day, your idea already breaks at the ServiceJourney level. So the id of ServiceJourney can't meet that criterium. Where should they store what THEY call a ServiceJourney?

[ue71603]

doing it as you want, is a non-starter for Switzerland. technical id should always be kept away from business id.

[skinkie]

We are now talking about ServiceJourney, your example was Quay (network).

[ue71603]

I used ServiceJourney as an example. Let's assume we have a European stop register. Where would you store the id when you are doing your own stuff (which usually also means your own id)?

[skinkie]

PrivateCode?