1. Enumerations Working Group (EWG) THURSDAY 11 APRIL 2013 0800-1200 Pacific Daylight Time SHELL ROOM SISO-REF-010 Enumerations for Simulation Interoperability Lance Marrou, EWG Lead lance.r.marrou@saic.com

2. TOPICS OF DISCUSSION Review Draft TOC – SISO-REF-010-00v20-0 Operations Manual (OPMAN) CRs ‒ SISO-REF-010-00v20-0 ‒ SISO-REF-010-00v21-0 TODO ‒ Any takers on unassigned action items? ‒ Any volunteers to support life forms effort? ‒ Any volunteers to support supplies effort? 11 April 20132013 Spring SIW2

3. Draft TOC SISO-REF-010-00v20-0 Cover Page Revision History Table of Contents 1.0 Introduction ‒ 1.1 Purpose ‒ 1.2 Scope ‒ 1.3 Objectives ‒ 1.4 Intended Audience (optional) ‒ 1.5 Acknowledgments (optional) 2.0 References 3.0 Definitions 4.0 Acronyms and Abbreviations 5.0+ (BODY) Annex ADistributed Interactive Simulation Specific Fields (normative) 11 April 20132013 Spring SIW3

4. TOC Body Sections 5.Entity Type… 6.Object Type 1.Domain 2.Object State Kind 3.Point Object State Types 4.Linear Object State Types 5.Areal Object State Types 7.Emitters 1.Electromagnetic Emitters 2.Acoustic Emitters 3.Other Active Sensors 4.Passive Sensors 8.Radio Communications 1.Transmitter and Receiver 2.Signal 3.Intercom 9.Emissions 10.Identification Friend or Foe 11.Designator 12.Underwater Acoustics 13.Gridded Data 5. Environmental Process 1. Model Type 2. Environment Status 3. Environment Record Type 4. Geometry Records 5. State Records 15. Minefields 16. Entity/Object Attributes and Interactions… 17. Warfare Attributes and Interactions 1. Force ID 2. Detonation Result 3. Munition Descriptor 4. Explosion Descriptor 5. Directed Energy 18. Variable Record Types 19. Entity Management 1. Aggregates 2. IsPartOf 3. IsGroupOf 4. Transfer Ownership 20. Logistics 21. SIMAN 22. Information Operations (IO) 11 April 20132013 Spring SIW4

5. Entity Type Entity Kind Platform Kind ‒ Domain ‒ Country ‒ Category  Land Domain Categories  Air Domain Categories  Surface Domain Categories  Subsurface Domain Categories  Space Domain Categories ‒ Civilian Land Subcategories ‒ Civilian Air Subcategories ‒ Civilian Surface Subcategories Munition Kind Life Form Kind Environmental Kind Cultural Feature Kind Supply Kind Radio Kind ‒ Domain ‒ Country ‒ Category ‒ Subcategory ‒ Specific Expendable Kind ‒ Domain ‒ Country ‒ Category  Air Domain Categories  Surface Domain Categories  Subsurface Domain Categories Sensor/Emitter Kind Domain ‒ Munition Kind ‒ Other Kinds Country Comprehensive Entity Types 11 April 20132013 Spring SIW5

6. Entity/Object Attributes and Interactions Dead Reckoning ‒ Dead Reckoning Algorithm ‒ Dead Reckoning Parameters Type Collision Type Entity Marking Entity Capabilities Attached Parts Articulated Parts ‒ Type Metric ‒ Type Class Object Modification Entity Association Separation Entity Type Change Indicator Appearance ‒ Entity Appearance  Platform Appearance  Munition Appearance  Life Form Appearance  Environmental Appearance  Cultural Feature Appearance  Supply Appearance  Radio Appearance  Expendable Appearance  Sensor/Emitter Appearance ‒ Object Appearance  General  Point Object State  Linear Object State  Areal Object State  General Object Enumerations ‒ General Appearance Enumerations 11 April 20132013 Spring SIW6

7. Annex ADIS Specific Fields Protocol Version [UID 3] PDU Type [UID 4] Protocol Family [UID 5] PDU Status [UID 301-308,389] Attribute Action Code [UID 295] Live Entity Subprotocol Number [UID 417] 11 April 20132013 Spring SIW7

