Issue 5564: Compliance point issues                                                                                                                                                                                 (smart-transducers-ftf)
Source:  (, )
Nature: Revision
Severity: 
Summary: At the OMG Technical Meeting in Dublin the following things have been identified

by the AB as subject for revision:



1. Delete Sec. 3.3

2. List Sec. 3.1.1 and 3.2.1 as single mandatory compliance points.

3. Identify List of Functions in Secs. 3.1.2 and 3.2.2 as individual,

optional compliance points
Resolution: Accept changes as proposed.
Revised Text: 9/29/02 Page 6
Section 3.3 has been deleted.
The former sections "3.1 Mandatory versus Optional Requirements for Smart
Transducers (ST)" and "3.2 Mandatory versus Optional Interfaces at the CORBA
Gateway" and all subsections have been rearranged to "3.1 Mandatory
Requirements" and "3.2 Optional Requirements" (without the need for
subsections):
3.1 Mandatory Requirements
Every ST must support MS rounds in order that one can read the physical
name of an ST from the CORBA interface. This function is necessary to
learn about the existence of an ST in a cluster.
Every ST must support at least reading of the first, second, and third (0x00,
0x01, and 0x02) record of the documentation file 0x3D as described in
Section 2.4.6, “The Documentation File (file no. 0x3D),” on page 2-19 in
order to allow reading the physical name.
Smart Transducers FTF
Finalization Task Force Report
Disposition: Accepted
OMG Issue No: 5564
9/29/02 Page 7
Every master must provide the capability to translate the representation of
the internal time of its cluster to the representation of the external time.
Every CORBA gateway must provide the three interfaces: the RS interface,
the DM interface, and the CP interface.
3.2 Optional Requirements
In addition to the mandatory services an ST compliant to this specification
may support an arbitrary set of the following optional services:
• Fixed MP Round
A low-cost ST that is used in mass-market applications may contain only
one or more a-priori preprogrammed RODLs in its ROM memory. Other
low-cost nodes may not support any MP round.
• Programmable MP Round
This function makes it possible to change the RODL within an ST on-line.
• Baptizing of STs without an assigned Logical Name
This function enables the on-line assignment of a logical name to an ST
that has no a-priori assigned logical name (the logical name 0xFF denotes
an ST currently not integrated in the system).
• Identification of STs (Plug and Play)
This function enables the on-line identification of a new node that has been
detected to exist.
• Sleep and Wakeup Service
This function enables a cluster to enter the sleep mode and to wake-up the
cluster after a significant event has occurred.
• First Membership
This function provides membership information about STs that participate
in MP rounds.
• Second Membership
This function provides membership information about currently available
STs in a cluster.
• External Clock Synchronization at Master or CORBA Gateway
Smart Transducers FTF
Finalization Task Force Report
Disposition: Accepted
OMG Issue No: 5565
The master or the CORBA gateway may provide an external clock
synchronization interface in order to synchronize the actions of the master
with an external time reference (e.g., GPS).
Actions taken:
August 5, 2002: received issue
December 11, 2002: closed issue
Discussion: 

End of Annotations:=====
ISSUE #xx (author: AB)

TYPE: Minor Change



At the OMG Technical Meeting in Dublin the following things have been
identified

by the AB as subject for revision:



1. Delete Sec. 3.3

2. List Sec. 3.1.1 and 3.2.1 as single mandatory compliance points.

3. Identify List of Functions in Secs. 3.1.2 and 3.2.2 as individual,

optional compliance points



ACTION



Section 3.3 has been deleted.



The former sections "3.1 Mandatory versus Optional Requirements for
Smart 

Transducers (ST)" and "3.2 Mandatory versus Optional Interfaces at the
CORBA 

Gateway" and all subsections have been rearranged to "3.1 Mandatory
Requirements" 

and "3.2 Optional Requirements" (without the need for subsections).