Movatterモバイル変換

1 Preface

The Content RepositoryAPI for Java™ Technology Specification, Version 2.0 (JCR 2.0Specification) consists of a normative part and a non-normative part.

The normative partconsists of:

• This document,excluding the appendix.

• The source code ofand its subpackages.

• The Javadocreference.

In case of a conflictthis document takes precedence over the source code and the sourcecode takes precedence over the Javadoc.

The non-normative partconsists of:

• The appendix ofthis document.

• Thefile ofand its subpackages.

The JCR 2.0Specification was created and released through the Java CommunityProcess (JCP) under Java Specification Request 283 (JSR 283).

1.1 Previous Versions

The Content Repositoryfor Java™ Technology API Specification, Version 1.0 (JCR 1.0Specification) was created and released through the Java CommunityProcess (JCP) under Java Specification Request 170 (JSR 170).

1.2 Coverage

This document describesthe abstract repository model and Java API of JCR. The API isdescribed from a high-level, functional perspective. Consult theaccompanying Javadoc for full information on signature variants andexceptions.

1.2.1 Classes and Interfaces

Unless otherwiseindicated, all Java classes and interfaces mentioned are in thepackageand its subpackages. Non-JCR classes mentioned are always fullyqualified. The only exception is,which is used throughout and written simply as.

1.2.2 Null Parameters

When describing JCR APImethods, this specification and the Javadoc assume that allparameters passed are non-,unless otherwise stated. Ifis passed as parameter and its behavior is not explicitly describedin this specification or in the Javadoc, then the behavior of themethod in that case is implementation-specific.

1.3 Typographical Conventions

A is used for JCR names and paths, andall instances of machine-readable text (Java code, XML, grammars,JCR-SQL2 examples, URIs, etc.).

1.3.1 String Literals in SyntacticGrammars

Formalgrammars are used at various places in the specification to definethe syntax of string-based entities such as names, paths, searchlanguages and other notations.

Whenastring literalappears as a terminal symbol within a grammar, each character literalin that string corresponds to exactly one Unicode code point.

Theintended code point of such a character literal must be determinedonly by reference to the Unicode Basic Latin code chart¹and no other part of the Unicode character set.

Anycode point outside the Basic Latin setcannotbe the intended code point of such a character literal, even if thegrapheme of the code point superficially resembles that of thecharacter literal.

Forexample, in the following production (excerpted from §3.2.2LocalNames).

The code pointsindicated by the character literals are, respectively,(“”),(“”),(““),(“”),(“”)and(“”).

1.4 SystemRequirements

The JCR 2.0 requiresJava Runtime Environment (JRE) 1.4 or greater.

1.5 License

Day Management AG(“Licensor”) is willing to license this specification to you ONLYUPON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THISLICENSE AGREEMENT (“Agreement”). Please read the terms andconditions of this Agreement carefully.

Content Repository forJava Technology API 2.0Specification (“Specification”)
Status: FCS
Release: 10August 2009

Copyright 2009 DayManagement AG
Barfuesserplatz 6, 4001 Basel, Switzerland.
Allrights reserved.

NOTICE; LIMITED LICENSEGRANTS

1. License for Purposesof Evaluation and Developing Applications. Licensor hereby grants youa fully-paid, non-exclusive, non-transferable, worldwide, limitedlicense (without the right to sublicense), under Licensor'sapplicable intellectual property rights to view, download, use andreproduce the Specification only for the purpose of internalevaluation. This includes developing applications intended to run onan implementation of the Specification provided that suchapplications do not themselves implement any portion(s) of theSpecification.

2. License for theDistribution of Compliant Implementations. Licensor also grants you aperpetual, non-exclusive, non-transferable, worldwide, fully paid-up,royalty free, limited license (without the right to sublicense) underany applicable copyrights or, subject to the provisions of subsection4 below, patent rights it may have covering the Specification tocreate and/or distribute an Independent Implementation of theSpecification that: (a) fully implements the Specification includingall its required interfaces and functionality; (b) does not modify,subset, superset or otherwise extend the Licensor Name Space, orinclude any public or protected packages, classes, Java interfaces,fields or methods within the Licensor Name Space other than thoserequired/authorized by the Specification or Specifications beingimplemented; and (c) passes the Technology Compatibility Kit(including satisfying the requirements of the applicable TCK UsersGuide) for such Specification (“Compliant Implementation”). Inaddition, the foregoing license is expressly conditioned on your notacting outside its scope. No license is granted hereunder for anyother purpose (including, for example, modifying the Specification,other than to the extent of your fair use rights, or distributing theSpecification to third parties).

3. Pass-throughConditions. You need not include limitations (a)-(c) from theprevious paragraph or any other particular “pass through”requirements in any license You grant concerning the use of yourIndependent Implementation or products derived from it. However,except with respect to Independent Implementations (and productsderived from them) that satisfy limitations (a)-(c) from the previousparagraph, You may neither: (a) grant or otherwise pass through toyour licensees any licenses under Licensor's applicable intellectualproperty rights; nor (b) authorize your licensees to make any claimsconcerning their implementation's compliance with the Specification.

4. ReciprocityConcerning Patent Licenses. With respect to any patent claims coveredby the license granted under subparagraph 2 above that would beinfringed by all technically feasible implementations of theSpecification, such license is conditioned upon your offering onfair, reasonable and non-discriminatory terms, to any party seekingit from You, a perpetual, non-exclusive, non-transferable, worldwidelicense under Your patent rights that are or would be infringed byall technically feasible implementations of the Specification todevelop, distribute and use a Compliant Implementation.

5. Definitions. For thepurposes of this Agreement: “Independent Implementation” shallmean an implementation of the Specification that neither derives fromany of Licensor's source code or binary code materials nor, exceptwith an appropriate and separate license from Licensor, includes anyof Licensor's source code or binary code materials; “Licensor NameSpace” shall mean the public class or interface declarations whosenames begin with “java”, “javax”, “javax.jcr” or theirequivalents in any subsequent naming convention adopted by Licensorthrough the Java Community Process, or any recognized successors orreplacements thereof; and “Technology Compatibility Kit” or “TCK”shall mean the test suite and accompanying TCK User's Guide providedby Licensor which corresponds to the particular version of theSpecification being tested.

6. Termination. ThisAgreement will terminate immediately without notice from Licensor ifyou fail to comply with any material provision of or act outside thescope of the licenses granted above.

7. Trademarks. Noright, title, or interest in or to any trademarks, service marks, ortrade names of Licensor is granted hereunder. Java is a registeredtrademark of Sun Microsystems, Inc. in the United States and othercountries.

8. Disclaimer ofWarranties. The Specification is provided “AS IS”. LICENSOR MAKESNO REPRESENTATIONS OR WARRANTIES, EITHER EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESSFOR A PARTICULAR PURPOSE, NON-INFRINGEMENT (INCLUDING AS ACONSEQUENCE OF ANY PRACTICE OR IMPLEMENTATION OF THE SPECIFICATION),OR THAT THE CONTENTS OF THE SPECIFICATION ARE SUITABLE FOR ANYPURPOSE. This document does not represent any commitment to releaseor implement any portion of the Specification in any product.

The Specification couldinclude technical inaccuracies or typographical errors. Changes areperiodically added to the information therein; these changes will beincorporated into new versions of the Specification, if any. Licensormay make improvements and/or changes to the product(s) and/or theprogram(s) described in the Specification at any time. Any use ofsuch changes in the Specification will be governed by thethen-current license for the applicable version of the Specification.

9. Limitation ofLiability. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILLLICENSOR BE LIABLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION,LOST REVENUE, PROFITS OR DATA, OR FOR SPECIAL, INDIRECT,CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED ANDREGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TOANY FURNISHING, PRACTICING, MODIFYING OR ANY USE OF THESPECIFICATION, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITYOF SUCH DAMAGES.

10. Report. If youprovide Licensor with any comments or suggestions in connection withyour use of the Specification (“Feedback”), you hereby: (i) agreethat such Feedback is provided on a non-proprietary andnon-confidential basis, and (ii) grant Licensor a perpetual,non-exclusive, worldwide, fully paid-up, irrevocable license, withthe right to sublicense through multiple levels of sublicensees, toincorporate, disclose, and use without limitation the Feedback forany purpose related to the Specification and future versions,implementations, and test suites thereof.

1.6 Acknowledgements

The following peopleand organizations have contributed to this specification:

David Nuescheler(Specification Lead)

Peeter Piegaze (Principal Author)