Job ticket unique identifiers

[Anrdzej Zydron <azydron@azdata-products.com>]

Hi,

In accordance with Peter's request regarding unique identifiers for 
tracking individual job/language translation files I have undertaken to 
summarize the discussion and proposed solution. This follows on from the 
discussion regarding "job tickets" from the previous meeting.

1) A unique identifier will be allocated to each individual atomic 
file/language entity. The granularity of the entity will be defined at 
the "file/language" pair level as submitted by the customer.

2) The file itself may be an archive file that contains more than one 
translatable file. No further granularity in identifying the job will be 
  allocated over and above the containing archive file level.

3) The standard will not concern itself with any grouping of the 
identifiers into any form of ontological entities or otherwise. It is up 
to the customer and/or supplier to implement any desired grouping of the 
unique identifiers for their own purposes (i.e. overall deliverable 
tracking or billing).


The remaining questions that require clarification on this topic are:

1) Who should generate the unique identifier - the supplier or the customer.
2) Should any defined formalism be attributed to the unique identifier.

Any further comments would be most welcome,

Regards,

Andrzej Zydroń

-- 

-- 
email - azydron@azdata-products.com
smail - Mr. A.Zydroń
         24 Maybrook Gardens,
         High Wycombe,
         Bucks HP13 6PJ
Mobile +(44) 7966 477181
FAX    +(44) 870 831 8868
www - http://www.azdata-products.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
may not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version. Unless
explicitly stated otherwise this message is provided for informational
purposes only and should not be construed as a solicitation or offer.