Issue 11505: DCPS/f and DCPS/m profiles issue (amsm-ftf) Source: Naval Surface Warfare Center (Mr. Paul V. Werme, paul.werme(at)navy.mil) Nature: Revision Severity: Significant Summary: Clarification of the intent and approach is requested concerning 1) how the DCPS/f profile will access static configuration information and 2) how the DCPS/m profile when used with the CORBA/IDL and CIM PSMs will map the Subscription methods to DCPS/m topics, i.e., the CORBA/IDL PSM subscription methods currently pass in an object with an interface to receive CORBA one-way callbacks, which would not be needed or used if the DCPS/m profile is used. Resolution: Point (1): DCPS/f accesses static configuration information through the mandatory XML PSM Point (2): "they work in their usual way, independently of each other" Revised Text: Replace first bullet of paragraph 11.1.1 with: "The DCPS/f ('/f' stands for full) PSM which relates to the full DCPS PSM as described in this section. This PSM along with the XML PSM is intended to be equivalent to the CORBA/IDL and CIM profile, and thus compliant implementations are not required to deploy any elements of the CORBA and/or CIM profiles. The DCPS/f PSM shall access the static configuration information through the mandatory XML PSM." Replace the second bullet of paragraph 11.1.1 with: "The DCPS/m ('/m' stands for monitoring) PSM which is a subset of the DCPS/f PSM, and contains those elements which are required for asynchronous monitoring of states of the different (software and hardware) elements. The DCPS/m PSM is defined to allow other PSMs (CORBA and/or CIM) to import it and use it for asynchronous monitoring tasks. Note that the inclusion of DCPS/m profile in CORBA and/or CIM PSM is not a mandatory, but an optional (convenience) mechanism. Whenever the DCPS/m profile is implemented along with CORBA and/or CIM PSM, the CORBA and/or CIM profile work in their usual way, independently of the DCPS/m profile." Actions taken: September 21, 2007: received issue July 18, 2008: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 20 Sep 2007 21:13:01 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Paul V. Werme Company: NSWCDD mailFrom: paul.werme@navy.mil Notification: No Specification: AMSM Section: General FormalNumber: dtc/07-05-02 Version: Beta 1 RevisionDate: 07-05-02 Page: General Nature: Revision Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727) Description Clarification of the intent and approach is requested concerning 1) how the DCPS/f profile will access static configuration information and 2) how the DCPS/m profile when used with the CORBA/IDL and CIM PSMs will map the Subscription methods to DCPS/m topics, i.e., the CORBA/IDL PSM subscription methods currently pass in an object with an interface to receive CORBA one-way callbacks, which would not be needed or used if the DCPS/m profile is used.