RE: MLW-LT Data categorie > process state

Dear all,

 

Thank you very much Moritz. Our opinion is that this should be included
because this is included in the scope, since the 3 main goals of LT-Web are:

 

(http://cordis.europa.eu/projects/rcn/101839_en.html):

The goal of LT-Web is to set the foundation for the integration of language
technologies into core Web technologies, via the creation of a standard
defining three kinds of metadata about: 1) information in Web content being
relevant for language technology processing; 2) processes for creating Web
content via localisation and content management work flows; 3) language
technology applications and resources used in these applications. The
organizations participating in LT-Web will join the World Wide Web
Consortium (W3C) and create a group defining the metadata standard, within
the Internationalization Activity of W3C. 

 

We think that the “process state” or “process trigger” responds to the 2nd
goal: 2) processes for creating Web content via localisation and content
management work flows. Also, we think this is one of the most interensting
part for part of the implementations of WP3. We also consider that the data
model we proposed do not contain really fine-grained process info, but only
the basic info to widely define any localisation process (concerning
workflows, for intance: processRequested –value: code or plain text (e.g. an
action or workflow name)).

 

Best,

Pedro

 

 

  _____  

De: Moritz Hellwig [mailto:Moritz.Hellwig@cocomore.com] 
Enviado el: jueves, 05 de abril de 2012 14:44
Para: "Pedro L. Díez Orzas"; public-multilingualweb-lt@w3.org
Asunto: AW: MLW-LT Data categorie > process state

 

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:  <mailto:pedro.diez@linguaserve.com> 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."

 ____________________________________