Thanks Declan,
I will try to draw up the data model for this item today. For the issue of lists, my assumption is that one would simply declare multiple instances of the data category. The scope of the element would be either the parent element (for ones declared within an element) or global (if declared, e.g., in the <head> element of an HTML5 file), but I can see some issues regarding overrides, etc., that we'd need to resolve.
-Arle
--
Dr. Arle Lommel
D-14197 Berlin â€¢ Wiesbadener StraÃŸe 18 â€¢ Germany
[U.S. mailing address: PO Box 190064 â€¢ Anchorage, Alaska 99519-0064 â€¢ USA]
Time zone: Central European Time (UTC+1, UTC+2 in summer)
Phone (U.S): +1.707.709.8650
Skype: arle_lommel
LinkedIn: http://www.linkedin.com/in/arlelommel
Sic scripsit Declan Groves in Apr 13, 2012 ad 16:51 :
> I'd support the idea of having a "languageResource" category. In terms of format I understand the need for standardisation here, but we need to be aware that it is far more common for people to use TMX,XLIFF,TBX etc. rather than a MIME type, so having the "other" option should cover this.
>
> languageResource should also allow for a list (it may already), as the process may be instructed to use multiple specified language resources e.g. a specific termbank plus a specific corpus etc.
>
>
> Declan
>
>
> On 13 April 2012 15:30, Yves Savourel <ysavourel@enlaso.com> wrote:
> > Yes, I think that would be wise, although I
> > suppose we would need an "other" option for those
> > things we don't anticipate, like someone wanting
> > to use "EBCDIC-encoded guillemot-delimited
> > bilingual glossary" ;-)
>
> Then they can register a MIME type for that :)
>
> http://tools.ietf.org/html/rfc2048#section-2.1.2
>
> cheers,
> -ys
>
>
>
>
>
> --
> Dr. Declan Groves
> Research Integration Officer
> Centre for Next Generation Localisation (CNGL)
> Dublin City University
>
> email: dgroves@computing.dcu.ie
> phone: +353 (0)1 700 6906