jsr-283
  1. jsr-283
  2. JSR_283-725

Clarification regarding same name property and node

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: current
    • Fix Version/s: milestone 1
    • Component/s: general
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      725

      Description

      Section 22.5 Property and Node with Same Name of the specification states that a
      repository may a property and node below the same parent having the same name.

      Is there a way how the API user can find out whether this is supported or not?
      We already defined quite some repository descriptors that indicate if the
      various nodetype specific options are allowed.

      So my question:

      Is the same-name property + name covered by the
      NODE_TYPE_MANAGEMENT_SAME_NAME_SIBLINGS_SUPPORTED descriptor? (section 22.5 is
      within 22.3 Reading and Writing Same-Name Siblings)

      Otherwise: can we define another descriptor for that?

      angela

        Issue Links

          Activity

          Hide
          Peeter Piegaze added a comment -

          We should define another descriptor. I don't think that this characteristic should be covered by NODE_TYPE_MANAGEMENT_SAME_NAME_SIBLINGS_SUPPORTED.

          Show
          Peeter Piegaze added a comment - We should define another descriptor. I don't think that this characteristic should be covered by NODE_TYPE_MANAGEMENT_SAME_NAME_SIBLINGS_SUPPORTED.
          Hide
          Peeter Piegaze added a comment -

          Looking at the spec again it seems that we intended to make "same name node and property" a fixed
          feature, not an option. See 3.1.3 "Names" for example. In that case the correct thing to do would be to
          move the section 22.5 "Property and Node with Same Name" to a new location outside the Same Name
          Siblings secion, since the features are not connected.

          Of course, a repository can effectively prevent this feature through the set of available node types or
          through a global constraint. However, since this is the case with so many "features" I don't think it
          warrants a descriptor of its own.

          Show
          Peeter Piegaze added a comment - Looking at the spec again it seems that we intended to make "same name node and property" a fixed feature, not an option. See 3.1.3 "Names" for example. In that case the correct thing to do would be to move the section 22.5 "Property and Node with Same Name" to a new location outside the Same Name Siblings secion, since the features are not connected. Of course, a repository can effectively prevent this feature through the set of available node types or through a global constraint. However, since this is the case with so many "features" I don't think it warrants a descriptor of its own.
          Hide
          Peeter Piegaze added a comment -

          Fixed.
          22.5 "Property and Node with Same Name" moved to 5.1.8 (under 5 "Reading"/5.1 "Direct Access")

          Show
          Peeter Piegaze added a comment - Fixed. 22.5 "Property and Node with Same Name" moved to 5.1.8 (under 5 "Reading"/5.1 "Direct Access")
          Hide
          stefan_guggisberg added a comment -

          > Looking at the spec again it seems that we intended to make "same name node and property" a fixed
          feature, not an option.

          i beg to differ. IMHO we shouldn't force an implementation to support this. personally i consider "same
          name node and property" rather a limitation (due to some underlying legacy system) than a feature since it
          renders a path ambiguous and might cause problems for content serialization formats.

          i would prefer that we add some wording like 'an implementation may ...', like we did in cvarious other
          places.

          Show
          stefan_guggisberg added a comment - > Looking at the spec again it seems that we intended to make "same name node and property" a fixed feature, not an option. i beg to differ. IMHO we shouldn't force an implementation to support this. personally i consider "same name node and property" rather a limitation (due to some underlying legacy system) than a feature since it renders a path ambiguous and might cause problems for content serialization formats. i would prefer that we add some wording like 'an implementation may ...', like we did in cvarious other places.
          Hide
          Peeter Piegaze added a comment -

          Clarified that this is an optional feature and added a new descriptor.

          Show
          Peeter Piegaze added a comment - Clarified that this is an optional feature and added a new descriptor.

            People

            • Assignee:
              jsr-283-issues
              Reporter:
              anchela
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: