Issues for HDAIS Finalization Task Force

To comment on any of these issues, send email to hdais-ftf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 5947: HDAISItemAttribute.idl
Issue 6414: Difficult to understand conformance
Issue 6415: No interface to access conformance
Issue 6416: Usage of namespaces
Issue 6417: The uniqueness of CancelID is unclear
Issue 6418: Exceptions not consistent
Issue 6419: Commented source lines
Issue 6420: Wording in discussion on OPC bridge
Issue 6421: Question PropertyID in SimpleValue
Issue 7088: OPC HDA AGGREGATE 0x0e to 0x13 are missing
Issue 7089: Reserv AggregateIDs 0 to 0x7FFFFFFF
Issue 7090: TimeSerie is not a correct English name
Issue 7091: WARNING_MORE_EXTREEM_VALUES wrongly spelled
Issue 7092: find_by_parent() and find_by_type shall use AttributeFilters
Issue 7093: The ConnectionPoint callback is missing in HDAIS
Issue 7094: The AttributeFilter contains a member "operator
Issue 7095: New OPC quality code OPCHDA_PARTIAL
Issue 7096: SimpleValue members are named differently
Issue 7097: The cancel method is lacking on some async interfaces

Issue 5947: HDAISItemAttribute.idl (hdais-ftf)

Click here for this issue's archive.
Nature: Uncategorized Issue
Severity:
Summary:

The File HDAISItemAttribute.idl that I retrieved from
http://www.omg.org/cgi-bin/doc?mantis/02-10-04
contains several errors:


The parameter name is missing on line 66 and 70,
and the type AbsoluteIntervals (lines 41 and 51)
does not exist.


I assume that TimeInterval is the correct type.

Resolution: rejected
Revised Text:
Actions taken:
June 5, 2003: received issue
March 10, 2005: closed issue

Discussion:

The file with this error could not be found. It was probably an old file that has been removed

Issue 6414: Difficult to understand conformance (hdais-ftf)

Click here for this issue's archive.
Source: ABB Power Technologies, Power Automation & Substat (Mr. Lars-Ola Osterlund, lars-ola.g.osterlund(at)se.abb.com)
Nature: Clarification
Severity: Minor
Summary:

It is difficult to understand the conformance table in section 1.6.
Discussion:
Give the conformance points clear names so that they can be easily identified. Add a list with the named conformance points after the table in section 1.6.

Resolution:
Revised Text: Refer to dtc/2004-10-06 section Conformance to HDAIS
Actions taken:
November 4, 2003: received issue
March 10, 2005: closed issue

Discussion:

Add conformance for DAIS server functions DA and A&E as well as for HDAIS server.
Add HDAIS function conformance

Issue 6415: No interface to access conformance (hdais-ftf)

There is no interface a client can use to get the level of conformance actually supported by a server.
Discussion:
Standardize the conformance levels and make them available through an interface at Server. Also do this for DAIS DA and A&E.

Resolution: Add one constant for server functions DA, A&E and HDA as well as all the HDA functions
Revised Text: Refer to dtc/2004-10-06 section 5.2. and Changes to formal/02-11-07 section 3.1.5. DAIS: Refer to dtc/2004-10-05 section 3.1.5.
Actions taken:
November 4, 2003: received issue
March 10, 2005: closed issue

Issue 6416: Usage of namespaces (hdais-ftf)

HDAIS adds to the DAIS module. This opens for a potential name clashes.
Discussion:
Investigate if to keep the current module structure or inclusion by redefinition. Make HDAIS functionality including DAIS. Move the HDA server up to the DAIS namespace.

Resolution: see above
Revised Text: Refer to dtc/2004-10-06 section 5.3.1.2
Actions taken:
November 4, 2003: received issue
March 10, 2005: closed issue

Discussion:

The Server object is moved up to the DAIS module and is called HDAServer. The Session object is till in the HDA module as this corresponds to the way the DAIS sessions for DA and A&E are packaged.

Issue 6417: The uniqueness of CancelID is unclear (hdais-ftf)

It is unclear if the CancelIDs need to be globally unique.
Discussion:
The CancelIDs are server assigned and must be globally unique. Make this clear in the text. Figure 5 does not show the session-callback object cardinality clearly. Fix this.

Resolution: Change made as suggested
Revised Text: Refer to dtc/2004-10-06 sections 5.1 and 5.2
Actions taken:
November 4, 2003: received issue
March 10, 2005: closed issue

Issue 6418: Exceptions not consistent (hdais-ftf)

The find_each call does not allow reporting on individual UnkonwItemIDs. The find_by calls does not support exceptions for all parameters, e.g. UnkownTypeIDs.
Discussion:
Update the exceptions to be consistent.

Resolution: Change as suggested
Revised Text: Refer to dtc/2004-10-06 section 5.5.4.2
Actions taken:
November 4, 2003: received issue
March 10, 2005: closed issue

Issue 6419: Commented source lines (hdais-ftf)

Why are some source lines commented out and not removed?
Discussion:
Remove commented source lines.

Resolution: The commented lines are kept and the comment slashes removed
Revised Text: Refer to dtc/2004-10-06 sections 5.5.5.2, 5.5.6.2 and 5.6.1.2
Actions taken:
November 4, 2003: received issue
March 10, 2005: closed issue

Issue 6420: Wording in discussion on OPC bridge (hdais-ftf)

The text discussing bridging to OPC gives the impression this is difficult.
Discussion:
Make the wording sound more positive.

