OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cti message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [cti] Re: MVP Discussion


Terry MacDonald wrote this message on Fri, Apr 08, 2016 at 21:18 +1000:
> This way of doing translations causes the same problems as the explicit
> versioning... relationships no longer point to the latest version of an
> object (as there may be two translations of the same object). Which object
> is the 'truth'? Which version of the object is the one that everyone should
> connect their relationships to?

Some references will need to point to an explicit version of an object,
for example, suggested-update should point to a version of the object,
not just the object to help the original producer know what exactly the
difference that is being proposed...

I view translations (if not embeded in the object) as being similar
(and similarly versioned TLO's)...

Borrowing and modifing your example:
{
  "id": "report--cbf7a3eb-5ef0-42ef-a30c-14be2a14cc1d",
  "type": "report",
  "revision": 1,
  "lang": "en",
  "created_at": "2016-01-29T21:18:33Z",
  "title": "Hi, this text is in English",
  "description": "So is this"
}

{
  "id": "translation--5cfa580e-ea87-4d11-b0cc-600af7a64968",
  "type": "translation",
  "revision": 1,
  "translated_type": "report",
  "translated_ref": [ "report--cbf7a3eb-5ef0-42ef-a30c-14be2a14cc1d", 1 ],
  "lang": "es",
  "created_at": "2016-01-30T19:13:09Z",
  "title": "Hola, este texto es español",
  "description": "Asi es esto"
}

Then if the report gets versioned:
{
  "id": "report--cbf7a3eb-5ef0-42ef-a30c-14be2a14cc1d",
  "type": "report",
  "revision": 2,
  "lang": "en",
  "created_at": "2016-01-29T21:18:33Z",
  "title": "Hi, this text is in English",
  "description": "This is a better descripition of the report."
}

The translator can then produce:
{
  "id": "translation--5cfa580e-ea87-4d11-b0cc-600af7a64968",
  "type": "translation",
  "revision": 2,
  "translated_type": "report",
  "translated_ref": [ "report--cbf7a3eb-5ef0-42ef-a30c-14be2a14cc1d", 2 ],
  "lang": "es",
  "created_at": "2016-01-30T19:13:09Z",
  "title": "Hola, este texto es español",
  "description": "Esta es una mejor descripción del informe."
}

And a UI can now inteligently display info about the transalation...
If they have received revision 2 of the object, but only the
translation for revision 1, they can present the translation, BUT
provide a tip that the translation may not match exactly, and give an
option to view the original field.

P.S. Yes, I do realize that I'm changing how _ref's work, and I did
originally think of idref-revisionnum, but liked this better.

-- 
John-Mark


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]