${taskforce.name} Avatar
  1. OMG Task Force

DAIS 1.1 RTF — Closed Issues

  • Key: DAIS11
  • Issues Count: 18
Open Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
DAIS11-16 Meaning of A&E Reason DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-15 Data type for VT_EMPTY DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-7 Bad parameters exception DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-6 DAIS::DataAccess::GroupEntry::Manager::create_entries() DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-14 The SimpleIO need an own error report struct DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-13 Change user quality from short to long DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-17 Improved A&E error reporting on enable/disable by area and source DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-10 find_by_type to take a node sequence DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-12 OPC_QUALITY_EGU_EXCEEDED twice in table DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-9 Missing exception InvalidFilter DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-11 ItemHome in description shall be just Home DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-8 Missing description of simple_io_home DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-18 A&E Keep alive supervision DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-19 Description of validate_entries DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-5 DAIS::DataAccess::Item::Home::get_ids() DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-2 datatype TypeID. But CORBA 3 was define keyword - typeid. DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-3 clash with keyword "home" in CORBA spec DAIS 1.0 DAIS 1.1 Resolved closed
DAIS11-4 DAIS::DataAccess::Item::ItemHome::find_each() DAIS 1.0 DAIS 1.1 Resolved closed

Issues Descriptions

Meaning of A&E Reason

  • Key: DAIS11-16
  • Legacy Issue Number: 7086
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The Alarms & Events Reason is claimed to describe the reason behind an event. Reason is mapped to OPC EventCategory. OPC EventCategory is more intended to describe the contents of an event rather than the reason causing the event. Investigate if this shall cause a name change of Reason to EventCategory. This will simplify mapping DAIS A&E to OPC A&E.

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Change as suggested in section Changes to formal/02-11-07

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Data type for VT_EMPTY

  • Key: DAIS11-15
  • Legacy Issue Number: 7084
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    A new datatype that corresponds to OPC VT_EMPTY is needed to indicate that the server shall use the native data type. SimpleValueType needs a UNSPECIFIED_TYPE

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Change as suggested

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Bad parameters exception

  • Key: DAIS11-7
  • Legacy Issue Number: 7076
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Bad parameters are signaled with the error code E_INVALIDARG. The corresponding OMG exception is BAD_PARAM. Remove InvalidStateSpecified in E&A Subscription and use BAD_PARAM instead

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Changed according to suggestion

  • Updated: Fri, 6 Mar 2015 20:58 GMT

DAIS::DataAccess::GroupEntry::Manager::create_entries()

  • Key: DAIS11-6
  • Legacy Issue Number: 6336
  • Status: closed  
  • Source: Technical University, Sofia, Bulgaria ( Lubomir Chorbadjiev)
  • Summary:

    When describing: DAIS::DataAccess::GroupEntry::Manager::create_entries() last paragraph on page 4-38 says:

    "both item and pathname specified ->..."

    I think that there is no way to specify both itemID and pathname in this method. Paramethers passed in this method are:

    DAIS::DataAccess::GroupEntry::Description

    where for item identification we use union, described on page 3-3,3-6:

    DAIS::ServerItemIdentification

    So, how we can specify both item ID and pathname?

  • Reported: DAIS 1.0 — Fri, 17 Oct 2003 04:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Update the text to reflect the IDL

  • Updated: Fri, 6 Mar 2015 20:58 GMT

The SimpleIO need an own error report struct

  • Key: DAIS11-14
  • Legacy Issue Number: 7083
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The SimpleIO need an own error report struct as it can't use the handles in the ItemError struct. Suggestion
    struct ItemError

    { Error err; ServerItemIdentification id; string reason; }

    ;

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Change as suggested

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Change user quality from short to long

  • Key: DAIS11-13
  • Legacy Issue Number: 7082
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    User quality is currently a unsigned short. This is insufficient and shall be increased to a long

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Refer to dtc/2004-10-05 section 3.1.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Improved A&E error reporting on enable/disable by area and source

  • Key: DAIS11-17
  • Legacy Issue Number: 7137
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The methods enable_conditions() and disable_conditions() at the
    Source::Home and Area::Home does not return error codes for Sources or
    Areas that fails.

  • Reported: DAIS 1.0 — Wed, 10 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Refer to dtc/2004-10-05 sections 5.2.5.2 and 5.2.6.2

  • Updated: Fri, 6 Mar 2015 20:58 GMT

find_by_type to take a node sequence

  • Key: DAIS11-10
  • Legacy Issue Number: 7079
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    find_by_type currently takes a single root node as input. By changing this to a sequence it is possible to use a set of nodes from a previous call as input to a subsequent call

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    see above, rejected

  • Updated: Fri, 6 Mar 2015 20:58 GMT

OPC_QUALITY_EGU_EXCEEDED twice in table

  • Key: DAIS11-12
  • Legacy Issue Number: 7081
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    OPC_QUALITY_EGU_EXCEEDED twice in table describing detailed quality flags for uncertain quality. Remove one entry.

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Change as suggested

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Missing exception InvalidFilter

  • Key: DAIS11-9
  • Legacy Issue Number: 7078
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Exception InvalidFilter is missing in find_by_parent() and find_by_type() in section 3.1.7.2.

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Add the exception

  • Updated: Fri, 6 Mar 2015 20:58 GMT

