Sent From: [log in to unmask]


Let me add that FOM development may be partially dependent upon the RTI capability (Just as Randy stated, " you [might] design your FOM to exploit the implementation details of your RTI") . You'll have to know what RTI you're developing/modifying your FOM to (since they may not all be compatable), If this occurs, then we're introducing the necessity of "lifecycle engineering" of FOMs. Woe! Not a pleasant thought, especially if we're having to maintain and update Reference FOMs for every new "baseline" RTI that comes out. I can hear it now, "Which RTI baseline version does your RPR FOM support?" Multiplicity without equalness! Now, that could be bad! - Paul >Let us not also forget that interoperability can't happen without FOM compliance. Thus... >HLA compliance = RTI compliance + FOM compliance



To unsubscribe from the Z-ARCHIVE-SIW-CFI list, click the following link:
https://discussions.sisostds.org/index.htm?SUBED1=Z-ARCHIVE-SIW-CFI