REST and State

["Toby Considine" <Toby.Considine@gmail.com>]

(retitled to follow conversation fork.)

 

 

Example: Many proposals in California et al. suggest that the price information itself be continuously broadcast on a reserved FM brand. DR days are in some places today submitted into the emergency CAP system and broadcast as CAP Alerts. EMIX is compatible with either of them. Energy Interoperation may have to encompass both of them [note to self – add to current draft]

 

Smart grid activities must embrace a variety of architectures. The value of certain kinds of infrastructure in a rural environment with miles between meters and little chance of picking up the neighbors wireless signals is quite different from that in a high-rise condo, with 100 meters in a small room, and no easy way to determine whose dishwasher is wirelessly binding to whose DR decisions.

 

tc

---

"If something is not worth doing, it`s not worth doing well" - Peter Drucker

---

Toby Considine TC9, Inc Chair, OASIS oBIX Technical Committee OASIS Technical Advisory Board

Email: Toby.Considine@gmail.com Phone: (919)619-2104 http://www.oasis-open.org blog: www.NewDaedalus.com

 

 

From: Considine, Toby (Campus Services IT) [mailto:Toby.Considine@unc.edu]
Sent: Wednesday, August 12, 2009 8:59 AM
To: 'Brian Frank'; 'William Cox'
Cc: 'smartgrid-interest@lists.oasis-open.org'; 'Toby Considine'
Subject: RE: [smartgrid-interest] Energy Market Information Exchange Charter - supporters wanted; ready for submission to create Technical Committee

 

Restful interactions have their place. As APIs at a distance, they are clean and predictable. As part of transactional systems and open bidding markets, one needs the rest of the WS Transaction infrastructure. As part of a massively distributed delayed environment that may involve long running workflows, one may need a multi-document messaging based format.

 

Zooming in on REST is a little like zooming in on UDP, only a couple layers up. There are times when RESTful connections are exactly what one needs. There are times when they are not.

 

tc

---

"A man should never be ashamed to own that he has been in the wrong, which is but saying ... that he is wiser today than yesterday." -- Jonathan Swift

---

Toby Considine Chair, OASIS oBIX TC Facilities Technology Office University of North Carolina Chapel Hill, NC

Email: Toby.Considine@ unc.edu Phone: (919)962-9073 http://www.oasis-open.org blog: www.NewDaedalus.com

 

 

From: Brian Frank [mailto:brian@skyfoundry.com]
Sent: Wednesday, August 12, 2009 8:42 AM
To: William Cox
Cc: smartgrid-interest@lists.oasis-open.org; Toby Considine
Subject: Re: [smartgrid-interest] Energy Market Information Exchange Charter - supporters wanted; ready for submission to create Technical Committee

 

Energy Market Information Exchange is an XML vocabulary to express price and characteristics, so the means of communicating is not part of the charter.

 

I can see how that is nice in theory, but I don't understand how that works in practice.  At the very least any sophisticated modeling requires naming things.  And naming things typically implies a way to reference those named things.

 

So I guess my question is - will the model be RESTful in that "things" are named and referenced with URIs?