COEL - Does format = name/value pairs? replace sections with JSON objects

    • Hide

      If what was meant was that the JSON objects Cluster, Class, Sub-class and Element share the same name/value pairs, let's say that.

      It is clearer and enables implementations to write and read those name/value pairs in any order.

      Show
      If what was meant was that the JSON objects Cluster, Class, Sub-class and Element share the same name/value pairs, let's say that. It is clearer and enables implementations to write and read those name/value pairs in any order.

      3.2.1 Artefact Format: reads in part:

      *****
      The Cluster, Class, Sub-class and Element sections of the JSON artefact SHALL all have the same format.
      *****

      You claim RFC4627 as a normative reference so do you mean to depart from the unordered nature of JSON objects or is the "format" limited to requiring the "fields" listed? (Fields being a defined term in JSON.)

            Assignee:
            paul.bruton
            Reporter:
            Chet Ensign
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: