Mismatch in ModificationException term naming

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • V4.01_CS02
    • Affects Version/s: V4.01_CSD03
    • Component/s: Protocol, Vocabularies
    • None
    • Environment:

      [Proposed]

    • Hide

      a. Update the protocol document to refer to "Core.ModificationException", or
      b. Update the Core.Vocabulary to prefix "Data" to "ModificationException", "ModificationExceptionType", and "ModificationOperationKind"

      I kinda prefer the prefixed name (b), although it is slightly longer. However, the vocabulary changes are "live" where-as the protocol document has not yet been finalized, so b) would technically be a breaking change to anyone using the new vocabulary term, although it could be argued that it's unlikely that people are already using that term.

      Show
      a. Update the protocol document to refer to "Core.ModificationException", or b. Update the Core.Vocabulary to prefix "Data" to "ModificationException", "ModificationExceptionType", and "ModificationOperationKind" I kinda prefer the prefixed name (b), although it is slightly longer. However, the vocabulary changes are "live" where-as the protocol document has not yet been finalized, so b) would technically be a breaking change to anyone using the new vocabulary term, although it could be argued that it's unlikely that people are already using that term.
    • Show
      https://github.com/oasis-tcs/odata-vocabularies/pull/60/files  

      In our last F2F we added a new term for annotating failed data modifications within a bulk (i.e., delta) payload. We went back and forth on the naming, and ended up with different names between the vocabulary and the protocol document.

      The protocol document, in section 11.4.12, Update a Collection of Entities, refers to the "Core.DataModificationException". However, the Core vocabulary defines "ModificationException" along with "ModificationExceptionType" and "ModificationOperationKind".

            Assignee:
            Unassigned
            Reporter:
            Michael Pizzo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: