DGTINA - Issues

0000020: Limited quantity DG shipments dont need UN Number and class

Thu, 22 Jun 2023 09:53:15 +0000

Our customer sends DG in limited quantity.

true

As of our knowledge such shipments don't need the UN number and danger label fields filled, so he sends dummy information like

_extended
_extended

0

LQ - Gefahrgut in begrenzter Menge

Please advise how to proceed

0000018: Move the link from DGConsignmentDescriptionStatic to "DGSpecialProvision"

Tue, 24 Jan 2023 15:40:58 +0000

The actual link is from class DGConsignmentDescriptionStatic to class DGSpecialProvision.

The link has to be moved in order to allow the DG transport document for an empty packaging with a special provision which not allowed now.

The future link with the same type and multiplicity will be from class DGDescriptionDetailsto class DGSpecialProvision.

0000019: Delete the link between Class DGTDocumentEntry and CLass QuantitiesPerShipment

Thu, 21 Apr 2022 16:11:02 +0000

This link is not usefull because it's redoundant with the attributes of:
class DGConsignmentDescriptionStatic
totalQuantityOfDG
unitTotalQuantityOfDG
and
Class DGDescriptionDetails
Attribute transportCategory

0000009: Output data for getArchiveJourneyList method -

Thu, 07 Apr 2022 15:54:29 +0000

Journey - DGTransportUnit

We agreed upon this, but it still has to be changed: in the wsdl in dgtina’s github it is still “idTransportUnit”

0000008: Input data for getArchiveJourneyList method -

Thu, 07 Apr 2022 15:50:21 +0000

DGTransportUnit

We agreed upon this, but it still has to be changed: in the wsdl in dgtina’s github it is still “idTransportUnit”

0000002: output data for handleLoadedVehicle method - Boolean

Thu, 07 Apr 2022 15:03:44 +0000

Possible improvement:
return the activationDate or deactivationDate (or even the started or completed “Journey”) as recorded by the TP1 indicating a successful activation / de-activation (and being more transparent about what is recorded at TP1 and returned in case the getArchiveJourneyList is called)

OR

a more structured error code and the corresponding description (allowing a more robust error handling at the TP2).

0000017: Details for in- and output data for “optional” web service methods

Wed, 06 Apr 2022 16:09:42 +0000

getTransportUnitByArea method
Input Data: idTransportUnit and countryCode

Possible improvement: update to DGTransportUnit

0000015: Details for in- and output data for “optional” web service methods

Wed, 06 Apr 2022 16:09:42 +0000

getDynamicinformation method
Input Data: idTransportUnit and countryCode

Possible improvement: update to DGTransportUnit

0000016: Details for in- and output data for “optional” web service methods

Wed, 06 Apr 2022 16:08:59 +0000

getDynamicinformation method
Input Data: DGPublication

Possible improvement: limit to relevant part of data model DGDynamicInformation and DGTransportUnit

0000014: Details for in- and output data for “optional” web service methods

Wed, 06 Apr 2022 16:08:16 +0000

saveTrackingDataVehicle method
Input Data: DGPublication

Possible improvement: limit to relevant part of data model DGDynamicInformation and DGTransportUnit

0000013: Details for in- and output data for “optional” web service methods

Wed, 06 Apr 2022 16:06:54 +0000

saveTP2Ok method

We should delete the method from the standard. If a TP1 wants to offer a webservice for automated registration of a TP2 (that can be used for updating a certificate, for example) than the method sendTP2RegistrationRequest and its output data should be sufficient

0000012: text to getArchiveJourneyList method -

Wed, 06 Apr 2022 16:04:07 +0000

The following text is displayed under the method description:

" A public service can use the output / the list of completed journeys to contact the TP2 content provider. Requesting accompanying information about completed journeys is not supported in any of the methods of the web services specified in this standard. The getDGTDocumentMultimodal and getGDTDocument methods will only return the accompanying information for currently active dangerous good transports. The TP1 access providers will return an error code (“notActiveTransportUnit” or “inactiveTransport”) in case a TP2 content provider has de-activated the transport / completed a journey using the handleLoadedVehicle method. "

Comment: Should we state that explicitly or delete it (since we only describe what can be done and not what cannot be done)?

0000011: Output data for getArchiveJourneyList method -

Wed, 06 Apr 2022 16:04:07 +0000

Journey - startTime and finishTime

Possible improvement: rename to activationDate and deactivationDate (to have a more clear connection to the content of the output data “Exchange” of the getDGTDocument(Multimodal) methods and the (possibly added) output data of handleLoadedVehicle.

0000010: Output data for getArchiveJourneyList method -

Wed, 06 Apr 2022 16:01:57 +0000

Journey - nameTP1 and nameTP2

Possible improvement: use identical / consistent information identifying TP1 and TP2 in getDGTDocument(Multimodal) and getArchiveJourneyList methods.

0000007: output data for getDGTDocumentMultimodal method - Exchange

Wed, 06 Apr 2022 15:56:20 +0000

DenyReasonEnum - Value: inactiveTransport

Possible improvement: delete from list, since identical to notActiveTransportUnit?

0000006: output data for getDGTDocumentMultimodal method - Exchange

Wed, 06 Apr 2022 15:54:17 +0000

DenyReasonEnum - Value: unknownCarrier

Possible improvement: delete from list, since carrier is not given as input data or checked.

0000005: output data for getDGTDocumentMultimodal method - Exchange

Wed, 06 Apr 2022 15:52:43 +0000

Possible improvement: Make the connection to activationDate and deactivationDate in handleLoadedVehicle and getArchiveJourneyList more transparent.

0000004: output data for getDGTDocumentMultimodal method - Exchange

Wed, 06 Apr 2022 15:51:08 +0000

Possible improvement: split in two parts:
identify TP2 that has registered an active dangerous good transport and provided the information returned in DGPublication.
Identify the TP1 that the dangerous good transport has been activated at / that forwarded the information returned in DGPublication to the public service (this could either be the TP1 asked by the public service or another TP1).

Information identifying the TP1 and the TP2 that provided / forwarded the output data in DGPublication should be “equivalent” to the information identifying the public service: at least return the name and the certificate used.
If we want to improve the information provided, we should discuss if there really is a use-case where more information is used (contact details of a natural person, postal address, e-mail address, url).

0000003: output data for getDGTDocumentMultimodal method - ErrorMessageException

Wed, 06 Apr 2022 15:48:30 +0000

Possible improvement: change to a well structured list of error codes and the corresponding description(s) allowing for a more robust error handling.

Move “DenyReasonEnum” from “Exchange” output data to the “ErrorMessageException” output data.