operation UInt8 Specifies the operation requested of this item. 0=Create 1=Read 2=Update 3=Delete name HexBinary16 statusCode UInt16 Indicates the status code of the associated transaction. 200 - Ok 201 - Created 204 - No Content 301 - Moved Permanently 302 - Redirect 304 - Not Modified 400 - Bad Request 401 - Unauthorized 403 - Forbidden 404 - Not Found 405 - Method Not Allowed 410 - Gone 500 - Internal Server Error statusReason Object Name Type Description extension anyType ServiceStatus Name Type Description currentStatus UInt8 The current status of the service. 0 = Unavailable 1 = Normal, operational Subscription ApplicationInformation
not the "yes/no" determination by the various standards. See referenced standards for definition, measurement protocol and period. Name Type Description flickerPlt Int48 A measurement of long term Rapid Voltage Change in hundredths. flickerPlt is derived from 2 hours of Pst values (12 values combined in cubic relationship). flickerPst Int48 flickerPst is a value measured over 10 minutes that characterizes the likelihood that the voltage fluctuations would result in perceptible light flicker. A value of 1.0 is designed to represent the level that 50% of people would perceive flicker in a 60 watt incandescent bulb. The reported is represented as an integer in hundredths. Int48 Int48 mainsVoltage Int48 UInt8 A reference to the source standard used as the measurement protocol definition. Examples are: 0 = "IEEE1519-2009" 1 = "EN50160" Int48 Int48 DateTimeInterval Int48 Int48 Int48
Authorization [] authorization NotifyData_() BatchList [] batchList UpdateData_() [] data The following contains a listing of these Logical Interface Operations, along with the expected Physical Operation for informative purposes. Physical operation names in parentheses are passed programmatically Actor Description Logical Physical Data Custodian Ability to get service status ReadServiceStatus ServiceStatus Data Custodian Initiate signed request_token request per RFC 5849 CreateRequestToken request_token Data Custodian Initiate signed authorize request per RFC 5849 Authorize authorize Data Custodian Initiate signed access_token request per RFC 5849 CreateAccessToken access_token Data Custodian Update existing authorization NotifyUpdateAuthorization_ Authorization Data Custodian Revoke existing authorization (Retail Customer) NotifyUpdateAuthorization_ Authorization Data Custodian Terminate existing authorization via service UpdateAuthorization Authorization Data Custodian Request subscription to authorized resource CreateSubscription Subscription (from config) Data Custodian Request authorized data resource(s) RequestData (request_token scope) Data Custodian Receive requested and subscribed ReadData (dataCustodianDefaultBatchResource) Data Custodian Request and receive authorized ReadData_ (request_token scope) Party Initiate callback specified in request_token per RFC 5849 ProvideAuthorization (request_token callback) Third Party Revoke existing authorization (Data Custodian) NotifyUpdateAuthorization_ Authorization Third Party Send requested and subscribed UpdateData_ (thirdPartyDefaultBatchResource) Third Party Notify requested and subscribed is available NotifyData_ (thirdPartyDefaultNotifyResource)