W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > April 2012

RE: Question on approval status

From: Des Oates <doates@adobe.com>
Date: Wed, 11 Apr 2012 13:01:59 +0100
To: Arle Lommel <arle.lommel@gmail.com>, Multilingual Web LT Public List <public-multilingualweb-lt@w3.org>
Message-ID: <7B8D77012FE36343856B6DE17A307DD284B6BDCBAA@eurmbx01.eur.adobe.com>
In my opinion it is a single category applicable to both. (Your option (2) below Arle.)  Though I don't think it is possible to imply any workflow state based on the respective values. I think this should be left up to the consuming processes to manage.

E.g. Source = 'yes' may mean:
"This content has been automatically verified by Acrolinx"
OR  "This content can be sent for translation",
OR "This content has been reviewed in context and can be published".

It would be up to each workflow implementation on how they would use it.

Des

From: Arle Lommel [mailto:arle.lommel@gmail.com]
Sent: 11 April 2012 11:28
To: Multilingual Web LT Public List
Subject: Question on approval status

Hi all,

In preparing the chart of which processes consume and generate various metadata items, I found I have a question about "approval status":

Is this intended to apply to the source, the target, or both?

I'm assuming both, but if that's the case, do we need two data categories, one for source and one for target?

The reason I ask is that you could have scenarios like the following, which show that the two do not have to correlate:


 *   Source release = no; Target release = yes; A draft of the source text has been sent on to the translator in advance of formal approval (to get a leg up on translation). The translation team wishes to indicate that it has approved the translation for release assuming the source is approved (or perhaps doesn't even know the approval status of the source).
 *   Source release = yes; Target release = no; The source has been released for publication but the review process is not completed for the target.
 *   Source release = yes; Target release = yes; everyone is happy.
 *   Source release = no; Target release = no; A draft of the source text has been sent on to the translator in advance of formal approval (to get a leg up on translation). The translation team also wishes to indicate that the translation provided is a proposal (perhaps they want feedback on it) and is not ready for publication.

I can think of two ways to handle these scenarios off the top of my head:


 1.  We have separate data categories for source and target. This strikes me as the way a workflow would handle this issue.
 2.  We bind the metadata to a lang declaration. This seems to be the way a content repository would handle this issue.

I am marking the chart up as though there were a unified data category (i.e., according to option 2), but think that this category needs more attention.

-Arle
Received on Wednesday, 11 April 2012 12:02:35 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 9 June 2013 00:24:55 UTC