Issue 5474: XML Schema COMMAND_ID                                                                                                                                                                                   (lecis-ftf)
Source: Creon-Labcontrol AG (Mr. Thorsten Richter, thorsten.richter@creonlabcontrol.com)
Nature: Uncategorized Issue
Severity: 
Summary: We cannot have the same COMMAND_ID within one SCD bause its of the type xsd:ID. That means,we cannot define multiple primary commands like "init" with the same ID for mutliple subunits.. We should change CommandID to type xsd:string ? 
Do we need the COMMAND_ID at all?


<xsd:complexType name="COMMAND_TYPE"> 
<xsd:sequence> 
<xsd:element name="COMMAND_ID" type="xsd:ID"/> 
<xsd:element name="NAME" type="xsd:string"/> 
<xsd:element name="ALIAS_NAME" type="xsd:string" minOccurs="0"/> 
<xsd:element name="DURATION" type="xsd:long"/> 
<xsd:element name="CATEGORY" type="ECOMMAND_CATEGORY"/> 
<xsd:element name="TYPE" type="ECOMMAND_TYPE"/> 
<xsd:element name="DESCRIPTION" type="xsd:string" minOccurs="0"/> 
<xsd:element name="FORMAL_ARGUMENTS" type="ARGUMENT_TYPE" minOccurs="0" maxOccurs="unbounded"/> 
<xsd:element name="EXCLUSION_LIST" type="ITEM_VALUE_TYPE" minOccurs="0" maxOccurs="unbounded"/> 
<xsd:element name="SYNC_RESPONSE_DATA" type="ARGUMENT_TYPE" minOccurs="0" maxOccurs="unbounded"/> 
<xsd:element name="PROPERTIES" type="ITEM_VALUE_TYPE" minOccurs="0" maxOccurs="unbounded"/> 
<xsd:element name="CONFIGURATION_COMMANDS" type="xsd:IDREF" minOccurs="0" maxOccurs="unbounded"/> 
<xsd:element name="REQUIRED_RESOURCES" type="xsd:IDREF" minOccurs="0" maxOccurs="unbounded"/> 
<xsd:element name="PRODUCED_RESCOURCES" type="xsd:IDREF" minOccurs="0" maxOccurs="unbounded"/> 
<xsd:element name="OUTPUT_PORTs" type="xsd:IDREF" minOccurs="0" maxOccurs="unbounded"/> 
<xsd:element name="INPUT_PORTs" type="xsd:IDREF" minOccurs="0" maxOccurs="unbounded"/> 
</xsd:sequence> 
</xsd:complexType>

Resolution: see discussion
Revised Text: On page 3-14 and 6-15 change
<xsd:complexType name="COMMAND_TYPE"> 

change 
<xsd:element name="COMMAND_ID" type="xsd:ID"/> 
to 
<xsd:element name="COMMAND_ID" type="xsd:string

Actions taken:
July 23, 2002: received issue
December 11, 2002: closed issue
Discussion: 
In <xsd:complexType name="COMMAND_TYPE"> 
change 
<xsd:element name="COMMAND_ID" type="xsd:ID"/> 
to 
<xsd:element name="COMMAND_ID" type="xsd:string

End of Annotations:=====
To: lecis-ftf@omg.org, lecis-post@yahoogroups.com 
Subject: LECIS FTF issue TR03:     XML Schema COMMAND_ID 
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000 
From: Thorsten.Richter@creonlabcontrol.com 
Date: Wed, 10 Jul 2002 09:22:08 +0200 
X-MIMETrack: Serialize by Router on domino1/creonlabcontrol/de(Release
5.0.8 |June 18, 2001) at 
 07/10/2002 10:55:44 AM, 
        Serialize complete at 07/10/2002 10:55:44 AM 


We cannot have the same COMMAND_ID within one SCD bause its of the
type xsd:ID. That means,we cannot define multiple primary commands
like "init" with the same ID for mutliple subunits.. We should change
CommandID to type xsd:string ? 
Do we need the COMMAND_ID at all?


<xsd:complexType name="COMMAND_TYPE"> 
<xsd:sequence> 
<xsd:element name="COMMAND_ID" type="xsd:ID"/> 
<xsd:element name="NAME" type="xsd:string"/> 
<xsd:element name="ALIAS_NAME" type="xsd:string" minOccurs="0"/> 
<xsd:element name="DURATION" type="xsd:long"/> 
<xsd:element name="CATEGORY" type="ECOMMAND_CATEGORY"/> 
<xsd:element name="TYPE" type="ECOMMAND_TYPE"/> 
<xsd:element name="DESCRIPTION" type="xsd:string" minOccurs="0"/> 
<xsd:element name="FORMAL_ARGUMENTS" type="ARGUMENT_TYPE"
minOccurs="0" maxOccurs="unbounded"/> 
<xsd:element name="EXCLUSION_LIST" type="ITEM_VALUE_TYPE"
minOccurs="0" maxOccurs="unbounded"/> 
<xsd:element name="SYNC_RESPONSE_DATA" type="ARGUMENT_TYPE"
minOccurs="0" maxOccurs="unbounded"/> 
<xsd:element name="PROPERTIES" type="ITEM_VALUE_TYPE" minOccurs="0"
maxOccurs="unbounded"/> 
<xsd:element name="CONFIGURATION_COMMANDS" type="xsd:IDREF"
minOccurs="0" maxOccurs="unbounded"/> 
<xsd:element name="REQUIRED_RESOURCES" type="xsd:IDREF" minOccurs="0"
maxOccurs="unbounded"/> 
<xsd:element name="PRODUCED_RESCOURCES" type="xsd:IDREF" minOccurs="0"
maxOccurs="unbounded"/> 
<xsd:element name="OUTPUT_PORTs" type="xsd:IDREF" minOccurs="0"
maxOccurs="unbounded"/> 
<xsd:element name="INPUT_PORTs" type="xsd:IDREF" minOccurs="0"
maxOccurs="unbounded"/> 
</xsd:sequence> 
</xsd:complexType>


Thorsten Richter
Project Manager
--------------------------------------------------------------
CREONLLLLLLLABCCCCCCCONTROL AG
Europaallee 27-29, D-50226 Frechen, Germany
Tel. +49 2234 9207-0 Fax. +49 2234 9207-99
http://www.creonlabcontrol.com
-------------------------------------------------------------- 


X-Sender: tstaab@popmail.esa.lanl.gov 
X-Mailer: QUALCOMM Windows Eudora Version 5.1 
Date: Tue, 06 Aug 2002 11:02:30 -0600 
To: lecis-ftf@omg.org 
From: Torsten Staab <tstaab@lanl.gov> 
Subject: LECIS FTF issue  # 5474 


In response to issue # 5474


Thorsten.Richter@creonlabcontrol.com wrote:
XML Schema COMMAND_ID
We cannot have the same COMMAND_ID within one SCD bause its of the
type xsd:ID. That means,we cannot define multiple primary commands
like "init" with the same ID for mutliple subunits.. We should change
CommandID to type xsd:string ? Do we need the COMMAND_ID at all?


I think that the command id is quite useful for debugging and logging
purposes.


Torsten



X-Sender: tstaab@popmail.esa.lanl.gov 
X-Mailer: QUALCOMM Windows Eudora Version 5.1 
Date: Fri, 09 Aug 2002 10:35:12 -0600 
To: lecis-ftf@omg.org 
From: Torsten Staab <tstaab@lanl.gov> 
Subject: LECIS FTF issue TR3 

In response to issue # TR3
"XML Schema COMMAND_ID"

Thorsten.Richter@creonlabcontrol.com wrote:
We cannot have the same COMMAND_ID within one SCD bause its of the
type xsd:ID. That means,we cannot define multiple primary commands
like "init" with the same ID for mutliple subunits.. We should change
CommandID to type xsd:string ? 
Do we need the COMMAND_ID at all?


I would keep COMMAND_ID and use string as a data type.

Torsten