{"action":"created","issue":{"url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/issues/229","repository_url":"https://api.github.com/repos/Esri/joint-military-symbology-xml","labels_url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/issues/229/labels{/name}","comments_url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/issues/229/comments","events_url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/issues/229/events","html_url":"https://github.com/Esri/joint-military-symbology-xml/issues/229","id":111738201,"number":229,"title":"Cyberspace amplifier ambiguity","user":{"login":"meterlongcat","id":13348788,"avatar_url":"https://avatars.githubusercontent.com/u/13348788?v=3","gravatar_id":"","url":"https://api.github.com/users/meterlongcat","html_url":"https://github.com/meterlongcat","followers_url":"https://api.github.com/users/meterlongcat/followers","following_url":"https://api.github.com/users/meterlongcat/following{/other_user}","gists_url":"https://api.github.com/users/meterlongcat/gists{/gist_id}","starred_url":"https://api.github.com/users/meterlongcat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/meterlongcat/subscriptions","organizations_url":"https://api.github.com/users/meterlongcat/orgs","repos_url":"https://api.github.com/users/meterlongcat/repos","events_url":"https://api.github.com/users/meterlongcat/events{/privacy}","received_events_url":"https://api.github.com/users/meterlongcat/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/labels/B%20-%20Question","name":"B - Question","color":"FAD8C7"},{"url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/labels/G%20-%20Military%20Team","name":"G - Military Team","color":"207DE5"}],"state":"open","locked":false,"assignee":{"login":"abouffard","id":4564846,"avatar_url":"https://avatars.githubusercontent.com/u/4564846?v=3","gravatar_id":"","url":"https://api.github.com/users/abouffard","html_url":"https://github.com/abouffard","followers_url":"https://api.github.com/users/abouffard/followers","following_url":"https://api.github.com/users/abouffard/following{/other_user}","gists_url":"https://api.github.com/users/abouffard/gists{/gist_id}","starred_url":"https://api.github.com/users/abouffard/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abouffard/subscriptions","organizations_url":"https://api.github.com/users/abouffard/orgs","repos_url":"https://api.github.com/users/abouffard/repos","events_url":"https://api.github.com/users/abouffard/events{/privacy}","received_events_url":"https://api.github.com/users/abouffard/received_events","type":"User","site_admin":false},"assignees":[{"login":"abouffard","id":4564846,"avatar_url":"https://avatars.githubusercontent.com/u/4564846?v=3","gravatar_id":"","url":"https://api.github.com/users/abouffard","html_url":"https://github.com/abouffard","followers_url":"https://api.github.com/users/abouffard/followers","following_url":"https://api.github.com/users/abouffard/following{/other_user}","gists_url":"https://api.github.com/users/abouffard/gists{/gist_id}","starred_url":"https://api.github.com/users/abouffard/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abouffard/subscriptions","organizations_url":"https://api.github.com/users/abouffard/orgs","repos_url":"https://api.github.com/users/abouffard/repos","events_url":"https://api.github.com/users/abouffard/events{/privacy}","received_events_url":"https://api.github.com/users/abouffard/received_events","type":"User","site_admin":false}],"milestone":{"url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/milestones/4","html_url":"https://github.com/Esri/joint-military-symbology-xml/milestones/Version%20-%20Next","labels_url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/milestones/4/labels","id":1087716,"number":4,"title":"Version - Next","description":"This version of JMSML will be focused on making the changes needed to produce the exported output needed to facilitate the automated creation of a template military feature geodatabase.  The tools used to create that geodatabase are part of the military features data repo.\r\n\r\nIssues concerning legacy mapping will also be addressed, ensuring that we have a clear understanding regarding what symbols in 2525D map to symbols in 2525C and vice versa.  Aditional exports and changes to some existing exports will address this.  Removing redundant control measures, as directed by approved SSMC CP 15-022-DS will also impact this effort.\r\n\r\nSome minor enhancements will also be made to the JMSML XML schema and instance data to support some special icon characteristics in 2525D.","creator":{"login":"conklinbd","id":2582674,"avatar_url":"https://avatars.githubusercontent.com/u/2582674?v=3","gravatar_id":"","url":"https://api.github.com/users/conklinbd","html_url":"https://github.com/conklinbd","followers_url":"https://api.github.com/users/conklinbd/followers","following_url":"https://api.github.com/users/conklinbd/following{/other_user}","gists_url":"https://api.github.com/users/conklinbd/gists{/gist_id}","starred_url":"https://api.github.com/users/conklinbd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/conklinbd/subscriptions","organizations_url":"https://api.github.com/users/conklinbd/orgs","repos_url":"https://api.github.com/users/conklinbd/repos","events_url":"https://api.github.com/users/conklinbd/events{/privacy}","received_events_url":"https://api.github.com/users/conklinbd/received_events","type":"User","site_admin":false},"open_issues":10,"closed_issues":13,"state":"open","created_at":"2015-04-28T15:43:11Z","updated_at":"2016-04-29T15:14:06Z","due_on":"2015-10-30T05:00:00Z","closed_at":null},"comments":3,"created_at":"2015-10-16T01:14:06Z","updated_at":"2016-07-20T14:53:08Z","closed_at":null,"body":"Good morning,\r\n\r\nI believe I have found an ambiguity for Cyberspace amplifiers, but am hopeful that I've just misinterpreted it and you can correct me. Here goes:\r\n\r\nSection L.5.3.3 of the 2525D spec states that the valid amplifiers for a Cyberspace symbol is dependent on the dimension of that symbol. This is reflected in _jmsml_D_Base.xml_, where multiple Dimensions contain Cyberspace. Each Dimension also captures the valid Fields (which includes amplifiers). This allows the valid amplifiers for a Cyberspace symbol to be retrieved via the relevant Dimension it belongs to. So far so good.\r\n\r\nConsider the following code-flow with example Cyberspace SIDC 1006600000 0000000000:\r\n\r\nMethod _Symbol#\\_UpdateFromCurrent()_ populates the various properties of the _Symbol_ object. Specifically, it calls _\\_librarian.SymbolSet(...)_, passing 6 and 0 (60 = Cyberspace's symbol set). This returns the correct Symbol Set object. Next _\\_librarian.DimensionBySymbolSet(...)_ is called, passing \"SS_CYBERSPACE\". This is where the ambiguity starts. Method _Librarian#DimensionBySymbolSet_ cannot determine what dimension the Cyberspace symbol exists in, and always returns the \"AIR\" dimension because it is the first dimension containing Cyberspace. This means that currently, all Cyberspace symbols are considered to be in the AIR dimension. Ultimately this means that the returned amplifiers for a Cyberspace symbol are always those defined for AIR.\r\n\r\nAs I understand it, the SIDC Symbol Set is used to pick the dimension. Therefore there is currently no way of defining a SIDC that defines a Cyberspace symbol plus the dimension it's in, because you can only have a single Symbol Set.\r\n\r\nIt looks like the 2525D spec is deficient in this regard, and requires the single Symbol Set 60 to be split into multiples as follows (much like Signals Intelligence already is):\r\n- Cyberspace - Space\r\n- Cyberspace - Air\r\n- Cyberspace - Land\r\n- etc.\r\n\r\nKind Regards,\r\nJan"},"comment":{"url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/issues/comments/233973949","html_url":"https://github.com/Esri/joint-military-symbology-xml/issues/229#issuecomment-233973949","issue_url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/issues/229","id":233973949,"user":{"login":"joebayles","id":5016557,"avatar_url":"https://avatars.githubusercontent.com/u/5016557?v=3","gravatar_id":"","url":"https://api.github.com/users/joebayles","html_url":"https://github.com/joebayles","followers_url":"https://api.github.com/users/joebayles/followers","following_url":"https://api.github.com/users/joebayles/following{/other_user}","gists_url":"https://api.github.com/users/joebayles/gists{/gist_id}","starred_url":"https://api.github.com/users/joebayles/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joebayles/subscriptions","organizations_url":"https://api.github.com/users/joebayles/orgs","repos_url":"https://api.github.com/users/joebayles/repos","events_url":"https://api.github.com/users/joebayles/events{/privacy}","received_events_url":"https://api.github.com/users/joebayles/received_events","type":"User","site_admin":false},"created_at":"2016-07-20T14:53:08Z","updated_at":"2016-07-20T14:53:08Z","body":"@abouffard can you update this as necessary?"}}
{"actor":{"display_login":"joebayles"}}