Sent From: [log in to unmask]
All, OK... It looks like this is not going to go away! Let`s move this forward to SISO to establish a Product Development Group (PDG). According to the SISO P&P, we need to establish a Product Nomination (PN). Please send your ideas for incorporation into a PN to me. I`ll do my best to draft a PN that reflects the interests of the community. I`m still a bit concerned that this activity could delay wide-spread deployment of 1516. However, I suppose that a public discussion of the issues is a big step for the move to 1516. For the PN, I`ll also need a list of interested parties. So, even if you don`t have additional ideas - please send an indication of your interest. If we don`t get interest from both users and vendors we can`t start. Here are a couple of ideas to get things started. 1) Standardization of HLA 1.3 Header. 2) An alternative 1516 C++ Header. To help me manage my email - and ensure your comments don`t get dropped, please do not change the Subject in your reply. Steve Monson -----Original Message----- From: Drake, Steven R [mailto:[log in to unmask]] Sent: Monday, July 29, 2002 9:19 AM To: SISO - Run-Time Infrastructure and Communications Forum Subject: RE: HLA Header Files are not ``Set in Stone`` (Was: Creating and Destroying Federations) So we`ve defined a need for two complimentary activities; maintenance of the 1516 standard and maintenance of the the 1.3 standard. Perhaps one organization can do both? How do we, as a ``community``, get this ball rolling? Given the discussion that we`ve had, it seems obvious that the 1.3 standard needs work now. -----Original Message----- From: Katherine Morse [mailto:[log in to unmask]] Sent: Sunday, July 28, 2002 4:17 PM To: SISO - Run-Time Infrastructure and Communications Forum Subject: Re: HLA Header Files are not ``Set in Stone`` (Was: Creating and Destroying Federations) SISC (not SISO) is the sponsoring committee for IEEE 1516. As with all IEEE standards, the IEEE itself only manages the standards process. Interested members of the appropriate technical community (that`s us) are recognized as having the vested interest and technical expertise to develop and maintain standards in the community`s best interest. It is up to us to maintain the standard(s) and to move forward with any desired revisions within the next three years; it`s been almost two years since we ratified it. If the SISO/IEEE MOU goes through, SISO will take over responsibility from SISC. KLM (SISC Vice-Chair) ----------------------------------- Katherine L. Morse, Ph.D. Chief Scientist, ASDI SAIC 10260 Campus Point Drive, MS C3, San Diego, CA 92121 (858)826-6728; (858)826-6223 (fax); (858)775-8651 (cell) From: ``Beeker, Emmet`` <[log in to unmask]> Reply-To: [log in to unmask] Date: Fri, 26 Jul 2002 07:42:03 -0400 To: SISO - Run-Time Infrastructure and Communications Forum <[log in to unmask]> Subject: RE: HLA Header Files are not ``Set in Stone`` (Was: Creating and Destroying Federations) I would not dismiss 1516 to IEEE so quickly. Who at IEEE controls 1516? I realize that we (SISC) submitted the 1516 standard to IEEE where it was balloted and approved. What I am asking is who at IEEE cares or would hold meetings to discuss revisions to the standard. I do not believe this discussion will take place through IEEE, but rather through SISO. The easiest time to modify the standard is at the 5 year renewal point. Similar to DIS, I do not believe there will be any movement in IEEE to work on the standard. Therefore, if there are changes that need to be made, they will have to be worked as they always have - by those that care about the results (us). If I am wrong, I am willing to be corrected by my betters. Emmet Beeker AT&T 1900 Gallows Road, Vienna, VA 22182 703-506-4894 [log in to unmask] -----Original Message----- From: Drake, Steven R [mailto:[log in to unmask]] Sent: Thursday, July 25, 2002 10:50 PM To: SISO - Run-Time Infrastructure and Communications Forum Subject: RE: HLA Header Files are not ``Set in Stone`` (Was: Creating and Destroying Federations) [Beeker, Emmet]
Another approach is to have a standards committee that maintains and versions the header files. [Steven R. Drake] I think this is what we need! Steve Monson`s suggestion that SISO assume this role for the 1.3 specification seems like the logical outcome of this discussion. The IEEE will continue to control the 1516 spec.
To unsubscribe from the Z-ARCHIVE-SIW-CFI list, click the following link: