Fw: [cmis-comment] HREF values in Link Relation URIs, etc

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

Mary,

How should we handle the CMIS specific link relations. They are not a namespace, XSD, or WSDL, but a string in URI form to convey meaning. They are very specific to AtomPub and the new Link header for HTTP.

For example, they are used like:

<link rel="http://docs.oasis-open.org/ns/cmis/link/200901/allowableactions" href=""foo"" />

That link element identifies a related resource (foo) of relation http://docs.oasis-open.org/ns/cmis/link/200901/allowableactions (e.g., displays a document describing the allowed actions on that resource).

Should a new style of a namespace document be created for each of the cmis specific link relations? There are not 31 of them - more like 6 or so.

Thanks,
-Al

Al Brown
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.
----- Forwarded by Al Brown/Costa Mesa/IBM on 11/05/2009 03:07 PM -----

From: Robin Cover <robin@oasis-open.org>
To: CMIS Comment List <cmis-comment@lists.oasis-open.org>
Cc: Robin Cover <robin@oasis-open.org>
Date: 11/05/2009 02:09 PM
Subject: [cmis-comment] HREF values in Link Relation URIs, etc

---

In the CMIS Public Review draft (CD 04) at
http://docs.oasis-open.org/cmis/CMIS/v1.0/cd04/cmis-spec-v1.0.html

I noted several HTML links where the anchor HREF attribute values are
different than the anchor element content, viz., the underlying
HTML code in the HREF value appears to be incorrect, while the
display text is apparently correct.

Actually, this appears not to be a root HTML problem, but a defect in
the editable source (.doc) from which HTML and PDF were apparently
generated.

Perhaps 30 or more of these, for example, in the section
"CMIS Specific Link Relations":

[a href=""

http://docs.oasis-open.org/ns/cmis/link/200901/allowableactions
"]
http://docs.oasis-open.org/ns/cmis/link/200908/allowableactions

etc.

test:
$ grep -c 200901 cmis-spec-v1.0.html
31

-rcc

--

Robin Cover
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: robin@oasis-open.org
Staff bio: http://www.oasis-open.org/who/staff.php#cover
Cover Pages: http://xml.coverpages.org/
Newsletter: http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-296-1783

--
This publicly archived list offers a means to provide input to the
OASIS Content Management Interoperability Services (CMIS) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: cmis-comment-subscribe@lists.oasis-open.org
Unsubscribe: cmis-comment-unsubscribe@lists.oasis-open.org
List help: cmis-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/cmis-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=cmis