- From: Yves Savourel <ysavourel@enlaso.com>
- Date: Fri, 13 Apr 2012 08:03:54 -0600
- To: "'Multilingual Web LT Public List'" <public-multilingualweb-lt@w3.org>
- Message-ID: <assp.0450d6b936.assp.0450e55e18.000401cd197e$437112f0$ca5338d0$@com>
Hi Arle, No objection, but my usual remark: the values for ‘format’ would need to be standardized. If it’s a format then maybe a MIME type could be used. Cheers, -yves From: Arle Lommel [mailto:arle.lommel@gmail.com] Sent: Friday, April 13, 2012 5:32 AM To: Multilingual Web LT Public List Subject: [terminology resource] expand this category? At present terminology resource is used to identify an (external) terminology resource. Could we expand this to become a language resource category? After all, a terminology resource is one type of language resource and at present we do not have a category to specify that the process should use a certain MT corpus or TM repository, so what if we change this to the following model: languageResource Identifies the appropriate language resources to be used for translation or other language-related tasks data model • type: (terminology|corpus|TM){1,1} • location: uri of resource{1,1} • format: text string identifying the format (e.g., "Multiterm", "TBX", "TMX"){1,1} • id: id value used to bind other metadata to this item.{1,1} • description: text description {0,1} Any objection to generalizing this? -Arle
Received on Friday, 13 April 2012 14:04:25 UTC