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

 


Help: OASIS Mailing Lists Help | MarkMail Help

emix message

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


Subject: Re: Some meta-requirements on price communication


I know that replying to one's own email says something ... I just wanted to pass this on related to the "attributed to Einstein" statement.

See http://www.entish.org/wordpress/?p=638 for a search through Einstein's and other published writings. And you'll see why I said "attributed".

Thanks!

bill
--
William Cox
Email: wtcox@CoxSoftwareArchitects.com
Web: http://www.CoxSoftwareArchitects.com
+1 862 485 3696 mobile
+1 908 277 3460 fax


William Cox wrote:
4AE9AC88.9000905@CoxSoftwareArchitects.com" type="cite">We'll have an interesting discussion on characteristics at today's meeting. I wanted to put in writing a succinct summary of what I think of as meta-requirements on our output, that is, requirements by which we can judge the quality of our solutions.

This list is in no particular order; it's drawn (in part) from Toby's and my paper for Grid-Interop 2009 on Price Communication and Product Definition.  And it's a mix of metarequirements and some specific solutions; some raise additional questions (e.g. how is "source" identified; how much of market context needs to be conveyed, how maintain a reasonable size schema in the face of subsetting).

I expect this to lead to some productive arguments in conjunction with the relevant characteristics discussions.
  1. Microstandard/XML vocabulary and data model to be reusable in other specifications
  2. Works inside, outside, to, and from microgrids and district power associations
  3. Subsettable for smaller and larger devices, for where the context is better or less well understood
  4. Avoid pulling in huge schemas for something simple (e.g. currency)
  5. Common elements are part of base schema
    1. Unit price, units, currency
    2. Source and/or other indication of market-significant characteristics, e.g., hard coal, soft coal, soft coal with scrubber, hydro, gas, etc
    3. Possibly carbon characteristics (whether informative or normative)
    4. Possibly initiator (market source) and intermediaries (doubtful to me)
  6. Exensible characteristics--we don't know what the future holds
    1. Additional details unknown today
    2. Mechanism for extension
      1. Consider SOA-EERP BQOS; may have baggage
    3. Management of extension namespace
  7. "Make everything as simple as possible, but not simpler." (attributed to Einstein)
Thanks!

bill
--
William Cox
Email: wtcox@CoxSoftwareArchitects.com
Web: http://www.CoxSoftwareArchitects.com
+1 862 485 3696 mobile
+1 908 277 3460 fax


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