Note that in a level 1 implementation clients will not be able to re-order, add or remove nodes or change properties in any case. However, the orderable-status, property definitions and child node definitions may still provide information related to write-capabilities that a level 1 implementation cannot in practice perform through this API.
This might be the case, for example, if a particular node-type happens to be shared with a level 2 repository. In general, the node type discovery methods will reflect the definition of the node type, regardless of the level of repository in which the node type happens to be found.
For this reason, the descriptions in this section often refer to write-related issues that will only be applicable in a level 2 repository.