draft version of the MME 2.0 maindocument

[derpmann]

The result from the discussion within the MME TaskForce is the attached
draft version of the main document for the MME 2.0 data format:
ISO_TS13499_V2_draft_20110921.pdf

[ucarstensen]

Hello,

I have a question about the convention of testnumbers.
Point 4.4 (File convention) reserved the ASCII 95 for the seperation of filenames. Also it defines the testnumber is free.

We use testnumbers like xx_xxxx_xxxx , and I hope it's still allowed. Otherwise we get in trouble with our database.

Best regards


Uwe Carstensen

[DiVe]

Dear Uwe,
I expect your naming convention might get in conflict with the special naming convention we suggest to introduce in the V2.x. Here the full channel name will consist of the test name the channel code and optionally the reference system and the origin:
<testnumber>_<channelcode>_<refsystem>_<origin>.mmd

As you can see here: http://www.iso-mme.org/forum/viewtopic.php?f=35&t=152
some parts can be omitted in the "standard case".

Also you will find this principle in other files like the comment files in the different subdirectories:
<testnumber>_<subdirectory-name>.txt

Therefore we implement a separator character and we opt for the "_". So we need to discuss if a software handling the 2.0 data can still identify the different parts may starting from the end of a filename. So that the "_" separator is still allowed in <testnumber> part.

I will discuss internally with my colleagues and come back later. May their are some other comments from software suppliers or users about this issue?

Bye,
Dirk

[DiVe]

Dear Uwe,
We discussed you issue on the Task Force Metting and we will change the main document to allow also the "_" character in <testname> (respectively <testnumber>).

As the major test descriptor file (<testnumber>.mme ) always consists of the full test name a software algorithm can identify this part in all other files. So the "_" character will be allowed.

Kind regards,
Dirk