8. OPMAN ISSUES 11 April 20132013 Spring SIW8 IDBrief Description 1Match latest SISO-ADM-005 style guide 2Update copyright: "machine-readable." 3Update the Automated Toolset section 4Revise Updater to not suggest an enumeration during an add 5Revise Updater to not set the draft/approved copyright 6Revise Word Generator to not set the SISO copyright on the first page 7Revise Word Generator standard mode to be in alignment with SISO numbering 8Revise Word Generator final mode to be in alignment with SISO numbering 9Separate all paragraphs and headings by a blank line 10Disallow only NATO Reporting Names 11Retain the descriptions and rules for CR form fields (including adding rules) 12Re-evaluate rules for the use of blank and zero fields for Entity Type enumerations 13Deprecate the use of "Deprecated" 14Revise Para. 7.4.2.9 the Sensor/Emitter paragraph to include the case of attached parts 15Radios 7.4.2.7 needs a reference to IEEE 1278.1 16The OPMAN should specify the toolset requirements 17The licensing section needs revision

9. 1 - Match SISO-ADM-005 style guide Submitter: L. Marrou Description: Ensure the OPMAN matches the latest SISO-ADM-005 style guide (copyrights called out as separate issue). Proposed Resolution: Review style guide and updated OPMAN to be in compliance. Any volunteers? Style-guide compliance is REQUIRED. There is no debate here. 11 April 20132013 Spring SIW9

10. 2 - Update copyright: "machine-readable." Submitter: L. Marrou Description: Include the updated copyright statements. For SISO-REF-010 we have agreed to use "machine- readable." Since that includes a documentation section and this OPMAN is numbered in accordance with SISO-REF-010, I recommend we use that copyright statement, but the Reference one would be okay here, too. Perhaps moreso because unlike for the enumerations we don't really desire a derivative product to the OPMAN (outside of SISO). Proposed Resolution: Adopt recommendation for machine-readable. 11 April 20132013 Spring SIW10

11. 3 - Update the Automated Toolset section Submitter: L. Marrou Description: (Graham?) Update the Automated Toolset section with any new changes (one is the copyright statement and that we don't have draft vs. final copyrights). Proposed Resolution: Reject (Close). Graham reviewed these sections and submitted comments. 11 April 20132013 Spring SIW11

12. 4 - Revise Updater to not suggest an enumeration during an add Submitter: G. Shanks Description: Remove subparagraphs 1 & 2 from 8.3.2.3 c) 2) iii and from 8.3.2.4 c) 2) iii. Rationale: the tool does not do this and I’m not sure that this is a good idea anyway. Proposed Resolution: Accept as-is 11 April 20132013 Spring SIW12

13. 5 - Revise Updater to not set the draft/approved copyright Submitter: G. Shanks Description: Remove 8.3.2.3 e) and 8.3.2.4 e) 4). Rationale: there is no longer any difference in the SISO copyright statements for drafts and approved products Proposed Resolution: Accept as-is 11 April 20132013 Spring SIW13

14. 6 - Revise Word Generator to not set the SISO copyright on the first page Submitter: G. Shanks Description: Delete “the SISO copyright on the first page and” from 8.3.2.5 c) 1 and from 8.3.2.6 c) 1. Rationale: there is no longer any difference in the SISO copyright statements for drafts and approved products Proposed Resolution: Accept as-is 11 April 20132013 Spring SIW14

15. 7 - Revise Word Generator standard mode to be in alignment with SISO numbering Submitter: G. Shanks Description: Replace “to include the year, year version & to denote that it is a draft” from 8.3.2.5 c) 2 with “for the current version number and draft number in accordance with SISO-ADM-001”. Rationale: the SISO numbering system has changed Proposed Resolution: Accept as-is 11 April 20132013 Spring SIW15

16. 8 - Revise Word Generator final mode to be in alignment with SISO numbering Submitter: G. Shanks Description: Replace “to include the year & year version” from 8.3.2.6 c) 2 with “for the current version number in accordance with SISO-ADM-001”. Rationale: the SISO numbering system has changed Proposed Resolution: Accept as-is 11 April 20132013 Spring SIW16

