Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
start [2016/03/15 06:30] admin Adding new ssubsection |
start [2020/02/21 14:02] (current) admin [Table] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | {{curiosity-rover-rocknest-panorama.jpg|}} | + | ====== Middleware and Related Services (MARS) Platform Task Force (PTF)====== |
| - | + | {{:curiosity-rover-rocknest-panorama.jpg?600|}} | |
| - | The above is a panorama taken by the MARS Curiosity Rover | + | \\ Rocknest Panorama taken by NASA's Mars Curiosity Rover |
| - | ====== Middleware and Related Services (MARS) Platform Task Force (PTF) ====== | + | |
| ===== Mission ===== | ===== Mission ===== | ||
| - | To solicit, evaluate, and select specifications for recommendation to the Platform Technology Committee for adoption by the OMG (http://www.omg.org/) in the areas of: | + | {{ :another_mars.jpg?100|}}To solicit, evaluate, and select specifications for recommendation to the Platform Technology Committee for adoption by the OMG (http://www.omg.org/) in the areas of: |
| - Request Broker Technology - including but not limited to Object Request Brokers (CORBA), Message-Oriented Brokers and other technologies that are the target implementation contexts for Platform Independent Services and their Mappings. | - Request Broker Technology - including but not limited to Object Request Brokers (CORBA), Message-Oriented Brokers and other technologies that are the target implementation contexts for Platform Independent Services and their Mappings. | ||
| - General purpose Pervasive Services that are either: | - General purpose Pervasive Services that are either: | ||
| Line 13: | Line 11: | ||
| - Mappings for such Pervasive Services to specific middleware platforms, and reference mappings from generic PIM constructs to platform-specific constructs and protocol rules. | - Mappings for such Pervasive Services to specific middleware platforms, and reference mappings from generic PIM constructs to platform-specific constructs and protocol rules. | ||
| - Supporting Technologies for Application Integration, Information Integration, and Collaboration | - Supporting Technologies for Application Integration, Information Integration, and Collaboration | ||
| - | |||
| ===== Co-Chairs ===== | ===== Co-Chairs ===== | ||
| - | ^ Name |Charlotte Wales | |Virginie Watine | | + | ^ Name | Charlotte Wales | Peter Denno | |
| - | ^ Company |The MITRE Corporation | |T H A L E S | | + | ^ Company | Jackrabbit Consulting | National Institute of Standards & Technology (NIST) | |
| - | ^ Email |<charwing@mitre.org> | |<virginie.watine@fr.thalesgroup.com> | | + | ^ Email | <char@drstavros.com> | <peter.denno@nist.gov> | |
| Line 50: | Line 47: | ||
| ===== Working Groups (WGs) ===== | ===== Working Groups (WGs) ===== | ||
| - | To paraphrase the MARS home page, MARS hosts a number of WGs that serve as MARS' technology incubators. The members of a WG meet to explore specific technologies, e.g., prepare and review responses to RFIs, present their findings to the TF or as a published green papers, and prepare Draft RFPs. There are 3 __//active//__ working groups at this time [★]: | + | MARS hosts a number of WGs that serve as MARS' technology incubators. These WGs are focused on and responsible for advancing a specific technology area. This may include the preparation of and review of responses from RFIs and the preparation of RFPs. There are 5 __//active//__ working groups at this time: |
| - | * **High Performance Embedded Computing (HPEC) Working Group** (Chartered March 2012) | + | * **Information Exchange Framework Working Group** (Chartered December 2005 - [[ief|]]) |
| - | * Wiki: [[http://www.omgwiki.org/hpec/]]; Maillist: [email protected] | + | |
| - | * Two RFCs -- for VSIPL and VSIPL++ -- successfully issued, adopted, and released as formal OMG specs ([[http://www.omg.org/spec/VSIPL/]] and [[http://www.omg.org/spec/VSIPL++/]]); other specifications based on these adopted specs are being considered. | + | |
| - | * This WG meets quarterly, co-located with the OMG TC quarterly meeting once or twice a year. | + | |
| - | * **Information Exchange Framework ([[IEF]]) Working Group** (Chartered December 2005) | + | |
| * Wiki: [[http://www.omgwiki.org/mars/doku.php?id=ief]]; maillist: [email protected] | * Wiki: [[http://www.omgwiki.org/mars/doku.php?id=ief]]; maillist: [email protected] | ||
| - | * Working from a roadmap for specifications to be developed (not just in MARS) to address the areas of policy based information exchange. Per this roadmap, two RFPs of three were issued. Of these two - one has since been withdrawn in deference to a new RFP issued in March 2014 to establish an IEF Reference Architecture ([[http://www.omg.org/cgi-bin/doc.cgi?mars/2014-3-17]]). In any case, the IEF Policy Based Packaging Vocabulary (IEPPV) specification was adopted in December 2013 and formalized in May 2015 [[http://www.omg.org/spec/IEPPV/]]. | + | * Working from a roadmap for specifications to be developed (not just in MARS) to address the areas of policy based information exchange. |
| - | * **Rich Internet Application (RIA) Working Group** (Chartered December 2009) | + | * The IEF Policy Based Packaging Vocabulary (IEPPV) specification was adopted in December 2013 and formalized in May 2015 [[http://www.omg.org/spec/IEPPV/]]. |
| - | * Wiki: [[http://www.omgwiki.org/mars/doku.php?id=ria&s=ria]] | + | * During the March 2017 meeting, hosted an IEF Info Day that was successful altho lightly attended (link to InfoDay page [[https://www.omg.org/news/meetings/tc/va-17/special-events/IEF_Day.htm]]). |
| - | * RIA Dynamic Component Model RFP issued in March 2013. Initial Submission rescheduled and expected in September 2015. Refer to [[http://www.omg.org/members/cgi-bin/doc?mars/15-03-10.pdf]] for a foretaste of what the submission will contain. | + | * The IEF Reference Architecture (IEF RA) was approved for adoption in June 2017 and completed finalization in June 2019. All that remains is approval by the Board. Finalized spec is here: [[https://www.omg.org/cgi-bin/doc?ptc/19-06-07]] |
| - | * **IDL Profiles Working Group** (Chartered March 2009, nominally disbanded June 2015) | + | * The IEF Policy Based Packaging Service (IEPPS) RFP was issued in December 2017 [[https://www.omg.org/cgi-bin/doc?mars/17-12-12]]; a revised (possibly final) submission is expected in December 2019 ([[https://www.omg.org/techprocess/meetings/schedule/IEPPS_RFP.html]]) |
| + | * **IDL Working Group** (Chartered March 2009) | ||
| * Maillist: [email protected] | * Maillist: [email protected] | ||
| * Vision Statement: mars/09-06-04 ([[http://www.omg.org/members/cgi-bin/doc?mars/09-06-04.pdf]]) | * Vision Statement: mars/09-06-04 ([[http://www.omg.org/members/cgi-bin/doc?mars/09-06-04.pdf]]) | ||
| * IDL 3.5 successfully issued as an RFC and is now a formal specification ([[http://www.omg.org/spec/IDL35/]]) | * IDL 3.5 successfully issued as an RFC and is now a formal specification ([[http://www.omg.org/spec/IDL35/]]) | ||
| - | * IDL 4.0 was issued as an RFC in March 2015 and, as of June 2015, is an adopted specification scheduled to be finalized by December 2015. (link to beta spec [[http://www.omg.org/spec/IDL/]]) | + | * IDL 4.0, issued as an RFC in March 2015, has been adopted, finalized, and revised. The current formalized version is IDL 4.2 ([[https://www.omg.org/spec/category/interface-definition-language/]]. IDL 4.2 was submitted to ISO and is in the final stages of approval. |
| - | * Based on the adoption of IDL 4.0, the work of the IDL WG is effectively complete; however, how to organize existing and new IDL specifications to align with IDL 4.0 continues as a topic of discussion. | + | * Since the adoption of IDL 4.0, the IDL WG has been busy: organizing existing and new IDL mapping specifications to align with IDL 4.x. To date, its work has lead to the following: |
| + | * IDL4 to Java Mapping: adopted June 2019 [[https://www.omg.org/cgi-bin/doc?mars/19-05-06]] | ||
| + | * IDL4 to C# Mapping: underway; revised submission expected Dec 2019 [[https://www.omg.org/cgi-bin/doc?mars/18-12-02]] | ||
| + | * IDL4 to C++ Mapping: new; Draft RFC expected Dec 2019 | ||
| + | * **High Performance Embedded Computing (HPEC) Working Group** (Chartered March 2012) | ||
| + | * Wiki: [[http://www.omgwiki.org/hpec/]]; Maillist: [email protected] | ||
| + | * Two RFCs -- for VSIPL and VSIPL++ -- successfully issued, adopted, and released as formal OMG specs ([[http://www.omg.org/spec/VSIPL/]] and [[http://www.omg.org/spec/VSIPL++/]]); other specifications based on these adopted specs are being considered. | ||
| + | * This WG meets quarterly, co-located with the OMG TC quarterly meeting once or twice a year. In the process of looking for new leadership. | ||
| + | * **SNC Working Group** (chartered June 2017) | ||
| + | * Wiki: [[https://www.omgwiki.org/snc-wg/doku.php]]; Maillist: [email protected] | ||
| + | * Organized in June 2017 during Brussels meeting. | ||
| + | * Issued the Secure Network Communications RFI in September 2017: mars/17-09-29 ([[https://www.omg.org/schedule/SNC_RFI.html]]) | ||
| + | * Since Dec 2018 have been preparing an RFP for a Space Telecommunications Interface (STI), a joint effort with the Space DTF. | ||
| + | * **CORBA Working Group ** (chartered June 2019) | ||
| + | * Wiki (TBD); maillist: [email protected] | ||
| + | * In the "forming" stage but already working on an RFP to provide "REST for CORBA" | ||
| + | |||
| + | ---- | ||
| - | MARS has three other working groups that are currently __//on hiatus//__. | + | MARS has four other working groups that are currently __//on hiatus//__ . |
| + | * Object Database Technologies ([[Object DB]]) Working Group (chartered September 2003; suspended since March 2009) | ||
| + | * Dynamic Deployment Configuration (DDC) Working Group (chartered September 2010) | ||
| * Software Defined Networks (SDN) Working Group (Chartered March 2013; suspended as of November 2015) | * Software Defined Networks (SDN) Working Group (Chartered March 2013; suspended as of November 2015) | ||
| - | * Dynamic Deployment Configuration (DDC) Working Group (chartered September 2010) | + | * Rich Internet Applications (RIA) Working Group (chartered December 2009; suspended as of September 2016) |
| - | * The Object Database Technologies ([[Object DB]]) Working Group (chartered September 2003; suspended since March 2009) | + | |
| As needed, these WGs can be re-activated as is or re-purposed. Also as needed, new WGs can be created. | As needed, these WGs can be re-activated as is or re-purposed. Also as needed, new WGs can be created. | ||
| - | For more information go to their respective wiki pages. To subscribe to the maillists for each WG, send an email to [email protected] or refer to this site [[http://www.omg.org/members/mailinglists.html | + | For more information go to their respective wiki pages. To subscribe to the maillists for each WG, send an email to [email protected] or refer to this site [[http://www.omg.org/members/mailinglists.html]] |
| - | ]] | + | |
| - | [★] The IDL Profiles Working Group hasn't met formally in a long time and is effectively done. However, it will remain in this list given how well it served its purpose. | ||
| Line 98: | Line 110: | ||
| - | + | ===== Looking Ahead ===== | |
| - | ===== News From Recent TC Meetings (and looking ahead) ===== | + | - Refer to the OMG Technical Meeting Resource Hub for the MARS report which provides more details on the work done in Amsterdam (June 2019) and our plans for the meeting in Nashville, TN (September 2019): [[http://www.omg.org/cgi-bin/doc?mars/2019-06-30]] (OMG member only access). |
| - | - Continuing and new Technology Processes | + | - Use this link to learn what MARS will be working on in Nashville [[https://www.omg.org/events/tn-19/agendas/MARSPTFCalendar.html]]. Note that prior to the 4 week deadline for Nashville, it may just be a unscheduled list of agenda items. |
| - | * //A significant milestone for MARS//! As cited above, the IDL 4.0 RFC has been **adopted** [[http://www.omg.org/cgi-bin/doc?mars/15-03-01]]. IDL 4.0 is the culmination of an idea proposed in 2008: how to make it easier to apply IDL to more domains than just CORBA. The first step was to copy IDL from the CORBA spec and make it stand-alone: IDL 3.5 ([[http://www.omg.org/spec/IDL35/]]). The next step was to define a way to create Profiles of IDL (CORBA, DDS, etc). IDL 4.0 establishes a set of //building blocks// and //annotations// and defines how to use them to construct IDL //profiles//.[[http://www.omg.org/spec/IDL/]] | + | |
| - | * An RFP to to define a gateway between DDS and the OPC UA ([[https://opcfoundation.org/about/opc-technologies/opc-ua/]]) was issued: [[http://www.omg.org/cgi-bin/doc.cgi?mars/2015-9-2]], | + | |
| - | * Three RFPs remain under discussion: one to extend the existing DDS Interoperability protocol to operate in Extremely Constrained Resource Environments (XRCE) and two to expand OMG's arsenal of IDL to language mappings (IDL to Java and IDL to C#). | + | |
| - | - Refer to the OMG Technical Meeting Resource Hub for the MARS report which provides more details on the work done in Cambridge and our plans for the meeting in La Jolla, CA (December 2015): [[http://www.omg.org/cgi-bin/doc?mars/2015-09-18]] (OMG member only access). | + | |
| - | * Our meeting in La Jolla will include reviews of the three new RFPs as well as two revised submissions: IEF Reference Architecture and the Unified Component Model for Distributed Realtime Systems (UCM for DRE). | + | |
| - | - When available, the agenda for the La Jolla meeting will be posted here: http://www.omg.org/news/meetings/tc/agendas/ca-15/MARS.pdf. | + | |
| Line 140: | Line 146: | ||
| As of December 2014, both include a Statistics tab, which contains graphical depictions of the //Cumulative Technology Process State// and //MARS Technology Process State by Year//. Both work with data recorded since November 2002 and are updated after each TC meeting. | As of December 2014, both include a Statistics tab, which contains graphical depictions of the //Cumulative Technology Process State// and //MARS Technology Process State by Year//. Both work with data recorded since November 2002 and are updated after each TC meeting. | ||
| + | |||
| Line 153: | Line 160: | ||
| ===== Useful Links ===== | ===== Useful Links ===== | ||
| - | MARS collaborates with a number of other Task Forces (C4I, Robotics, Systems Assurance, Government) and SIGs (DDS, Telecoms, Ontology). For example: | + | MARS **//collaborates//** with a number of other Task Forces (C4I, Robotics, Systems Assurance, Government) and SIGs (DDS, Telecoms, Ontology, BlockChain). For example: |
| * The IEF WG represents a collaboration between MARS and C4I with as needed involvement of Gov DTF and Ontology PSIG. IEF WG maintains an active dialog with Gov DTF's Info Sharing WG. As needed, the two WGs also meet jointly during the TC meeting week. | * The IEF WG represents a collaboration between MARS and C4I with as needed involvement of Gov DTF and Ontology PSIG. IEF WG maintains an active dialog with Gov DTF's Info Sharing WG. As needed, the two WGs also meet jointly during the TC meeting week. | ||
| - | * DDS PSIG serves as the incubator for the many DDS related technology processes handled by MARS and active in the IDL Profiles WG. | + | * DDS PSIG serves as the incubator for the many DDS related technology processes handled by MARS; its membership is very active in the IDL WG. |
| - | * Any technology processes relating to security (e.g., DDS Security) are developed with input from and in collaboration with the Systems Assurance PTF. | + | * MARS, the BlockChain PSIG, and Finance DTF are collaborating in the area of BlockChain technologies. As appropriate, the products of this collaboration will be formally managed by either MARS or FDTF. Right now, it's mostly MARS. (new since 2018) |
| + | * The Cloud WG is working closely with MARS in order to publish revisions to many of the white papers previously published by the Cloud Standards Customer Council (CSSC). | ||
| + | * Any technology processes relating to security aspects of specifications previously developed by MARS (e.g., DDS Security) are managed by the Systems Assurance PTF but developed in collaboration with MARS. | ||
| - | Links to the respective home pages for these TFs and SIGs are provided below: | + | Links to the respective home pages for these TFs, SIGs, and WGs are provided below: |
| * C4I (Consultation, Command, Control, Communications, and Intelligence) DTF: [[http://c4i.omg.org/]] | * C4I (Consultation, Command, Control, Communications, and Intelligence) DTF: [[http://c4i.omg.org/]] | ||
| Line 165: | Line 174: | ||
| * Systems Assurance PTF: [[http://sysa.omg.org/]] | * Systems Assurance PTF: [[http://sysa.omg.org/]] | ||
| * Government DTF: [[http://gov.omg.org/]] | * Government DTF: [[http://gov.omg.org/]] | ||
| + | * Finance DTF [[http://www.omg.org/fdtf/]] | ||
| * Data Distribution Services (DDS) PSIG: [[http://portals.omg.org/dds/]] | * Data Distribution Services (DDS) PSIG: [[http://portals.omg.org/dds/]] | ||
| * Ontology PSIG: [[http://ontology.omg.org/]] | * Ontology PSIG: [[http://ontology.omg.org/]] | ||
| - | * Telecoms PSIG: [[http://telecom.omg.org/]] | + | * BlockChain PSIG: [[http://www.omg.org/blockchain/]] |
| + | * Cloud WG: [[http://www.omg.org/cloud/]] | ||
| Other links: | Other links: | ||
| Line 175: | Line 185: | ||
| * OMG Technical Meeting Resource Hub, an excellent resource for all Technical Committee (TC) reports and any special event presentations from previous and all past meetings (back to September 2003): [[http://www.omg.org/members/TMResourceHub/]] | * OMG Technical Meeting Resource Hub, an excellent resource for all Technical Committee (TC) reports and any special event presentations from previous and all past meetings (back to September 2003): [[http://www.omg.org/members/TMResourceHub/]] | ||
| - | Note that all these sites, except for the Meeting Resource hub, are __//public sites//__ .. **//no password required to access//**. | + | **//Note://** All these sites, except for the Meeting Resource hub, are __//public sites//__ .. __**//no password required to access//**.__ |
