DATEX-II-EU / DatexII

Main repository for issues and bugs for the DATEXII standard

0 stars 0 forks source link

External object references should be able to include endpoint API URL (Bugzilla Bug 467) #467

Closed datexii closed 1 month ago

datexii commented 7 months ago

This issue was created automatically with bugzilla2github.py

Bugzilla Bug 467

Date: 2023-11-28T15:53:49+01:00 From: @iancornwellmottmac To: @JoergFst

Last updated: 2024-05-16T17:48:53+02:00

datexii commented 7 months ago

Comment 1881

Date: 2023-11-28 15:53:49 +0100 From: @iancornwellmottmac

A request was made that when specifying a reference to an external object, one should be able to identify an endpoint from which the object can be obtained.

Today we have GlobalReference (and its subclasses) which has a couple of string identifiers but neither are exactly for an API endpoint URL.

For example it could also have something like sourceEndpoint of type UrlLink or Url.

datexii commented 1 month ago

Comment 1940

Date: 2024-05-16 17:47:44 +0200 From: @JoergFst

Created attachment 56 Solution

Attached file: ApiEndpoint.png (image/png, 120346 bytes) Description: Solution

datexii commented 1 month ago

Comment 1941

Date: 2024-05-16 17:48:53 +0200 From: @JoergFst

Acknoledged.

In Version 4, an aggregation "externalPublicationSource" between GlobalReference and UrlLink is introduced. In addition, a new literal "apiEndpoint" is added to UrlLinkTypeEnum.