Re: [cmis] unreadable property names and current clients?

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

On the property definition (inside the type definition), there should be a field property id that can be used to hold the URI or un-mangled form of the property. In addition, the specification allows the repository to expose more information via repository specific XSDs. such as <myrep:name>foo</myrep:name>. This is done through xs:any in the schema.

-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.

Julian Reschke ---03/04/2009 04:26:05 AM---Jens Hübel wrote:

From:	Julian Reschke <julian.reschke@greenbytes.de>
To:	Jens Hübel <jhuebel@opentext.com>
Cc:	cmis@lists.oasis-open.org
Date:	03/04/2009 04:26 AM
Subject:	Re: [cmis] unreadable property names and current clients?

---

Jens Hübel wrote:
 > ...
 > I have a question how the typical clients behave in regards of 
property names today.
 > ...

Related to that: many systems identify properties by [URI, localname] 
(JCR, WebDAV) or URI (RDF).

Can an CMIS implementation, while mangling that name for CMIS interop, 
expose it as supplementary information as well?

BR, Julian


-- 
<green/>bytes GmbH, Hafenweg 16, D-48155 Münster, Germany
Amtsgericht Münster: HRB5782


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php