Issue 2217: Not all references to event types have been updated (notif_service-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: Not all references to event types have been updated to refer to the correct IDL type names: struct EventType { string domain_name; string type_name; }; Resolution: fix see below Revised Text: I used "Find" to find all errant occurances of "domain_type" and "event_type". I made appropriate changes in following places: Table 2-2, Figure 2-2, 2nd paragraph after Fig 2-2, filtering example in section 2.3, 2nd to last paragraph in section 2.8, section 3.1.1.1. Actions taken: November 17, 1998: received issue November 16, 1999: closed issue Discussion: Synopsis: An older, pre-adoption revision of the spec defined the fixed header of a structured event to contain string type members named "domain_type" and "event_type". Prior to adoption of the spec, this was changed to be the following data structure struct EventType { string domain_name; string type_name; }; The submitter of this issue pointed out several places in the spec where the legacy fixed header member names "domain_type" and "event_type" are still used, and recommends they be changed to make them consistent with the actual member names. Disposition: I agree with the issue and the proposed resolution VOTE: YES means to make the recommended changes; NO means to do nothing End of Annotations:===== Return-Path: To: issues@omg.org Cc: notif_service-rtf@omg.org Subject: Notification Service Issue X-face: *A\_v+D,~Jx_g]`m,s61-x|*;H4hgZeE= Issue: Not all references to event types have been updated to refer to the correct IDL type names: struct EventType { string domain_name; string type_name; }; In particular, outdated or incorrect references occur in the following sections: 2.2 makes serveral references to "domain_type" instead of "domain_name", including the Diagram of a Structured Event. 2.3 also refers to "domain_type" 2.6.5 "Special Event Types" refers to event type and domain rather than explicitly to EventType.domain_name and EventType.type_name. One explict reference here would clarify things. 2.8 refers to domain_type rather than domain_name 3.1.1.1 contains a sub-section "domain_type" which is inconsistent with the IDL "domain_name". contains a sub-section "event_type" which is inconsistent with the IDL "type_name". Many sections: "event type names" is used to mean the struct "EventType". In most cases this will not lead to great confusion, but substituting the term "event type" for "event type name" would be a good idea in most cases. (Notably these occur in the descriptions of the obtain_*_types operations.) A.1 "Event Type Meta-Model" also refers to "names of event types"... K -- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Keith Duddy : dud at dstc.edu.au : http://www.dstc.edu.au/AU/staff/dud CRC for Distributed Systems Technology (DSTC) General Purpose South, University of Queensland, 4072, Australia ph: +61 7 336 5 4310 :: fx: +61 7 336 5 4311 ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2nd edition of my book ``Java Programming with CORBA'' now in bookshops >>> http://www.wiley.com/compbooks/vogel <<< :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::