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

Re: Missing requirment - content format/type

From: David Lewis <dave.lewis@cs.tcd.ie>
Date: Mon, 30 Apr 2012 23:47:23 +0100
Message-ID: <4F9F167B.8060209@cs.tcd.ie>
To: public-multilingualweb-lt@w3.org
Hi Yves,
The text we currently have in the requirements for the content data 
category seems very similar, albeit a subset of, the values defined for 
restype in XLIFF.

Yves, I'm not very familiar with this feature in XLIFF, could you 
provide a bit more background on where it used and by whom?

Context came out as a major issue in questionnaire, but I'm not sure how 
much further we should go beyond the HTML5 tags, without getting 
specific e.g. to particular XML vocabularies, or too scripting language 
which we were leaving out of scope?


On 30/04/2012 20:45, Yves Savourel wrote:
>>> Format type though is something different. The examples
>>> >>  given (e.g., subtitles, spoken text)  seem to indicate
>>> >>  its more a specification of the intended delivery modality.
>> >
>> >  formatType wasn't from me. It was in the original requirements
>> >  doc, IIRC, and I just ported it over. It was not always clear
>> >  where things came from.
>> >  ...
>> >  I do think, however, that your description of formatType is correct:
>> >  it was designed to convey something to the translator (who might
>> >  see only an XML file) something about the intended destination
>> >  at the end of the process.
> Like if the text to translate is a caption, a button, a menu label?
> It seems formatType would then be some sort of 'type of resource', like the restype of XLIFF.
> If not, it would be closer to the context data category.
> -ys
Received on Monday, 30 April 2012 22:47:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:08:16 UTC