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

Re: AW: MLW-LT Data categorie > process state

From: Dave Lewis <dave.lewis@cs.tcd.ie>
Date: Thu, 05 Apr 2012 15:20:58 +0100
Message-ID: <4F7DAA4A.5060301@cs.tcd.ie>
To: public-multilingualweb-lt@w3.org
Hi Moritz, Pedro,
you raise an important point that was brought up here, which also came 
up at the MLW workshop in luxembourg. Just explaining the use of these 
data categories requires some expression of the different processes 
involved before we even get onto the separate point of whether we need a 
data category.

I had a related post earlier in:

I will raise an issue so this is on the table for the next teleconf.

For now I'd like to suggest the following:
1) we add two column to Arle's data category summary table in:
One to list processes that produce that meta-data and one to list 
processes that consumer that meta-data

2) We settle on an initial set of process names and populate those 
column with them. The end to end use case gives us a list of processes 
we can start from:

This should give us a good initial overview of which data categories are 
relevant where (it will also help deceide which one are relevant to 
which of the planned implementations).

lets discuss this tomorrow.

On 05/04/2012 13:43, Moritz Hellwig wrote:
> Hello all,
> Cheers for the update.
> As the list of data catagories is becoming quite large, I'd like to 
> pose a question: Is MLW-LT metadata meant to include metadata for very 
> fine-grained processes in CMS content and/or language services too? 
> There are some categories which are mostly concerned with the 
> processing of content (e.g. the proposed process trigger to some 
> extent) and others are concerned with the content itself (no 
> translate, terminology, ...).
> I'm wondering whether we need to clarify how big the scope of the 
> requirements is supposed to be. From the CMS point of view, metadata 
> which can support content management and/or content publishing 
> workflows are a very good thing, but since we are not allowed to 
> remove metadata from content, metadata in the content can become very 
> big it seems. Personally, I think these information should be included 
> in the requirements document, but might be out of scope for the two 
> implementations necessary for the W3C Recommendation.
> Cheers,
> Moritz
> *Von:*"Pedro L. Díez Orzas" [mailto:pedro.diez@linguaserve.com]
> *Gesendet:* Mittwoch, 4. April 2012 19:48
> *An:* public-multilingualweb-lt@w3.org
> *Betreff:* MLW-LT Data categorie > process state
> Dear all,
> I do not know if this is a new issue, or it is related with issue-1, 
> or with ACTION-20 open Gather CMS user and developer perspective 
> requirements from MLW-LT, including from drupal con.
> I discussed with Arle, that the current metadata related with 
> localization processes where mostly "passive" (declaring the resulting 
> state) and not "active" (driving the following process). In the 
> current version of process state in the requirements it seems to 
> reflect also this disjunctive:
> We doubt that the current metadata do cover the metadata to express 
> "guidance for localization process", that is in the "active" sense.
> The data category "process state" should do it, by itself and/or by 
> using other additional data categories.
> In this sense, if "process state" is reserved for indicating "the 
> current state of the content within a localization process", we would 
> suggest another like "process trigger", and this data category could 
> have the following data model:
> *process trigger*
> provides information to guide a process of localization of content
> Data model
>   * processRequested --value: code or plain text (e.g. an action or
>     workflow name)
>   * contentFormat -values: plainText, xml, html3, html4, html5. El
>     level sería element.
>   * targetLangs - values: standard ISO values
>   * pivotLang - value: standard ISO value
>   * dateRequest --value: date and time
>   * dateDelivery --value: date and time
>   * priotity --value: numeric
>   * contentResult --value: monolingual, multilingual
> Other existing data categories can be also used combined with this, 
> like "provenance - source language" to express the source language; 
> "special requirements" to info about length limitations;
> *__________________________________***
> **
> *Pedro L. Díez Orzas*
> *Presidente Ejecutivo/CEO*
> *Linguaserve Internacionalización de Servicios, S.A.*
> *Tel.: +34 91 761 64 60
> Fax: +34 91 542 89 28 *
> *E-mail: **pedro.diez@linguaserve.com 
> <mailto:pedro.diez@linguaserve.com>***
> *www.linguaserve.com <http://www.linguaserve.com/>*
> **
> «En cumplimiento con lo previsto con los artículos 21 y 22 de la Ley 
> 34/2002, de 11 de julio, de Servicios de la Sociedad de Información y 
> Comercio Electrónico, le informamos que procederemos al archivo y 
> tratamiento de sus datos exclusivamente con fines de promoción de los 
> productos y servicios ofrecidos por LINGUASERVE INTERNACIONALIZACIÓN 
> DE SERVICIOS, S.A. En caso de que Vdes. no deseen que procedamos al 
> archivo y tratamiento de los datos proporcionados, o no deseen recibir 
> comunicaciones comerciales sobre los productos y servicios ofrecidos, 
> comuníquenoslo a clients@linguaserve.com 
> <mailto:clients@linguaserve.com>, y su petición será inmediatamente 
> cumplida.»
> "According to the provisions set forth in articles 21 and 22 of Law 
> 34/2002 of July 11 regarding Information Society and eCommerce 
> Services, we will store and use your personal data with the sole 
> purpose of marketing the products and services offered by LINGUASERVE 
> personal data to be stored and handled, or you do not wish to receive 
> further information regarding products and services offered by our 
> company, please e-mail us to clients@linguaserve.com 
> <mailto:clients@linguaserve.com>. Your request will be processed 
> immediately."
> *____________________________________***
Received on Thursday, 5 April 2012 14:15:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:43 UTC