[OASIS Issue Tracker] (ENERGYINTEROP-720) Market Rules Enforcement

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/ENERGYINTEROP-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated ENERGYINTEROP-720:
--------------------------------------
    Resolution: 
Actor behavior is filtered through the narrow CTS definition. Enforcement of market rules includes EiResponse to describe why a request is rejected.

Reconsider this analysis for Public Review 2, as much has changed.

> Market Rules Enforcement
> ------------------------
>
>                 Key: ENERGYINTEROP-720
>                 URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-720
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: cts
>    Affects Versions: CTSPR01
>         Environment: Horia Pop; Lateral Inc https://lists.oasis-open.org/archives/energyinterop-comment/202112/msg00001.html
>            Reporter: Toby Considine
>            Assignee: Toby Considine
>            Priority: Major
>              Labels: FACET, MARKET
>             Fix For: ctsWD16, ctsWD17
>
>
> *Market Rules Enforcement*
> Until the standard covers the facets, operation, and information models of an auditor and enforcer actor, the free interoperation of distinct conforming implementation is going to be hindered. It is hard to imagine a vendor accepting a standard-conforming actor with a distinct implementation to trade freely, knowing it can introduce malicious behavior and that thereÃs no standard way to inhibit it that the actor would oblige by.
> _[Lines 195]_



--
This message was sent by Atlassian Jira
(v8.3.3#803004)