Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <37643467.1245332467413.JavaMail.jira@brutus>
Date: Thu, 18 Jun 2009 06:41:07 -0700 (PDT)
From: "angela (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-2156) Usage of "qualified name" in JavaDoc
 and Comments
In-Reply-To: <833406606.1245243487535.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela resolved JCR-2156.
-------------------------

    Resolution: Fixed
      Assignee: angela

> Usage of "qualified name" in JavaDoc and Comments
> -------------------------------------------------
>
>                 Key: JCR-2156
>                 URL: https://issues.apache.org/jira/browse/JCR-2156
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core, jackrabbit-jcr2spi
>            Reporter: angela
>            Assignee: angela
>
> Within jackrabbit the term "qualified name" is used, when the internal representation of a JCR name is referred according to the usage of "fully-qualified name" within the JSR 170 specification.
> Based on input by julian (Issue #449) the phrasing has been adjusted in JSR 283 to match the terminology used in XMLNS.
> As of JSR 283
> - Qualified Name -> refers to a JCR Name in the form prefix:localname
> - Expanded Name -> is used for what was formerly called "fully-qualified name".
> In order to avoid confusion i would suggest to fix the javadoc throughout the project and eventually add explanations in cases where method or class names are misleading.

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