17. 9 - Separate all paragraphs and headings by a blank line Submitter: F. Hill Description: An overall editorial comment is that all paragraphs and headings need to be separated by a blank line or use the Word spacing that we used in 1278.1-2012 which is slightly less than a full blank line. This is for readability. Proposed Resolution: Reject (close). Update to style guide as per issue 1. 11 April 20132013 Spring SIW17

18. 10 - Disallow only NATO Reporting Names Submitter: F. Hill Description: "NATO Reporting Names. We need to discontinue allowing a CR to be submitted that only contains the NATO Reporting Name for an enumeration (e.g., aircraft and ship entity types, emitter names, etc.). NATO Reporting names are classified code names. The reason that many of the NATO reporting names have found their way into the public domain is that the cold war is over. There may be other reasons, but the bottom line there is no public access to NATO reporting names and the associated actual equipment they represent either from NATO or the Air and Space Interoperability Council (ASIC). Therefore, for example, the actual national or commercial designation for emitters that have a NATO reporting name cannot always be found through a web search or via Jane's. Therefore, it is possible that a CR may be submitted for an emitter that does not include a NATO Reporting name, but has a national or commercial designation. That emitter may be a duplicate of a NATO reporting name for which no national or commercial designation is listed in SISO-REF-010. I have found that some of the NATO reporting names can yield national and commercial designations through a web search. But if a web search for a commercial or national designation does not yield the associated NATO reporting name, we will not know that the emitter has a NATO reporting name that is in SISO-REF-010 unless someone with access to restricted or clarified information says so. Even then, they will not be able to provide the association if it is still restricted or classified. I disagree with deleting information about the National designation, NATO Reporting Name, and Commercial Designation columns. We need to include a paragraph about submitting emitter names and establish rules." Proposed Resolution: Paragraph to this end has been added. Consider revising the order of suggestion entries. Do not suggest linking the same emitter as submitted by different fields 11 April 20132013 Spring SIW18

19. 11 - Retain the descriptions and rules for CR form fields (including adding rules) Submitter: F. Hill Description: I disagree with deleting anything about the CR form fields. We need to mention certain rules for completing some of the fields. For example, as related to revisions. The name of the Submitter of the revision needs to go in the Submitter name field or a new field needs to be added for the person who submits the revision. If you don't know who submitted the revision by looking at the CR revision, then there is no accountability. Likewise the date needs to be the date the revision is made and not the original date. If the tool cannot be modified, then we must make it a requirement that the actual submitter of a revision, if different from the original submitter must be included in the comment field. The same applies to the actual revision submission date always being included. Proposed Resolution: (a) This text was not deleted, just moved, as explained in the OPMAN updates, so reject un-delete. (b) Add statement to suggest identifier person revising CR in comments. NOTE that given the discussion forum, you can access exactly who submitted what and when. 11 April 20132013 Spring SIW19

20. 12 - Re-evaluate rules for the use of blank and zero fields for Entity Type enumerations Submitter: F. Hill Description: The rules for the use of blank and zero fields for Entity Type enumerations needs to be re-evaluated. A blank in a trailing field needs to be. A blank in a trailing field should be interpreted as a zero value for the field. The zero value needs to be defined as "no Statement". You cannot have wildcards in an Entity Type enumeration and have interoperability. I am not advocating adding zeros to enumeration. I am advocating defining what a trailing blank field means. The sad truth is because zeroes are left out, some projects, organizations, and programs have interpreted that to mean that they are free to use the field anyway they want, including using the field to set real-time values that may change during the exercise or between exercises. Proposed Resolution: (a) In practice, over the last few years, I agree that wildcards (the ‘x’ entry) is not useful. I recommend removing that. (b) Do not otherwise change blank/zero definitions or processing. Blanks are needed for the schema differences (they are not the same). Any changes here would be a significant change in the schema and not advisable at this time. Make it an action item to pursue? Note that I’ve added text to discuss notation. 11 April 20132013 Spring SIW20