ItemHome in description shall be just Home

  • Key: DAIS11-11
  • Legacy Issue Number: 7080
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    In description of Item::Home the interface is called ItemHome, shall be just Home

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Change as suggested

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Missing description of simple_io_home

  • Key: DAIS11-8
  • Legacy Issue Number: 7077
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    Description of simple_io_home is missing in section 4.2.2.2

  • Reported: DAIS 1.0 — Tue, 2 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    rejected The description is not missing. This is not an issue.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

A&E Keep alive supervision

  • Key: DAIS11-18
  • Legacy Issue Number: 7138
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    When an A&E subscription has a non-zero keep-alive time, the server will
    insure that the client receives a callback on the subscription minimally at
    rate indicated by the keep-alive time, even when there are no new events to
    report. By providing callbacks at a minimum known frequency, the client can
    be assured of the health of the server and subscription without resorting
    to "pinging the server" (the common practice of making periodic calls to a
    server method, e.g. IOPCEventServer::GetStatus() ).

  • Reported: DAIS 1.0 — Wed, 10 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Add a new member keep_alive_time in the AlarmsAndEvents::Subscription::State struct

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Description of validate_entries

  • Key: DAIS11-19
  • Legacy Issue Number: 7085
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. Lars-Ola Osterlund)
  • Summary:

    The DAIS specification states that validate_entries (on DAISGroupEntry) is: "Used to check if Descriptions a client holds are still valid without effecting the existing group." The OPC specification of ValidateItems (on IOPCItemMgt) states: "Determines if an item is valid (could it be added without error). Also returns information about the item such as canonical datatype. Does not affect the group in any way."
    Update the specification to reflect the behavior according to the OPC specification

  • Reported: DAIS 1.0 — Sat, 20 Mar 2004 05:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Change as suggested

  • Updated: Fri, 6 Mar 2015 20:58 GMT

DAIS::DataAccess::Item::Home::get_ids()

  • Key: DAIS11-5
  • Legacy Issue Number: 6335
  • Status: closed  
  • Source: Technical University, Sofia, Bulgaria ( Lubomir Chorbadjiev)
  • Summary:

    When describing DAIS::DataAccess::Item::Home::get_ids() the specification says:

    "Translate a sequence of pathnames to the corresponding sequence of >>node<< identifications. If a pathname fails to translate to >>node<< identification..."

    I suppose that word >>node<< should be replaced with >>item<< because: 1) the IDL definition for this method is: ItemIDs get_ids(in Strings pathnames); 2) description of return values on page 4-22 says: "return The corresponding sequence of >>item<< identifications."

  • Reported: DAIS 1.0 — Fri, 17 Oct 2003 04:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Changed according to suggestion

  • Updated: Fri, 6 Mar 2015 20:58 GMT

datatype TypeID. But CORBA 3 was define keyword - typeid.

  • Key: DAIS11-2
  • Legacy Issue Number: 6064
  • Status: closed  
  • Source: RNPK ( Eugeny P. Florov)
  • Summary:

    In this idl-file is defined datatype TypeID. But CORBA 3 was define keyword - typeid.

    In result idl compiler write:

    tao_idl: "DAISCommon.idl", line 15: spelling differs from IDL keyword only in case: "TypeID" tao_idl: "DAISCommon.idl", line 20: spelling differs from IDL keyword only in case: "TypeID"

  • Reported: DAIS 1.0 — Sun, 24 Aug 2003 04:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    To avoid keyword collision in CORBA 3 the existing type ResourceID replaces TypeID

  • Updated: Fri, 6 Mar 2015 20:58 GMT

clash with keyword "home" in CORBA spec

  • Key: DAIS11-3
  • Legacy Issue Number: 6320
  • Status: closed  
  • Source: KU Leuven ( Panagiotis Issaris)
  • Summary:

    Regarding the specification "IDL for Data Acquisition from Industrial Systems": The IDL files define interfaces named Home, which clash with the keyword "home" of the CORBA 3 specification.

    The TAO IDL compiler reports: tao_idl: "DAISNode.idl", line 33: spelling differs from IDL keyword only in case: "Home"

  • Reported: DAIS 1.0 — Mon, 13 Oct 2003 04:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    "Home" interfaces are renamed to "IHome" the distinguish from the keyword Home

  • Updated: Fri, 6 Mar 2015 20:58 GMT

DAIS::DataAccess::Item::ItemHome::find_each()

  • Key: DAIS11-4
  • Legacy Issue Number: 6334
  • Status: closed  
  • Source: Technical University, Sofia, Bulgaria ( Lubomir Chorbadjiev)
  • Summary:

    When describing what DAIS::DataAccess::Item::ItemHome::find_each() returns, the specification says:

    "return: An >>iterator<< holding the item descriptions"

    I suppose that word >>iterator<< should be replaced with >>sequence<< since the IDL definition is:

    Descriptions find_each(in ItemIDs items) raises (UnknownItemID);

  • Reported: DAIS 1.0 — Fri, 17 Oct 2003 04:00 GMT
  • Disposition: Resolved — DAIS 1.1
  • Disposition Summary:

    Changed according to suggestion

  • Updated: Fri, 6 Mar 2015 20:58 GMT