Base Object Model v0.12 Adjudication

1. Base Object Modelv0.12 Adjudication Jan 12 – 13, 2006 Orlando, FL

2. Statistics • Spec • 18 commenters • 141 comments • 29 Basic Editorial comments (#1) • 58 Significant Editorial comments (#1.5) • 50 Minor Content/Technical comments (#2) • 1 Major Content/Technical comment (#3) • 3 General comments (#4) • Guide • 14 commenters • 137 comments • 66 Basic Editorial comments (#1) • 38 Significant Editorial comments (#1.5) • 24 Minor Content/Technical comments (#2) • 1 Major Content/Technical comment (#3) • 8 General comments (#4) • Total • 278 comments 109 63

3. Game Plan (Overview) • Move to approve all Basic Editorial (#1) Comments in Spec & Guide • 29 Spec • 66 Guide • Move to resolve all Major Technical (#3) comments • 1 Spec • 1 Guide • Analyze / Move to table all appropriate General (#4) Comments for future discussion (via telecon, reflector, or upon future opening of docs) • 3 Spec • 8 Guide • Focus on critical sections of Spec • 109 Comments (total) • Focus on common areas shared between Spec / Guidance • 48 Comments (total) • Focus on critical sections of Guide • 117 Comments (total)

4. Game Plan (Today) • Examine/Approve Basic Editorial (as a Package) • Examine/Approve Major Technical (#3s) • Examine/Reassign/Table General (#4s) • Examine/Approve Critical Sections of “Spec” (#1.5s and #2s) • Section 5 – Conventions • Section 6 – BOM Template Components • Section 7 – BOM DIF Schema • Annex A – BOM Schema • Annex B – BOM Example • Annex C – XMLSpy™ Graphical Notation • General Issues • Examine/Approve Common Areas Shared between Spec / Guidance • Front Matter • Section 1 – Introduction • Section 2 - References • Section 3 – Definitions • Section 4 – Acronyms and Abbreviations

5. Game Plan (Tomorrow) • Finish with Common Areas (if necessary) • Examine/Approve Critical Sections of “Guide” • Section 5 – BOM Rationale • Section 6 – BOM Concept • Section 7 – FEDEP • Section 8 – Individual BOM Development • Section 9 – BOM Assembly Development • Section 10 – Related Resources • Section 11 – BOM Development and Distribution • General Issues

6. Recommended Editor Resolutions (from BPDP)

7. Final (Adjudication) Resolutions(from BPDP)

8. Basic Editorial Package(#1s) 29 Spec66 Guide (see cells highlighted in aqua blue)

9. Spec (#1s)

12. Guide (#1s)

18. Major Technical Comments (#3s) 1 Spec 1 Guide

20. General Comments (#4’s) 3 Spec 8 Guide Objective: Verify that these should be 4’s, if not, change them to 2’s.

21. Recommend: Change to 2Agreed by commenter to change to 2

22. Recommend: Leave 4, and resolve Via 431

23. Recommend: Leave 4“W”

24. Recommend: Leave 4“D1” -

25. Recommend: Leave 4 “D3”

26. Recommend: Change 2 “A1” – See Reference 9.6“not appropriate for mass destruction”

27. Recommend: Leave 4 “D1”

28. Recommend: Leave 4“D1”

29. Recommend: Leave 4“D1”

30. Recommend: Leave 4 “D1”

31. Recommend: Leave 4 “D1”

32. Critical Sections of “Spec” • Section 5 – Conventions • Section 6 – BOM Template Components • Section 7 – BOM DIF Schema • Annex A – BOM Schema • Annex B – BOM Example • Annex C – XMLSpy™ Graphical Notation • General Issues

33. Section 5 - Spec Conventions 6 Comments

34. “D2”

35. “A1” Look into HLA OMT To see if change is Also needed as approved

37. “A1”See also comment 511 (for def) and 545

38. “A1”remove line 335

39. “A1”

40. Section 6 - Spec BOM Template Components 92 Comments

41. “A1”

42. “D2”

43. “W”

44. “A2” – Pattern of Interplay in both Spec and Guide

45. “D2” – see line 374to see def of presentation

46. “A1”

47. “A3”“Specific rules for using these tablescan be found in the section 8.4 ofGuide document.” (goes in 6.4) Include default value table in Guide as outlined on the whiteboard

50. “A2”