Payloads in the model need care as to expected results

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • wd25
    • Affects Version/s: wd22
    • Component/s: model
    • None
    • Environment:

      William Cox

    • Hide

      Make decisions on the detailed semantics for all services including the EiConstraint service.

      Make names consistent across the spec and schema.

      Note that programName should be marketContextName or something similar (see ENERGYINTEROP-356 and ENERGYINTEROP-395

      RequestConstraint should send marketContextName, and not a list as the constraints are specific to the program.

      EiSentConstraint returns 0..3 constrains, as an error would return none, and there are (in wd22) three kinds of constraints.

      Document that there are up to three constraints per "program"/marketcontext (the relationship is not clear) and modify the model and spec and schema as required.

      Show
      Make decisions on the detailed semantics for all services including the EiConstraint service. Make names consistent across the spec and schema. Note that programName should be marketContextName or something similar (see ENERGYINTEROP-356 and ENERGYINTEROP-395 RequestConstraint should send marketContextName, and not a list as the constraints are specific to the program. EiSentConstraint returns 0..3 constrains, as an error would return none, and there are (in wd22) three kinds of constraints. Document that there are up to three constraints per "program"/marketcontext (the relationship is not clear) and modify the model and spec and schema as required.

      Consider EiConstraint payloads.

      When RequestConstraint is called it sends agreementName - should that be programName? Could it be a list? (probably not because the VTN for each program may be different).

      When EiSentConstraint returns does the payload consist of 0..* constraints or only one?

            Assignee:
            William Cox (Inactive)
            Reporter:
            William Cox (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: