Issue 6057: BaseDataType/Any (xtce-ftf) Source: University of Maryland (Dr. Ed Shaya, eshaya@umd.edu) Nature: Revision Severity: Minor Summary: BaseDataType/Any should be reserved to describe any parameter that can be of any datatype. As it is, it is fixed to be a SourceParameterRef only Resolution: Revised Text: Actions taken: August 12, 2003: received issue August 2, 2005: closed issue Discussion: Resolution: Remove the BaseDataType/Any as it has no purpose that can't be resolved on other manners. Revised Text: BaseDataType/Any is removed End of Annotations:===== From: webmaster@omg.org Date: 12 Aug 2003 17:34:59 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Ed Shaya Company: Raytheon Corp. mailFrom: ed.shaya@gsfc.nasa.gov Notification: No Specification: XTCE Section: SpaceTF FormalNumber: space-03-01-01 Version: 1.2 RevisionDate: 03-03-01 Page: 80 Nature: Revision Severity: Minor HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529 Description BaseDataType/Any should be reserved to describe any parameter that can be of any datatype. As it is, it is fixed to be a SourceParameterRef only. From: "Kevin Rice" To: Cc: Subject: Schema question -- basedatatype ANY Date: Tue, 9 Sep 2003 14:12:47 -0400 X-Mailer: Microsoft Outlook Express 5.50.4133.2400 Sam the basedatatype has an ANY which is a sourceparameterref. It seems like the ANY is misnamed and should called something else, and the ANY should be a real ANY. Any thoughts on clearing this up? Here is the original issue from issue list: Issue 6057: BaseDataType/Any (xtce-ftf) Click here for this issue's archive. Source: University of Maryland (Dr. Ed Shaya, eshaya@umd.edu) Nature: Revision Severity: Minor Summary: BaseDataType/Any should be reserved to describe any parameter that can be of any datatype. As it is, it is fixed to be a SourceParameterRef only Resolution: Revised Text: Actions taken: August 12, 2003: received issue