Fwd: FW: XML-MTF Refactor Collaborative Project
266 views
Skip to first unread message
James Neushul
Nov 1, 2014, 1:01:19 PM11/1/14
to MIL OSS
Hi All,
I`ve been lurking too long.
Per below ..Working to refactor USMTF and NATO MTF. Hope to fix releasability issues but until then has to remain behind the wire. NIEM conformance will require public access.
Anyone already working MTF with DoD welcome to join.
If anyone has gotten Forge svn to work with 64 Bit Ubuntu please let me know. Tired of having to use winBlows VM for subversion.
Semper OSS!
Neutron
---------- Forwarded message ----------
From: "Neushul Maj James D" <james....@usmc.mil>
Date: Oct 3, 2014 8:47 AM
Subject: FW: XML-MTF Refactor Collaborative Project
To: "james....@gmail.com" <james....@gmail.com>
Cc: "james.d.n...@mail.mil" <james.d.n...@mail.mil>
-----Original Message-----
From: Neushul Maj James D
Sent: Friday, October 03, 2014 8:45 AM
To: 'Terry...@act.nato.int'; 'charles.c...@us.af.mil'; Connally CIV Earl M; 'steven.f...@mail.mil'; jeffery.c....@mail.mil; 'Raymond.f...@mail.mil'; Francis CIV David L; 'lam.d.h...@mail.mil'; 'mark.j.maj...@mail.mil'; 'marcus...@us.af.mil'; 's...@mitre.org'; Wade LT Travis L; 'Wink...@mitre.org'; 'Amit.r.da...@us.af.mil'; 'rodney.mc...@us.af.mil'; Stienon CTR Julian P; jacqueline.l...@mail.mil; Kays CIV Jennifer E; Pfaff, Rebekah J (Rebeka...@ManTech.com); Anderson, Thomas (Tom) (CIV) (tsan...@nps.edu); M_MCTSSA_TCG_IOB_Branch
Cc: Giersch LtCol Tarrell; Coates Civ Robert A; Roe CIV Murray O; Canterbury CIV Michael G; 'Stone CIV Shawn'; 'james.d.n...@mail.mil'
Subject: XML-MTF Refactor Collaborative Project
This is the Project Kickoff announcement for the MTF XML development effort on Forge.mil.
Please log in to https://software.forge.mil/sf/projects/mtfxml to track progress and participate. DoD CAC is required.
Request membership and participate in discussions, create tasks and participate as appropriate. Invite maximum participation. If you would like "Project Leader" status in order to approve more people and adjust permissions please let me know.
Anyone across the DoD with vested interests in this MIL STD and can be invited to participate. Subversion tracks all changes - so please do not worry about unauthorized or inappropriate changes by anyone. A problem of too much participation is one we would like to have and can easily be mitigated. I will take responsibility for doing this - but others may do so as well.
This methodology is based on a success model which drives some of the most impactful resources on the web and in the world today (i.e.: Apache, Linux, OGC, Android, etc.). Community involvement is a metric which indicates relevance.
Basics:
Version Control:
1. All of my work has been uploaded. I will "commit" all changes going forward.
2. If you use a SVN client to "Check out" work - the first download will be large but all subsequent actions will be differences only and are very efficient.
3. Your SVN Client will display an icon for files that have been updated - thereby allowing you to always work with the latest version.
4. Everyone has the ability to "revert" to prior versions using your SVN client
5. For work which is divergent or not intended to be part of the main effort there is the ability to create "Tags" or "Branches".
6. Documents can be versioned as well as source / XML files as long as you use a Subversion client.
7. For Windows users - Tortoise SVN is integrated into the file system and is very useful for this work.
Recommended Practices;
1. While documents (i.e.: spreadsheets) are likely to be used initially, I will eventually encourage developers to use simple XML documents which contain changes and annotation. These can be easily applied to implement XML Schema changes using XSLT.
2. These do not have to be XML Schemas since we can employ XSLT to apply appropriate Schema naming and design rules as well as generate documentation to support ICPs.
3. Initially - XML used for CM / ICP development do not need XML Schemas or namespaces, but in the future we may employ them in order to support automated XML CM activities.
4. I can read spreadsheets to XML and will do so initially if XML is not comfortable for everyone. I will post the code to do this.
5. Eventually we will implement a "continuous build" process that will automatically run tests on every message in the MIL STD in order to verify that changes do not "break the build" - or render other messages invalid or non-compliant with naming and design rules.
Tasks:
1. Because this is a very complex effort we need to avoid duplication of work and allow developer/implementation comments engagement earliest.
2. Active participant are encouraged to generate tasks for themselves within the categories I have created - or make new categories.
3. If you use the tasks to pace your own activities we will gain awareness of how long things are going to take.
4. There are no rules with regard to "estimated time" etc. They simply raise awareness. Adjust freely.
5. Please create a discussion topic for each task category and endeavor to capture all pertinent remarks there. These will be used to achieve consensus and craft the ICP. Service representatives can indicate initial approval here.
6. Ideally we want to be able to segment work into manageable chunks - approximating Agile behaviors. It is beneficial to decompose complex efforts into specific parts.
5. Basic task examples:
1. Create list of items that may require ICP actions using Spreadsheet or XML
2. Add proposed changes and comments
3. Incorporate the changes into draft "Venetian Blind" XML Schemas
4. Incorporate the changes into draft "Garden of Eden" XML Schemas
5. Verify that changes do not adversely impact referencing XML Schemas or messages across the MIL STD
Note: I will likely be able to take on 3-5 where needed and will endeavor to provide documentation on how it is done so that others can do it.
Collaboration:
1. Some things have been done by others across the DoD.
2. Posting a reference implementation task, for example, will allow them the opportunity contribute work.
3. There are likely many implementations in the DoD for parsing USMTF text and XML that don't need to be reinvented. We can collect them here and select best of breed.
4. Please advertise this effort to encourage involvement.
I will add these notes to the Dev Site, as well as start a "Process" discussion. Please use that to post comments, suggestions or issues.
Respectfully,
Major James D. Neushul
Marine Corps Tactical Systems Support Activity
james....@usmc.mil
james.d.n...@mail.mil
james....@gmail.com
760-576-5015
-----Original Message-----
From: CHIPMAN, CHARLES E CTR USAF ACC ACC A589/A5JI [mailto:charles.c...@us.af.mil]
Sent: Wednesday, October 01, 2014 10:04 AM
To: Neushul Maj James D
Cc: POWER, MARCUS E GS-12 USAF ACC ACC A589/A5JI; MCCOY, RODNEY A CTR USAF ACC ACC A589/A5JI; DASWANI, AMIT R CTR USAF ACC ACC A589/A5JI
Subject: XML-MTF Refactor
With notes from today's meeting.
From: "Neushul Maj James D" <james....@usmc.mil>
Date: Oct 3, 2014 8:47 AM
Subject: FW: XML-MTF Refactor Collaborative Project
To: "james....@gmail.com" <james....@gmail.com>
Cc: "james.d.n...@mail.mil" <james.d.n...@mail.mil>
-----Original Message-----
From: Neushul Maj James D
Sent: Friday, October 03, 2014 8:45 AM
To: 'Terry...@act.nato.int'; 'charles.c...@us.af.mil'; Connally CIV Earl M; 'steven.f...@mail.mil'; jeffery.c....@mail.mil; 'Raymond.f...@mail.mil'; Francis CIV David L; 'lam.d.h...@mail.mil'; 'mark.j.maj...@mail.mil'; 'marcus...@us.af.mil'; 's...@mitre.org'; Wade LT Travis L; 'Wink...@mitre.org'; 'Amit.r.da...@us.af.mil'; 'rodney.mc...@us.af.mil'; Stienon CTR Julian P; jacqueline.l...@mail.mil; Kays CIV Jennifer E; Pfaff, Rebekah J (Rebeka...@ManTech.com); Anderson, Thomas (Tom) (CIV) (tsan...@nps.edu); M_MCTSSA_TCG_IOB_Branch
Cc: Giersch LtCol Tarrell; Coates Civ Robert A; Roe CIV Murray O; Canterbury CIV Michael G; 'Stone CIV Shawn'; 'james.d.n...@mail.mil'
Subject: XML-MTF Refactor Collaborative Project
This is the Project Kickoff announcement for the MTF XML development effort on Forge.mil.
Please log in to https://software.forge.mil/sf/projects/mtfxml to track progress and participate. DoD CAC is required.
Request membership and participate in discussions, create tasks and participate as appropriate. Invite maximum participation. If you would like "Project Leader" status in order to approve more people and adjust permissions please let me know.
Anyone across the DoD with vested interests in this MIL STD and can be invited to participate. Subversion tracks all changes - so please do not worry about unauthorized or inappropriate changes by anyone. A problem of too much participation is one we would like to have and can easily be mitigated. I will take responsibility for doing this - but others may do so as well.
This methodology is based on a success model which drives some of the most impactful resources on the web and in the world today (i.e.: Apache, Linux, OGC, Android, etc.). Community involvement is a metric which indicates relevance.
Basics:
Version Control:
1. All of my work has been uploaded. I will "commit" all changes going forward.
2. If you use a SVN client to "Check out" work - the first download will be large but all subsequent actions will be differences only and are very efficient.
3. Your SVN Client will display an icon for files that have been updated - thereby allowing you to always work with the latest version.
4. Everyone has the ability to "revert" to prior versions using your SVN client
5. For work which is divergent or not intended to be part of the main effort there is the ability to create "Tags" or "Branches".
6. Documents can be versioned as well as source / XML files as long as you use a Subversion client.
7. For Windows users - Tortoise SVN is integrated into the file system and is very useful for this work.
Recommended Practices;
1. While documents (i.e.: spreadsheets) are likely to be used initially, I will eventually encourage developers to use simple XML documents which contain changes and annotation. These can be easily applied to implement XML Schema changes using XSLT.
2. These do not have to be XML Schemas since we can employ XSLT to apply appropriate Schema naming and design rules as well as generate documentation to support ICPs.
3. Initially - XML used for CM / ICP development do not need XML Schemas or namespaces, but in the future we may employ them in order to support automated XML CM activities.
4. I can read spreadsheets to XML and will do so initially if XML is not comfortable for everyone. I will post the code to do this.
5. Eventually we will implement a "continuous build" process that will automatically run tests on every message in the MIL STD in order to verify that changes do not "break the build" - or render other messages invalid or non-compliant with naming and design rules.
Tasks:
1. Because this is a very complex effort we need to avoid duplication of work and allow developer/implementation comments engagement earliest.
2. Active participant are encouraged to generate tasks for themselves within the categories I have created - or make new categories.
3. If you use the tasks to pace your own activities we will gain awareness of how long things are going to take.
4. There are no rules with regard to "estimated time" etc. They simply raise awareness. Adjust freely.
5. Please create a discussion topic for each task category and endeavor to capture all pertinent remarks there. These will be used to achieve consensus and craft the ICP. Service representatives can indicate initial approval here.
6. Ideally we want to be able to segment work into manageable chunks - approximating Agile behaviors. It is beneficial to decompose complex efforts into specific parts.
5. Basic task examples:
1. Create list of items that may require ICP actions using Spreadsheet or XML
2. Add proposed changes and comments
3. Incorporate the changes into draft "Venetian Blind" XML Schemas
4. Incorporate the changes into draft "Garden of Eden" XML Schemas
5. Verify that changes do not adversely impact referencing XML Schemas or messages across the MIL STD
Note: I will likely be able to take on 3-5 where needed and will endeavor to provide documentation on how it is done so that others can do it.
Collaboration:
1. Some things have been done by others across the DoD.
2. Posting a reference implementation task, for example, will allow them the opportunity contribute work.
3. There are likely many implementations in the DoD for parsing USMTF text and XML that don't need to be reinvented. We can collect them here and select best of breed.
4. Please advertise this effort to encourage involvement.
I will add these notes to the Dev Site, as well as start a "Process" discussion. Please use that to post comments, suggestions or issues.
Respectfully,
Major James D. Neushul
Marine Corps Tactical Systems Support Activity
james....@usmc.mil
james.d.n...@mail.mil
james....@gmail.com
760-576-5015
-----Original Message-----
From: CHIPMAN, CHARLES E CTR USAF ACC ACC A589/A5JI [mailto:charles.c...@us.af.mil]
Sent: Wednesday, October 01, 2014 10:04 AM
To: Neushul Maj James D
Cc: POWER, MARCUS E GS-12 USAF ACC ACC A589/A5JI; MCCOY, RODNEY A CTR USAF ACC ACC A589/A5JI; DASWANI, AMIT R CTR USAF ACC ACC A589/A5JI
Subject: XML-MTF Refactor
With notes from today's meeting.
Boyd Fletcher
Nov 1, 2014, 6:14:21 PM11/1/14
to mil...@googlegroups.com, Roger Costello
James
We have generic parser than leverages the Data Format Description Language (DFDL) to parse a variety of military message formats including USMTF, VMF, OTH-G, and TADIL-J. It can also parse LOTS of other data types.
We have an example of converting USMTF's ATO into its XML representation using DFDL and a little XSLT Magic.
Google "dfdl and daffodil" the first set of links at NCSA is where the parser is hosted.
Some example VMF and USMTF DFDL schemas are on forge.mil (search for DFDL) since they are FOUO.
If interested drop me an email at boyd.c.fle...@mail.mil
Boyd
--
--
You received this message because you are subscribed to the "Military Open Source Software" Google Group.
To post to this group, send email to mil...@googlegroups.com
To unsubscribe from this group, send email to mil-oss+u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/mil-oss?hl=en
www.mil-oss.org
---
You received this message because you are subscribed to the Google Groups "Military Open Source Software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mil-oss+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Arnie Shore
Nov 1, 2014, 6:17:27 PM11/1/14
to mil...@googlegroups.com
It had to happen; a discussion of military message formats without a mention of JANAP128
Boyd Fletcher
Nov 1, 2014, 6:55:24 PM11/1/14
to mil...@googlegroups.com, Roger Costello
Forgot to mention the parser is called "Daffodil" and DFDL is an open standard from the open grid forum.
Boyd Fletcher
M: 757.535.8190
John Scott
Nov 4, 2014, 8:46:08 AM11/4/14
to Boyd Fletcher, mil...@googlegroups.com, Roger Costello
Reply all
Reply to author
Forward
0 new messages