OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

David Holmberg commented on ENERGYINTEROP-720:

It seems out of scope to define actor profiles. Or maybe it is like OpenADR 1.0a and b profiles. We could have CTS simple market profile that maybe doesn't include an enforcer agent, but does include the basic market agent, and basic participant. A basic participant agent sends tenders and receives transactions. Higher level participants include Quote, Position, Ticker facets. There also the Measurement agent? Or can we say that a facet *is* and interoperability profile? An enforcer actor used measurement and whatever else to evaluate the behavior of some participants. How it does that is something market specific or at least not defined in CTS.Â

> 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
> *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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]