Resolution: Change the text
Revised Text: Refer to dtc/2004-10-06 section 1.4.1
Actions taken:
November 4, 2003: received issue
March 10, 2005: closed issue

Issue 6421: Question PropertyID in SimpleValue (hdais-ftf)

Source: ABB Power Technologies, Power Automation & Substat (Mr. Lars-Ola Osterlund, lars-ola.g.osterlund(at)se.abb.com)
Nature: Clarification
Severity: Minor
Summary:

Is it necessary to add the PropertyID to SimpleValue?
Discussion:
If this can be avoided there is no need to change the DAF spec.

Resolution: No, SimpleValue will not be extended with PropertyID.
Revised Text: Refer to dtc/2004-10-06 section 4.3
Actions taken:
November 4, 2003: received issue
March 10, 2005: closed issue

Issue 7088: OPC HDA AGGREGATE 0x0e to 0x13 are missing (hdais-ftf)

Click here for this issue's archive.
Nature: Revision
Severity: Significant
Summary:

The OPC HDA AGGREGATE defined for numbers 0x0e to 0x13 are missing for AggregateID. This complicates bridges. Change the AggregateID numbering to include the OPC HDA AGGREGATE numbers 0x0e to 0x13

Resolution: The numbers was erroneously defined and shall be corrected
Revised Text: Refer to dtc/2004-10-06 section 5.5.6.2
Actions taken:
March 2, 2004: received issue
March 10, 2005: closed issue

Issue 7089: Reserv AggregateIDs 0 to 0x7FFFFFFF (hdais-ftf)

The OPC HDA AGGREGATE defined for numbers 0 to 0x7FFFFFFF are reserved by OPC foundation. They shall be reserved for HDAIS as well. Add text making this reservation.

Resolution: Change as described
Revised Text: Refer to dtc/2004-10-06 section 5.5.6.2
Actions taken:
March 2, 2004: received issue
March 10, 2005: closed issue

Issue 7090: TimeSerie is not a correct English name (hdais-ftf)

The singular and plural forms are the same for time series, i.e. there is no English word time serie. Replace the word TimeSerie with TimeSequence or TimeSeriesItem.

Resolution: rejected
Revised Text:
Actions taken:
March 2, 2004: received issue
March 10, 2005: closed issue

Discussion:

The standard way the describe a sequence is to add an "s" on the identifier. When the type TimeSerie is made a sequence it becomes TimeSeries. This standard is kept for TimeSerie as the standard in this case is more important than correct English.

Issue 7091: WARNING_MORE_EXTREEM_VALUES wrongly spelled (hdais-ftf)

WARNING_MORE_EXTREEM_VALUES wrongly spelled, should be WARNING_MORE_EXTREME_VALUES.

Resolution: Change all WARNING_MORE_EXTREEM_VALUES to WARNING_MORE_EXTREME_VALUES
Revised Text: Refer to dtc/2004-10-06 section 5.5.6.2 for the IDL change. The text shall also be changed. These changes are not shown in section Changes to dtc/03-02-01 below.
Actions taken:
March 2, 2004: received issue
March 10, 2005: closed issue

Issue 7092: find_by_parent() and find_by_type shall use AttributeFilters (hdais-ftf)

find_by_parent() and find_by_typ shall take multiple filter spec rather than a single, i.e. use AttributeFilters instead of AttributeFilter.

Resolution: Change as described
Revised Text: Refer to dtc/2004-10-06 section 5.5.4.2
Actions taken:
March 2, 2004: received issue
March 10, 2005: closed issue

Issue 7093: The ConnectionPoint callback is missing in HDAIS (hdais-ftf)

In DAIS there is an attribute holding the callback object. The same solution shall be used in HDAIS.

Resolution: Add callback.
Revised Text: Refer to dtc/2004-10-06 section 5.4.2
Actions taken:
March 2, 2004: received issue
March 10, 2005: closed issue

Issue 7094: The AttributeFilter contains a member "operator (hdais-ftf)

The AttributeFilter "operator" clash with the C++ keyword operator. Change to "opc_operator".

Resolution: Change as suggested
Revised Text: Refer to dtc/2004-10-06 section 5.5.4.2
Actions taken:
March 2, 2004: received issue
March 10, 2005: closed issue

Issue 7095: New OPC quality code OPCHDA_PARTIAL (hdais-ftf)

OPC has added a new quality code bit OPCHDA_PARTIAL in HDA 1.20. Add also to HDAIS

Resolution: Add the code
Revised Text: Refer to dtc/2004-10-06 section 5.2
Actions taken:
March 2, 2004: received issue
March 10, 2005: closed issue

Issue 7096: SimpleValue members are named differently (hdais-ftf)

SimpleValue members in different structs are named differently, e.g. val, simple_value, the_value. Use a consistent naming, e.g. simple_value.

Resolution: Change as described
Revised Text: Refer to dtc/2004-10-06 section 5.2
Actions taken:
March 2, 2004: received issue
March 10, 2005: closed issue

Issue 7097: The cancel method is lacking on some async interfaces (hdais-ftf)

The cancel method is lacking on the async Playback and AsyncUpdate interfaces. Either add the methods or move it to the Session object

Resolution: Have one cancel method on the Connection (Session) object used for all cancelations
Revised Text: Refer to dtc/2004-10-06 sections 5.4.2, 5.6.1.5, 5.6.2.2, 5.6.3.2 and 5.6.4.2
Actions taken:
March 2, 2004: received issue
March 10, 2005: closed issue