search

DATEX-II-EU / DatexII

Main repository for issues and bugs for the DATEXII standard
0 stars 0 forks source link

IMPORTED (201) - Location Referencing: documentation and specification Inconsistency about country code ccd (Bugzilla Bug 46) #46

Open datexii opened 5 years ago

datexii commented 5 years ago

This issue was created automatically with bugzilla2github.py

Bugzilla Bug 46

Date: 2019-03-01T10:59:41+01:00 From: @ingeniumfaber To: Jean-Philippe Mechine <Jean-Philippe.Mechin@cerema.fr> CC: @iancornwellmottmac

Last updated: 2020-09-11T11:06:12+02:00

datexii commented 24 years ago

Comment 156

Date: 2000-01-01 01:01:01 +0100 From: @ingeniumfaber

An inconsistency has been found in documentation provided on website, since version 1.0 in example messages and User Guide about Alert C Location coding Country Code In Alert C Method for AlertCLinear, AlertCPoint and AlertCArea Classes the same attribute alertCLocationCountryCode has definition "EBU country code" The UserGuide ( DATEXIIv2.0-UserGuide.pdf ) for Alert C report to use 'F' for France we assume the reference in mind is the EN 50067 which contains the definition for usage of COuntry Codes in RDS ( and extended country codes out of Europe ) which map E for Sweden and Spain and F for France (http://www.interactive-radio-system.com/docs/EN50067_RDS_Standard.pdf pag 70 and 71 ) in the provided examples such code is otherwise managed in different ways ( since Version 1.0 to the current version ) - in example Situation Record Accident we find alertCLocationCountryCode = E for sweden feed - in example file for Travel Time we found 14 in example from France - in example for Itinerary we find both Code E and 14 ( and incidentally version is further defined as "2.1" or "2.0" while it should be an integer in TMC coding despite the datatype is valid as it is String ) otherwise searching the web for "EBU country codes" lead to https://tech.ebu.ch/docs/tech/tech3279.pdf which base its definition to ISO alha 2 country codes. same concern is about alertCLocationTableNumber which in the user guide is identified with 32 and in the examples from Sweden is 33 and also for France is the same.. while we had assumed in the past it was the Location Table number defined in the country, which for Italy we would provide as 1 after discussion in TG it seems that the correct reference for CC is EN 50067 so we assume this should be improved in definition and updated in example messages and guides

datexii commented 24 years ago

Comment 157

Date: 2000-01-01 01:01:01 +0100 From: @iancornwellmottmac

Discussed at Oporto TG and agreed that the model should not change. Call on 3/12 agreed this should be reassigned to documentation.

datexii commented 5 years ago

Comment 158

Date: 2019-03-01 10:59:41 +0100 From: bugzilla admin <webmaster@datex2.eu>

--- Bug imported by webmaster@datex2.eu 2019-03-01 10:59 CET ---

This bug was previously known as bug 201 at https://bugzilla.datex2.eu/show_bug.cgi?id=201 This bug blocked bug(s) 2.

LBlaive commented 2 weeks ago

The official reference for Country code of RDS is IEC 62106:2009, which has superseded EN 50067 (similar in terms of content) whereas the source for location table number is EN ISO 14819-3:2021. The definitions found in the current model version are correct. However, it is to note that the possible values for the attributes “alertCLocationCountryCode”, “alertCLocationTableNumber” and “alertCLocationTableVersion”, which are typified as “String”, are not constrained. It may be interesting to rediscuss this latter point.

Note 1: For IEC 62106, the country code is indeed a four-bit digit allowing values between 1 and 15 (0 excluded) but frequently represented by a hexadecimal digit thus e.g. “E” (instead of “14”) and “F” (instead of “15”) for France. In EN ISO 14819-3, location table numbers are integers between 1 and 63 (0 being excluded).

Note 2: When this issue was already discussed during the preparation of Version 3, it was agreed to introduce facets for limit the acceptable for these attributes.This does not seem done