Issue 5597: A master is also an ST (smart-transducers-ftf) Source: Institut fuer Technische Informatik (Mr. Thomas Losert, thomas@vmars.tuwien.ac.at) Nature: Uncategorized Issue Severity: Summary: A master is also an ST. Thus in the first paragraph of Section 2.2.1 "The master of each cluster is connected to the CORBA gateway through a real-time communication network, which provides a synchronized time to each master. [...] Since the STs are controlled by the master, we call them also slave nodes." should be replaced by "The master (an ST with extended features) of each cluster is connected to the CORBA gateway through a real-time communication network, which provides a synchronized time to each master. [...] Since the other STs are controlled by the master, we call them slave nodes also." Resolution: Accept changes as proposed. Revised Text: done as proposed Actions taken: August 27, 2002: received issue December 11, 2002: closed issue Discussion: End of Annotations:===== OMG Issue No: XXXX Title: A master is also an ST (smart-transducers-ftf) Source: TTTech Computertechnik AG (Mr. Thomas Losert, thomas@vmars.tuwien.ac.at) Summary: A master is also an ST. Thus in the first paragraph of Section 2.2.1 "The master of each cluster is connected to the CORBA gateway through a real-time communication network, which provides a synchronized time to each master. [...] Since the STs are controlled by the master, we call them also slave nodes." should be replaced by "The master (an ST with extended features) of each cluster is connected to the CORBA gateway through a real-time communication network, which provides a synchronized time to each master. [...] Since the other STs are controlled by the master, we call them slave nodes also." Resolution: See above. Revised Text: Done as proposed. Disposition: Accepted Subject: RE: Ballot 24 contents Date: Sun, 22 Aug 2004 18:14:34 -0400 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Ballot 24 contents Thread-Index: AcSG/RR08heWHceBT0e21r23XxLi6ABkqPhA From: "Pete Rivett" To: "Branislav Selic" , , X-Virus-Scanned: by amavisd-new at sentraliant.com Though 5597 is withdrawn I think we need to get in a fix to the problem I spotted when reviewing it: isUnique=true is the default for MultiplicityElement so we have a problem in that AFAIK (looking at resolution to 7575 in this set of issues) there is no notation to specify non-default multiplicity: the of {unique} is pointless since that's the default anyway! This is not a problem in the FAS which does have {nonunique} - not sure when we dropped this. Pete Rivett (mailto:pete.rivett@adaptive.com) Chief Scientist, Adaptive Inc. Dean Park House, 8-10 Dean Park Crescent, Bournemouth, BH1 1HL, UK Tel: +44 (0)1202 449419 Fax: +44 (0)1202 449448 http://www.adaptive.com -------------------------------------------------------------------------------- From: Branislav Selic [mailto:bselic@ca.ibm.com] Sent: Friday, August 20, 2004 5:21 PM To: uml2-superstructure-ftf@omg.org; mu2i-ftf@omg.org; uml2di-ftf@omg.org Subject: Ballot 24 contents The following changes were made since the draft ballot was issued: The following resolutions that appeared in the draft ballot have been withdrawn 3898 - due to Pete's concerns 5977 - due to Pete's concerns 6395 - due to Eran's concerns 6616 - due to Conrad's concerns 6630 - due to Pete's concerns 6975 - due to Conrad's concerns 7392 - due to possibility of synchronizing with Thomas' XXXX fix 7400 - due to Pete's concerns 7431 - due to Thomas' concerns 7434 - due to Thomas' concerns 7438 - due to Conrad's concerns 7441 - due to AlanMoore's concerns I have also left out the following resolutions that were proposed for this ballot: Anders' and Joaquin's joint resolution for defining Events - this is because it is a large resolution that needs a bit more soak time. However, because this is a ready resolution, I will make an exception of this case and will put it on the final "clean-up" ballot (ballot 26) Thomas XXXX resolution on new kinds of events - the same reason as above: it is a large change that needs more soak time and because its potential impact on issue 7392 needs to be investigated a bit more. However, since most of the resolution is available, I intend to include it on ballot 26 as well. The resolutions to issues 7344 (from IBM) and 6373 (from Thomas) dealing with the annoying issue of Operations and Parameters. These two proposals are both complete, but provide slightly different but very similar resolutions and it is likely that they can be consolidated. Again, the intent is to include it on ballot 26. Please note that, unless there are dangerous fires to be put out, we will not allow any other resolution proposals on ballot 26 -- except the ones that are deemed "clean-up" editorial items. For the moment these are issues: 6876, 6877, 6958, 7157, 7367, and 7401. I'll issue the ballot shortly. Cheers, Bran Disposition Parameter: None