Uploaded image for project: 'OASIS Energy Interoperation TC'
  1. OASIS Energy Interoperation TC
  2. ENERGYINTEROP-653

Issues with Conformance statements

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: wd35
    • Fix Version/s: wd36
    • Component/s: None
    • Labels:
      None
    • Environment:

      Ed Koch

    • Proposal:
      Hide

      line 2080 currently says: Service and Operation payloads.

      This line should be deleted.

      line 2097 has the following sentance: In addition, interoperation payloads MUST be used as defined or extended; in the event that payloads are 2097 extended a description of the extension(s) SHALL be included in the Implementation's conformance 2098 statement.

      This sentence should have the MUST changed to a SHOULD to says the following:

      In addition, interoperation payloads SHOULD be used as defined or extended; in the event that payloads are 2097 extended a description of the extension(s) SHALL be included in the Implementation's conformance 2098 statement.

      Furthermore to allow flexibility in defining product profiles within the OpenADR Alliance I recommend that we soften the language on the requirements for services. More specifically line 2032 is the following sentence:

      We present in simplified tabular form the Energy Interoperation services required as part of the OpenADR Profile.

      This sentence should be modified in the following way:

      We present in simplified tabular form the Energy Interoperation services that SHOULD be supported as part of the OpenADR Profile.

      Show
      line 2080 currently says: Service and Operation payloads. This line should be deleted. line 2097 has the following sentance: In addition, interoperation payloads MUST be used as defined or extended; in the event that payloads are 2097 extended a description of the extension(s) SHALL be included in the Implementation's conformance 2098 statement. This sentence should have the MUST changed to a SHOULD to says the following: In addition, interoperation payloads SHOULD be used as defined or extended; in the event that payloads are 2097 extended a description of the extension(s) SHALL be included in the Implementation's conformance 2098 statement. Furthermore to allow flexibility in defining product profiles within the OpenADR Alliance I recommend that we soften the language on the requirements for services. More specifically line 2032 is the following sentence: We present in simplified tabular form the Energy Interoperation services required as part of the OpenADR Profile. This sentence should be modified in the following way: We present in simplified tabular form the Energy Interoperation services that SHOULD be supported as part of the OpenADR Profile.
    • Resolution:
      Hide

      Use text in http://www.oasis-open.org/committees/download.php/44276/energyinterop-conformance-changes%2B20111108.pdf .

      This clarifies and simplifies the conformance statements; implementations not implementing all services and artifacts ("Full Conformance") list the services and operations and information types that they are not implementing, or have extended (brief summary).

      Show
      Use text in http://www.oasis-open.org/committees/download.php/44276/energyinterop-conformance-changes%2B20111108.pdf . This clarifies and simplifies the conformance statements; implementations not implementing all services and artifacts ("Full Conformance") list the services and operations and information types that they are not implementing, or have extended (brief summary).

      Description

      The new conformance section that was added in wd35 seems too restrictive if the OpenADR Alliance is going to claim they are conformant with EI. In general there are two things the Alliance wants to do that may not be in line with the conformnace statements:

      (1) Create product profiles wherein some of the profiles do not implement all of the services in the OpenADR profile.

      (2) Create transport specific payloads that are particular to the networking means that they are pursuing, i.e. not SOAP.

      Both these are reasonable approaches to how they are profiling the EI spec and do not effect the data schema's, or the type of services and operations that are supported.

      In the proposal section of this JIRA I am recommending some very explicit and minor mods to the language to allow for the above objectives within the Alliance to be achieved and still claim conformance to EI.

        Attachments

          Activity

            People

            • Assignee:
              william.cox William Cox (Inactive)
              Reporter:
              ed.koch Ed Koch (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: