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-710) Minimal and Fractal

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

William Cox updated ENERGYINTEROP-710:
See comments.

6. Extension does not allow simplification of the type taken (e.g. refactoring the Emix Basek complexity). See other responses.

7. Supply and demand curves are supported as of WD17

10. Addresses current software engineering practice.

> Minimal and Fractal
> -------------------
>                 Key: ENERGYINTEROP-710
>                 URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-710
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: cts
>    Affects Versions: CTSPR01
>         Environment: Donald Hammerstrom https://lists.oasis-open.org/archives/energyinterop-comment/202111/msg00008/2111DJH_CTS_Review.pdf
>            Reporter: Toby Considine
>            Assignee: William Cox
>            Priority: Major
>              Labels: ARCH-CONF
>             Fix For: ctsWD16
> There are 30 specific recommendations in the "Specific Recommendations" section of the submitted Hammerstrom paper. I have numbered them all for traceability as I recombine them into specific issues. The original white paper/submission can be read in the URI under "environment"
> 6. Section 1.6: Iâm awaiting the novel value of this âminimal transactive profile.â If valuable, why are the referenced standards not being extended instead of creating a separate CTS standard?Â
> 7. Section 2.1.1: This claim of hierarchical or âfractalâ application of CTS is questionable. It seems that CTS provides means of procuring needed and selling surplus energies in time, but it does not aggregate the opportunities that could be embedded in an aggregate supply or demand curve. It is unlikely that dissimilar aggregated devices or prioritizable actor preferences can be combined at the same identical strike price.Â
> 10. Section 2.2.1: This treatment of âfacetsâ seems to be a step backward and is not architecturally sound. The âfacetsâ are first introduced as properties of interactions and later as Actor roles. These are certainly not actor roles and do not inherently even belong to Actors. What an odd mix! (Maybe these are âinteraction profilesâ?)Â
> Â

This message was sent by Atlassian Jira

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