21. 13 - Deprecate the use of "Deprecated" Submitter: F. Hill Description: Deprecated has a sordid history and continues to be misused. For example, I believe a new term is need such as "notinservice" to indicate an Entity Type that is no longer in active service. Our rules for submitting a CR to indicate that an entity is no longer in service need to be tightened, such as requiring at least 2 authoritative sources that, in fact, an entity type is no longer in active service. We need to define what "active service" or other term we use means The main purpose I have seen to having a discriminator for inactive entity types is to allow a simulator's data base with limited storage of unique entity types to be reduced. It still comes down to exercise requirements as to which entity types one needs to generate or to be able to process (including rolling up received entity types if necessary. ) Proposed Resolution: Reject (close). There’s a difference between not in service and deprecated. We don’t allow “not in service” deprecations, explicitly mentioned in 7.2. 11 April 20132013 Spring SIW21

22. 14 - Revise Para. 7.4.2.9 the Sensor/Emitter paragraph to include the case of attached parts Submitter: F. Hill Description: Para. 7.4.2.9 the Sensor/Emitter paragraph needs revision as it does not include the case of attached parts. Proposed Resolution: Accept: update to mention attached parts. 11 April 20132013 Spring SIW22

23. 15 - Radios 7.4.2.7 needs a reference to IEEE 1278.1 Submitter: F. Hill Description: Radios 7.4.2.7 needs a reference to IEEE 1278.1 to point the user to the proper IEEE section in order to properly fill out some of the fields. Proposed Resolution: Accept: add reference for those users of 1278.1 (but not as a general requirement for these fields) 11 April 20132013 Spring SIW23

24. 16 - The OPMAN should specify the toolset requirements Submitter: F. Hill Description: I see the OPMAN as specifying the toolset requirements. If the present toolset cannot meet certain requirements, that does not mean we should delete those requirements. However, we may want to note those desired requirements that are not presently implemented by the existing tool we are using. Proposed Resolution: Close (not actionable) 11 April 20132013 Spring SIW24

25. 17 - The licensing section needs revision Submitter: F. Hill Description: The licensing section needs revision. We shouldn't be recommending anything but, instead, be stating our firm requirements based on experience to date. Proposed Resolution: TBD 11 April 20132013 Spring SIW25

26. CR Review 11 April 20132013 Spring SIW26

27. Action Items (Unassigned) 191 - Define portable weapons 193 - Define Commonplace Objects 198 - Implement web hosting capabilities 221 - STD/Spec reference schema design (and populate) 222 - Protected schema design (and populate) 252 - Review character sets and encodings allowable within the XML/XSD (UTF-8 only?) 253 - Investigate a clearer definition of object specific appearance in relation to object type. 256 - Consider schema change to support Emitter Name (75) with structural attributes/elements and NOT metadata 11 April 20132013 Spring SIW27

28. ENUMS: Status (Current) Previous version: SISO-REF-010-2011 ‒ April 2011 ‒ 114 CRs processed  48 approved  66 withdrawn/rejected ‒ Major upgrade from SISO-REF-010-2006 Current version: SISO-REF-010-2011.1 ‒ December 2011 ‒ 224 CRs processed  138 approved  86 rejected ‒ Changes: schema, templates, civilian air platforms 11 April 20132013 Spring SIW28

29. ENUMS: Status (Next) SISO-REF-010-00v20-0 (ETA ?) ‒ 381 CRs processed (285 approved, 96 rejected) ‒ Major Changes (see next slide) CRs TBD (e.g., v21) ‒ 7 approved, 9 rejected ‒ 10 pending ‒ 517 remaining 11 April 20132013 Spring SIW29

30. SISO-REF-010-00v20-0 DIS v7 CRs (63, 2651-2713) Land Domain Civilian Platforms Surface Domain Civilian Platforms Implicit Entity Types (e.g., generic civilian surface platforms) Emitters (24 CRs) Reorganization ‒ In accordance with SISO-ADM-005 Style Guide ‒ To better support protocols other than DIS ‒ UID values clearly noted (used by 1278.1) ‒ Text schema updates to move as much text from template to XML or OPMAN Introduction changes according to SAC and EXCOM Bitmasks (records) schema revision Does NOT Contain: ‒ Life Form Updates ‒ Supplies major revision 11 April 20132013 Spring SIW30

