AW: MLW-LT Data categorie > process state

Hello Arle,

 

I am fine with the inclusion of Pedro's data category. The discussion I tried
to trigger wasn't specific to that category.

 

Cheers,

Moritz

 

Von: Arle Lommel [mailto:arle.lommel@gmail.com] 
Gesendet: Donnerstag, 5. April 2012 14:50
An: Pedro L. Díez Orzas
Cc: public-multilingualweb-lt@w3.org
Betreff: Re: MLW-LT Data categorie > process state

 

Hi Pedro,

 

I've implemented the other ones, but since it seems like there is some
discussion about this topic, I think I am going to hold off on implementing
the changes until I'm clear what the results will be. Perhaps later today
we'll be clear.

 

-Arle

 

Sic scripsit Pedro L. Díez Orzas in Apr 4, 2012 ad 19:48 :





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, 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 INTERNACIONALIZACIÓN DE
SERVICIOS, S.A. If you do not wish your 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. Your request will be processed immediately."

 ____________________________________