Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <761651575.1223561926280.JavaMail.jira@brutus>
Date: Thu, 9 Oct 2008 07:18:46 -0700 (PDT)
From: "Julian Reschke (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Created: (JCR-1796) DAV compliance class for observation
 should use a URI instead of a token
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

DAV compliance class for observation should use a URI instead of a token
------------------------------------------------------------------------

                 Key: JCR-1796
                 URL: https://issues.apache.org/jira/browse/JCR-1796
             Project: Jackrabbit
          Issue Type: Bug
          Components: jackrabbit-webdav
            Reporter: Julian Reschke
            Priority: Minor


Currently, the DAV compliance class constant for the observation feature uses the string "observation".

However, RFC 4918 suggests that tokens are reserved for things defined through the IETF standards process:

"The value is a comma-separated list of all compliance class identifiers that the resource supports. Class identifiers may be Coded-URLs or tokens (as defined by [RFC2616]). Identifiers can appear in any order. Identifiers that are standardized through the IETF RFC process are tokens, but other identifiers SHOULD be Coded-URLs to encourage uniqueness." -- http://greenbytes.de/tech/webdav/rfc4918.html#rfc.section.10.1

...which is not the case for Observation. Thus, a coded-url should be used.

(unless no client actually needs it, in which case we should juet get rid of it)


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.