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

[all] Discussion on proposed metadata categories: approvalStatus

From: Moritz Hellwig <Moritz.Hellwig@cocomore.com>
Date: Tue, 24 Apr 2012 12:11:46 +0200
Message-ID: <A5F4BCC8EDECF74D97DBCEF820F7269FB8980B@cocont10.office.cocomore.com>
To: <public-multilingualweb-lt@w3.org>
Hello all,

 

I've been talking to our editorial team to identify publication process
metadata which might also be relevant for the LSP. I ran into a couple of
questions though.

 

I'll use approvalStatus as an example (from the requirements document):

>> approvalStatus 

>> Information about the status of the content in a formal approval workflow

>> Indicates whether the content has been approved for release 

>> Possible values:

>>>> yes

>>>> no

 

Approval can have many values which are rarely only "release yes|no" and they
can be client/application-specific. However, none of these statuses seem to
be relevant to the LSP, as they only precede or succeed the LSP's processes.

 

There might be one exception: When a translation shouldn't be begun before a
certain date / time, yet the content itself is transferred to the LSP ahead
of time. This might be a rare use case though. And it might be more aptly
covered by process trigger, rather than by a further metadata category:

>> processTrigger

>>>> dateEarliestStart - value: date and time

>>>> Defines the earliest date / time when LSP workflows may start.

Does anybody have any real applications / use cases for this?

 

We can of course put approvalStatus into content. If no other process will
look at it though, I find it redundant for MLW-LT.

 

Any thoughts? Am I missing something? Are there use cases where the approval
status of a piece of content will affect the LSP?

 

Cheers,

Moritz
Received on Tuesday, 24 April 2012 10:12:34 UTC

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