This is an old revision of the document!


The above is a panorama taken by the MARS Curiosity Rover

Middleware and Related Services (MARS) Platform Task Force (PTF)

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:

  1. 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.
  2. General purpose Pervasive Services that are either:
    • Fundamental for developing useful distributed applications
    • Provide a universal basis for Application Integration and Information Integration, or
    • Support higher-level facilities and frameworks
  3. Mappings for such Pervasive Services to specific middleware platforms, and reference mappings from generic PIM constructs to platform-specific constructs and protocol rules.
  4. Supporting Technologies for Application Integration, Information Integration, and Collaboration

Co-Chairs

Name Charlotte Wales Virginie Watine
Company The MITRE Corporation T H A L E S
Email charwing@mitre.org virginie.watine@fr.thalesgroup.com

Working Groups (WGs)

To paraphrase the MARS home page, MARS hosts a number of WGs, serving 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 4 active working groups at this time [★]:

  • Software Defined Networks (SDN) Working Group (Chartered March 2013)
  • High Performance Embedded Computing (HPEC) Working Group (Chartered March 2012)
    • Two RFCs – for VSIPL and VSIPL++ successfully issued, adopted, and released as formal OMG specs; 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 (Information Exchange Framework (IEF) Working Group) Working Group (Chartered December 2005)
  • Rich Internet Application (RIA) Working Group (Chartered December 2009)
  • IDL Profiles Working Group (Chartered March 2009, nominally disbanded June 2015)
    • 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 coming)
    • 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 is the next topic of discussion.

MARS has two other working groups that are currently on hiatus.

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

[★] 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.

News From Recent TC Meetings (and looking ahead)

  1. Continuing and new Technology Processes
    • 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.
    • Four new RFPs are now on the MARS Roadmmap. One to define a gateway between DDS and the OPC UA (https://opcfoundation.org/about/opc-technologies/opc-ua/), 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#).
  2. Refer to the OMG Technical Meeting Resource Hub for the MARS report which provides more details on the work done in Berlin and our plans for the meeting in Cambridge, MA (September 2015): http://www.omg.org/cgi-bin/doc?mars/2015-06-10 (OMG member only access).
    • Our meeting in Cambridge will include reviews of the four new RFPs as well as three submissions: RIA Dynamic Component Model (RDCM) [initial], IEF Reference Architecture [revised], and the Unified Component Model for Distributed Realtime Systems (UCM for DRE)[revised]. MARS will also be hosting an IEF Information Day.
  3. When available, the agenda for the Cambridge meeting will be posted here: http://www.omg.org/news/meetings/tc/agendas/ma-15/MARS.pdf.

MARS Technology Roadmap

The latest MARS Roadmap can be found at the MARS home page http://mars.omg.org. Two versions are posted:

  • A public version that requires no password to open. It provides links to issued RFPs, RFCs, and RFIs and adopted submissions (adopted during the current and previous year); all material available to the public. Published as a PDF file only.
  • A member's only version that needs a userid and password to access. Published in two formats: an editable Excel file and a nominally non-editable PDF file.

Reproduced below is the OMG technology process as captured in the MARS Roadmap.

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.

MARS collaborates with a number of other Task Forces (C4I, Robotics, Systems Assurance, Government) and SIGs (DDS, Telecoms, Ontology). 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.
  • DDS PSIG serves as the incubator for the many DDS related technology processes handled by MARS and active in the IDL Profiles WG.
  • Any technology processes relating to security (e.g., DDS Security) are developed with input from and in collaboration with the Systems Assurance PTF.

Links to the respective home pages for these TFs and SIGs are provided below:

Other links:

Note that all these sites, except for the Meeting Resource hub, are public sites .. no password required to access.

/usr/local/wiki/mars/private/attic/start.1435682510.txt.gz · Last modified: 2015/06/30 12:41 by charwing
Back to top
OMG Home Logos and Trademarks Become a Member Become a Sponsor Upcoming TC Meeting TOP