Issue 11518: Add prefix to the topic names (amsm-ftf)
Source:  (, )
Nature: Enhancement
Severity: Significant
Summary: Add prefix to the topic names, because they are global and should be unique within the whole system. B.t.w.: For the type definitions the prefix is not necessary because the are in the namespace AMSM. Proposed solution: Add Prefix AMS or CIM to Topic names. Topic name = Data type name

Resolution: Add Prefix AMS to Topic names
Revised Text: In Section 11.1.1.2, replace the first bullet with:
The name of an "element topic" is the concatenation of "AMS_" and the name of the class of the corresponding AMSM object.
In Section 11.1.1.2, replace the names in the first column of the second table by (in the same order): AMS_CT_LoadConfiguration, AMS_CT_UnloadConfiguration, AMS_CT_ShutDownESE, AMS_CT_CreateHardwareGroup, AMS_CT_ShutDown, AMS_CT_StartUp, AMS_CT_StartUpOnHost, AMS_CT_StartUpOnSpec, AMS_CT_ActivateAsPrimary, AMS_CT_ForceShutDown, AMS_CT_Load, AMS_CT_Stop, AMS_CT_ClearLog, AMS_ControlResponse
In Section 11.1.1.5.5, replace the first line with: " "Control topics" have specific data types which names are the same as the topic names (cf. table in paragraph 11.1.1.2).", and remove the following table. In the reminder of the paragraph 11.1.1.5.5, replace "ControlResponse" with "AMS_ControlResponse").
In Section 11.1.1.5.5, replace the last code snippet with:
struct AMS_ErrorStruct {
	// message
	string Message;
	// errno
	long Number
	// error code
	AMS_ErrorCode Code;
	// full path to the element
	string Element
};

struct AMS_ControlResponse {
	// identifier of the request
	long request_id;
	// the ErrorStruct
	AMS_ErrorStruct Error;
}

#pragma keylist AMS_ControlResponse request_id

Actions taken:
September 26, 2007: received issue
July 18, 2008: closed issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 26 Sep 2007 07:53:49 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report



--------------------------------------------------------------------------------

Name: Willy Boenink
Company: Thales Nederland
mailFrom: willy.boenink@nl.thalesgroup.com
Notification: Yes
Specification: AMSM
Section: 11
FormalNumber: dtc/07-05-02
Version: 1
RevisionDate: 07-05-02
Page: 271 ..
Nature: Enhancement
Severity: Significant
HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Description
Add prefix to the topic names, because they are global and should be unique within the whole system. B.t.w.: For the type definitions the prefix is not necessary because the are in the namespace AMSM. Proposed solution: Add Prefix AMS or CIM to Topic names. Topic name = Data type name


Disposition: Resolved
OMG Issue No:  11518
Title:	Add prefix to the topic names
Source:
THALES
Summary:
Add prefix to the topic names, because they are global and should be unique within the whole system. 
Resolution:
Add Prefix AMS to Topic names.
Revised Text:
In Section 11.1.1.2, replace the first bullet with:
The name of an .element topic. is the concatenation of "AMS_" and the name of the class of the corresponding AMSM object.
In Section 11.1.1.2, replace the names in the first column of the second table by (in the same order): AMS_CT_LoadConfiguration, AMS_CT_UnloadConfiguration, AMS_CT_ShutDownESE, AMS_CT_CreateHardwareGroup, AMS_CT_ShutDown, AMS_CT_StartUp, AMS_CT_StartUpOnHost, AMS_CT_StartUpOnSpec, AMS_CT_ActivateAsPrimary, AMS_CT_ForceShutDown, AMS_CT_Load, AMS_CT_Stop, AMS_CT_ClearLog, AMS_ControlResponse
In Section 11.1.1.5.5, replace the first line with: " .Control topics. have specific data types which names are the same as the topic names (cf. table in paragraph 11.1.1.2).", and remove the following table. In the reminder of the paragraph 11.1.1.5.5, replace "ControlResponse" with "AMS_ControlResponse").
In Section 11.1.1.5.5, replace the last code snippet with:
struct AMS_ErrorStruct {
	// message
	string Message;
	// errno
	long Number
	// error code
	AMS_ErrorCode Code;
	// full path to the element
	string Element
};

struct AMS_ControlResponse {
	// identifier of the request
	long request_id;
	// the ErrorStruct
	AMS_ErrorStruct Error;
}

#pragma keylist AMS_ControlResponse request_id

Disposition:	Resolved