[#CMIS-355] Change namespace delimiter to a url safe character - OASIS Technical Committees Issue Tracker

OASIS Content Management Interoperability Services (CMIS) TC

Change namespace delimiter to a url safe character

Created: 15/Jul/09 09:52 AM Updated: 27/Jul/09 12:20 PM

Component/s:

Domain Model

Affects Version/s:

Draft 0.62

Fix Version/s:

None

Description

« Hide

Type/Property Ids contain ":" for the namespace delimiter. However, these have to be encoded when placed in a URL path. This is an issue for the AtomPub binding of getType/s, if an implementation chooses to embed the type id in the path.

All

Comments

Change History

Sort Order:

[ Permalink | « Hide ]

Florent Guillaume added a comment - 15/Jul/09 11:02 AM

RFC3986 talks about many *potential* reserved characters (2.2), but leaves it to each scheme to define which ones are actually reserved:
> These characters are called "reserved" because they may (or may not)
> be defined as delimiters by the generic syntax, by each scheme-specific syntax...

My reading of RFC1738 (3.3) is that only "/", ";" and "?" are reserved for HTTP.

So I don't think a ":" has to be escaped.

[ Permalink | « Hide ]

David Caruana added a comment - 15/Jul/09 11:40 AM

In that case, this issue can be closed. Thanks Florent.

[ Permalink | « Hide ]

Al Brown added a comment - 15/Jul/09 07:28 PM

David,

Can you check this quickly on your impl? E.g., see if a browser or appserver has issues with - http://alfrescco/rep1/type/cmis:document

[ Permalink | « Hide ]

Florent Guillaume added a comment - 16/Jul/09 06:18 AM

Googling a bit I found .NET people having problems: http://forums.iis.net/t/1149909.aspx
But this is the internet, they may be wrong or overlooking something. So somebody with .NET should check that it can parse such URLs all right

[ Permalink | « Hide ]

Al Brown added a comment - 17/Jul/09 12:01 PM

How about cmis- instead of cmis: for our prefixes? Should do the same job. Since we don't parse them anymore (it's opaque) it is really just a prefix to prevent casual collisions with types and properties a customer/isv may create

[ Permalink | « Hide ]

Florent Guillaume added a comment - 17/Jul/09 12:45 PM

Well it's not an issue only with the "cmis" prefix of course, all vendors may have their own prefixes also. It seems strange to use "-" as a delimiter for that.

[ Permalink | « Hide ]

Al Brown added a comment - 17/Jul/09 01:11 PM

~~CMIS-317~~ removed parsing of id to support extraction of prefixes. Ids are opaque strings and CMIS specifies values for Id. The values it specifies are 'cmis:document' for example.

Since it is really just a prefixing for cmis properties and not namespaces/prefixes (namespace is in a separate attribute now) and the id property is completely opaque, I think it makes sense to use cmis- rather than cmis: given the potential url encoding issue. or cmis/, really any character that does not run into the limitations on queryname and do not need url encoding.

[ Permalink | « Hide ]

Al Brown added a comment - 20/Jul/09 12:34 PM

deferred to give tc time to test with :
current consensus is to leave as is if no issues

[ Permalink | « Hide ]

Al Brown added a comment - 27/Jul/09 12:20 PM

closed by tc