RE: [cmis] Specifying natural language for a document

[Al Brown <albertcbrown@us.ibm.com>]

CMIS itself does not include support for multi-language objects (docs & folders) though the renditions proposal is a step forward. The renditions proposal allows a docId for each rendition which could hold enough info to return the language-specific version of the properties. E.g., the [cmis] docId in the rendition could be "24;fr-FR" for the french version of #24.

In REST/AtomPub when you expose the children, each atom entry should include addition link elements like:

<link rel="alternate" href=""<service>/documents/24?lang=fr-FR" hreflang="fr-FR" />

That would at least expose the alternate language versions of the object via REST.

-Al

Al Brown
Emerging Standards and Industry Frameworks
CMIS: https://w3.tap.ibm.com/w3ki07/display/ECMCMIS/Home
Industry Frameworks: https://w3.tap.ibm.com/w3ki07/display/ECMIF/Home

Office 714 327 3453
Mobile 714 263 6441
Email albertcbrown@us.ibm.com
CONFIDENTIAL NOTICE: The contents of this message, including any attachments, are confidential and are intended solely for the use of the person or entity to whom the message was addressed. If you are not the intended recipient of this message, please be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify the sender. Please also permanently delete all copies of the original message and any attached documentation.

"Doug Domeny" ---06/11/2009 02:46:54 PM---I'm working on Rest/Atom binding, so I'm thinking of something like:

From:	"Doug Domeny" <ddomeny@ektron.com>
To:	<Randall_Craig@emc.com>
Cc:	<cmis@lists.oasis-open.org>
Date:	06/11/2009 02:46 PM
Subject:	RE: [cmis] Specifying natural language for a document

---

I'm working on Rest/Atom binding, so I'm thinking of something like:
 
<service>/folders/<folder-id>/children?lang=fr
 
However, 'lang' is not a CMIS-defined parameter.
 
Additionally, at Ektron, content ids are the same across languages. That is, content id 24 can exist for English, Spanish, and French. So,
 
<service>/documents/24 refers to the same content, but translated into multiple languages.
 
Therefore, I would need either some session/cookie variable or query string variable to specify the language.
 
<service>/documents/24?lang=fr-FR
 
I'm wondering how others have dealt with language when not using query.
 
Thanks,
Doug

---

From: Randall_Craig@emc.com [mailto:Randall_Craig@emc.com] 
Sent: Thursday, June 11, 2009 5:02 PM
To: Doug Domeny
Cc: cmis@lists.oasis-open.org
Subject: RE: [cmis] Specifying natural language for a document
 
Hi Doug.
 
This sounds like a matter of information architecture and modeling. For example, you could have an attribute on a type to indicate natural language. You could then leverage CMIS SQL and CMIS query facilities to retrieve content in the relevant natural language.
 
Are you looking for something beyond query-based support?
 
-Craig
 
From: Doug Domeny [mailto:ddomeny@ektron.com] 
Sent: Thursday, June 11, 2009 1:57 PM
To: cmis@lists.oasis-open.org
Subject: [cmis] Specifying natural language for a document
 
What concepts exist, if any, for specifying the natural language of a document?
 
For example, when getting the children in a folder, is there a way to limit the documents to a specific language?
 
Thanks,
Doug