31. Civilian Platforms Summary Needed significant updates to entity types to support civilian platforms ‒ Air Domain (Bob Murray – Boeing)  Changes (except deprecation of CAT 57) incorporated in SISO- REF-010-2011.1  Deprecations CRs 2569-2570 in SISO-REF-010-00v20-0 ‒ Land – CRs 2547-2562; 2567-2568 (Lance Marrou – SE Core CVEM; CAF DMO) ‒ Surface – CRs 2714-2725 (Theresa Reynolds – NCTE) ‒ Subsurface/Space – no plans yet Category values start at 80 for civilian platforms Subcategory values predetermined for each Category 11 April 20132013 Spring SIW31

32. Current Status of Operations Manual SISO-REF-010.1-2011 (April 2011) SISO-REF-010-01v2-0 (ETA Summer 2013) ‒ Clarification on Entity Type notation  Do not use leading zeroes  Zeroes at the end may be left out; but then refers to that entity and all potential children ‒ 1 CR may be used to accumulate all acronyms for a particular revision ‒ Provided exceptions for allowing deletion (rather than deprecation):  Schema change or schema record deletion  Copyrighted, trademarked, or patented text  Enumerations later determined to be classified ‒ Clarification on real-world entities that exist, changed “commissioned” to “launched” ‒ Provided clarification on capitalization (title-case): Capitalize the first and last words of the enumeration and all nouns, pronouns, adjectives, verbs, adverbs, and subordinating conjunctions (if, because, as, that, and so on). Articles (a, an, the), coordinating conjunctions (and, but, or, for, nor), and prepositions, regardless of length, are lower-cased unless they are the first or last word of the enumeration ‒ Provided clarification of the notations for transferred and variation 11 April 20132013 Spring SIW32

33. Current Status of Operations Manual SISO-REF-010-01v2-0 (ETA Summer 2013) (Continued…) ‒ Clarification on Base ID for transfers and variants  The Base ID of the new entity type (for change of country ownership for uniquely identified entity types) shall be set to the entity type from which it was transferred. The Base ID of the transferred entity type shall be set to the new entity type.  The Base ID of the new entity type (for country design variations of recurrent entity types) shall be set to the entity type from which the design is derived. ‒ Provided rules for miscategorized entries: ‒ Provided rules for duplicate entries: ‒ Provided clarification on footnotes: Footnotes are only added on new or updated enumeration entries and not on deprecations. To add a footnote while deprecating an entry, use a separate line to update the entry first. ‒ Deleted notation for “replaced” ‒ Clarified some wording in the examples ‒ Provided guidelines for Emitter Name fields 11 April 20132013 Spring SIW33

34. EWG Enumerations Guidelines and Rules Defines notation using decimal points (e.g., 1.1.225.2.5.22) (trailing zeroes not required) Deprecation guidelines and rules (including deletion) Entity Types are added for real-world entities that exist or have existed Capitalization guidelines Country codes are not used to identify regions (e.g., Europe) or organizations (e.g., Taliban) A change of country ownership can occur for uniquely identified entity types (these are typically ships) A country design variation can be made for recurrent entity types Ammunition loads are not specified in the Entity Type Emitter Names, recommended in order (only one): NATO, commercial, national; no Electronic Intelligence Notation (ELNOT) 11 April 20132013 Spring SIW34

35. Automated Toolset Status Tools written ‒ Registrar (C#, Windows.NET) ‒ Updater (C#, Windows.NET) XSLT Translators ‒ Excel® Generator (from XSLT) ‒ C99 Header (from XSLT) ‒ HTML and PDF Generator (from document) Open source Registrar, Updater, and Word Generator ‒ SourceForge: http://sourceforge.net/projects/esitools/http://sourceforge.net/projects/esitools/ ‒ Boost Software License (BSL 1.0) ‒ Initial commit access limited to Graham, DIS PSG Officers, and EWG Lead ‒ Copyright by Graham Shanks Tools TBD: Publisher, Status Publisher Significant updates being made for SISO-REF-010-00v20-0 11 April 20132013 Spring SIW35