[OASIS Issue Tracker] Commented: (ENERGYINTEROP-348) Use of "Ack"as a string

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25989#action_25989 ] 

Gerald Gray commented on ENERGYINTEROP-348:
-------------------------------------------

I "think" that we have concensus that the various Ack strings can be removed from the message payloads as the returns (both normal and errors) along with message header information serve to address this need.  Once the Ack string are removed this issue may be closed.

> Use of "Ack" as a string
> ------------------------
>
>                 Key: ENERGYINTEROP-348
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-348
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Sub-task
>          Components: model, schema
>    Affects Versions: wd22
>         Environment: Gerald Gray
>            Reporter: Gerald Gray
>            Assignee: William Cox
>
> Throughout the model there are various uses of "ack" type attributes which have been set to the data type of string.  An ack type action is probably best reflected as a Boolean.
> However, the repeated uses of "ack" attributes throughout the model suggest this attribute may be abstracted out.  In addition if more information about an acknowledgement is needed there may be an opportunity to leverage the Status class from CIM.
> IEC61968.Common.Status (compounded class)
> This class contains dateTime, reason, remark, value that may be leveraged for this purpose.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira