Issues for Mailing list of the Smart Antenna Finalization Task Force

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

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

Issue 12342: consider addition or correction of attributes
Issue 12343: Section: 6.3
Issue 12344: Section: 6.3
Issue 12345: Section: 8.2.2
Issue 12346: Section: 8.2.4
Issue 12347: Section: 8.3.1
Issue 12348: Section: 8.3.2,8.3.8
Issue 12349: Section: 8.3.4
Issue 12350: Section: 9.1
Issue 12351: XMI for the profile itself is also needed
Issue 12352: XSD or DTD file needed for mapping of configuration portions of PIM to XML
Issue 12358: Section: 8.3.4

Issue 12342: consider addition or correction of attributes (smartantenna-ftf)

Reference (SmartAnt FTF Issues List): #7 Responses should specify examples in addition to the results. Choi: We have corrected the typo (CORBA->IDL @ page 11 of presentation material). Jerry: I think the examples are the submission, so I am not sure what additional information can be supplied. Or you specified in the submission where the requirement was satisified. Mark: may not be in scope of the revised submission Choi: We will skip this matter for the revised submission. We will come back to this problem when TC of OMG raises this matter more specifically. In fact, this matter will have to be treated again when we double check the requirements of RFP and consider addition or correction of attributes. 

Reference (SmartAnt FTF Issues List): #7 The acknowledgments section lists "Office of the Military of Defense". Is this correct? Mark: See also opening section (2nd page of document)

Reference (SmartAnt FTF Issues List): #16 The relationship between the Device interfaces and the Control interfaces does not seem to be fully specified in this document. For example the AlgorithmControl interface has a <<readwrite>> Algorithms attribute that is a set of SAAlgorithmDevice instances. It doesn't say anything about how the SAAlgorithmDevice instances get created and registered with the AlgorithmControl interface, or what it means to modify this. Is this relationship between Devices and Controls sufficiently specified by the Component Framework Specification? Could you point me to the appropriate section?

Reference (SmartAnt FTF Issues List): #17 The CalibrationTable and CalibrationAccuracy attributes of the Calibration interface are of type ComplexSequence. I see no description of what the individual elements of these sequences correspond to. Do they related to individual antenna elements, or maybe times or frequencies? Also, units haven't been specified for these.

Reference (SmartAnt FTF Issues List): #19 No units have been specified for the Timing and Threshold Synchronization interface attributes whose types are ULong and ULongLong.

Reference (SmartAnt FTF Issues List): #20 What do the ComplexType values returned by the getPreData() and getPostData() operations of the SAAlgorithmDevice interface contain? It seems an additional parameter may be needed to select which type of data is being requested. Or is this determined by the specific algorithm represented by the SAAlgorithmDevice instance?

Reference (SmartAnt FTF Issues List): #21 What do the individual elements of the Beamforming interface's BFWeights and the ChannelEstimation interface's ChannelImpulse ComplexSequence attributes correspond to? Are these antenna elements? If so, does the association of indices with the geometry of the antenna need to be specified somewhere?

Reference (SmartAnt FTF Issues List): #22 The Beamforming interface's NullBFDirection attribute and the DOAEstimation interface's DOA attribute are each a FloatSequence. Are these dimensions of some coordinate system? Does anything more need to be specified?

Reference (SmartAnt FTF Issues List): #24 What is meant by "Object references map to the name of CORBA objects" in mapping rule #13? Does this refer to names in a naming service or the names of the interface types?

Reference (SmartAnt FTF Issues List): #24 The Smart Antenna Profile.xml file included in sbc-08-02-02.zip appears to be the Smart Antenna PIM model, not the XMI of the UML Profile for Smart Antenna. The XMI for the profile itself is also needed.

Reference (SmartAnt FTF Issues List): #26 Is an XSD or DTD file needed for the mapping of the configuration portions of the PIM to XML? Or is this covered by existing specifications?

Reference (SmartAnt FTF Issues List): #23 How does the UShort field of the STCMapping represent a code pattern?