|AllJoyn Certification Matrix|
|AllJoyn Core Version||Required Services|
|15.04.00||- Deprecated for security -|
|15.04.00a||- Deprecated for security -|
Key: ABI – Active and accepted into the Base Implementation, CR – Candidate for review into the Base Implementation, RBI – Retired from the Active Base Implementation, R – released and under review for inclusion in the Base Implementation, U – unreleased, ✔ - available required service, ✖ - service not applicable, Z – Zip file, S – Source code, N – release notes.
- 16.04 Standard Client and 16.04 Thin Client were approved by the TSC and sent to the Board of Directors for the official 30 day review on 03 May 2016.
- 15.09 Base Services were approved by the TSC and sent to the Board of Directors for the official 30 day review on 08 December 2015.
- 15.09 Standard Client and 15.09 Thin Client were approved by the TSC and sent to the Board of Directors for the official 30 day review on 30 September 2015.
- 15.04 Lighting Service Framework was approved by the TSC and sent to the Board of Directors for the official 30 day review on 10 November 2015.
- 15.04 Core + Base Services;15.04 Core + Base Services is now an official and approved Base Implementation. The initial 30 day review of 15.04 Core and Base Services commenced on 9 June 2015 and closed on Thursday, 9 July, 2015 at midnight Pacific time. 15.04 Core - released 29 April 2015 and accepted by the TSC on May 4 2015. 15.04 Base Services - released 8 June 2015, approved by the TSC on 9 June 2015.
- 15.04 Gateway Agent - the Gateway Agent project has not released version 15.04 of the Gateway Agent.
- 15.04 Lighting Service Framework - the Lighting Service Framework project has not released version 15.04 of the Lighting Service Framework.
- 14.12 Core + Base Services - 14.12 Core + Base Services is now an official and approved Base Implementation. The initial 90 day review of 14.12 Core and Base Services commenced on 27 February 2015 with the release of 14.12 Base Services. The 90 day review period for 14.12 Core and Base Services officially closed on Thursday, 28 May, 2015 at midnight Pacific time.
- 14.12 Gateway Agent is an official component of the Base Implementation- The Gateway Agent project released version 14.12 of the Gateway Agent on 19 April 2015. It was presented to the TSC on 20 April 2015 and unanimously approved. The Alliance Board was notified on 21 April 2015 that this Base Implementation component was accepted. The 90 day review period completed on 20 July 2015 at midnight PST.
- 14.12 Lighting Service Framework is an official component of the Base Implementation - The Lighting Service Framework project released version 14.12 of the Lighting Service Framework on 19 April 2015. It was presented to the TSC on 20 April 2015 and unanimously approved. The Alliance Board was notified on 21 April 2015 that this Base Implementation component was accepted. The 90 day review period completed on 20 July 2015 at midnight PST.
What is the Base Implementation? It is the official code base of AllJoyn that can be used for certification. The Base Implementation includes the "Core" and several "Required Services". The AllJoyn Framework Core delivers the fundamental AllJoyn protocol, Required Services deliver additional functionality on top of the AllJoyn Core. The Base Implementation is formally defined in the IP Policy .
How did the initial Base Implementations get created? The initial Base Implementation was created when it was nominated and approved by a vote of the TSC.
What is in the initial Base Implementation? Nine approved elements of Alliance code were included in the initial Base Implementation: 14.12 Core thin client, 14.12 Core standard client, 14.12 standard client routing service, 14.12 notification, configuration, control panel, onboarding, 14.12 lamp service, 14.12 lighting controller service, 14.12 gateway service. The components proposed for the initial AllJoyn Base Implementation were subject to a 90 day review.
How is versioning handled in the Base Implementation? A new release of AllJoyn is started with the release of the AllJoyn Core (Standard and Thin Client) which triggers a new version of the Base Implementation. Alliance code for required services included in the new release may version with the AllJoyn framework (but they do not necessarily have to). Each element of versioned AllJoyn Code for a new release of the AllJoyn - Core and Required Services- that is already part of the Base Implementation is reviewed by the TSC and the Board of Directors (process below) and if there are no objections, this versioned Core or Required Service becomes part of the Base Implementation.
What is the process for reviewing and accepting versioned components of the Base Implementation? When a versioned element of the Base Implementation is released (via its containing project), the Technical Steering Committee (TSC) is notified that a release candidate for Core or Required Services is available. The Interface Review Board, Security Review Board and Compliance and Certification Committee review the release to ensure that the release candidate meets their respective criteria, and if the release candidate successfully passes these reviews, the release candidate is sent to the full TSC for review. The TSC votes to accept or reject the release candidate for inclusion in the Base Implementation. If approved by the TSC, the TSC chair notifies the Board that specific versioned elements have been released and are now under review for inclusion into a specific version of the Base Implementation. On notification to the Board, the clock starts on the Board's Base Implementation review period of 30 days as specified in the IP Policy . Upon successful completion of review, the release candidate becomes an official part of the Base Implementation (at the specified version level), the Compliance page is updated, and the TSC mailing list is notified.
( review_process_for_updates_to_existing_elements_of_the_cbi.pdf )
What is the process for adding new Required Services to the Base Implementation? When a project believes that a new element of AllJoyn Code is ready for inclusion in the Base Implementation as a NEW Required Service, the project petitions the Technical Steering Committee for Foundational Status for the proposed new Required Service, presenting a release candidate for the Required Service. When applying for Foundational Status for a new Required Service, the project must indicate which starting version and potentially which subsequent version(s) of the Base Implementation that the new Required Service should be included in. If granted Foundational Status, the element of AllJoyn code will become a Required Service included in the Base Implementation at the specific version(s) of the Base Implementation indicated. The TSC reviews the released candidate 1) for its merits for inclusion into the Base Implementation and 2) per the steps outlined above in " reviewing and accepting versioned components of the Base Implementation ". Based on these the TSC will vote to accept/reject the petition for Foundational Status. If accepted by the TSC, the TSC chair notifies the Board that a new Foundational Status Required Service has been proposed to and accepted by the TSC for inclusion into the Base Implementation. The Board must vote to accept or reject the TSC's recommendation. If the Board accepts the TSC's recommendation, the NEW Required Service is added to the official Base Implementation, the matrix on the Compliance page is updated accordingly and the clock starts on the 30 day Base Implementation review process . Upon successful completion of the review, the candidate becomes an official Required Service of the Base Implementation (at its version(s), the Compliance page is updated, and the TSC mailing list is notified.
How long is the review period for a versioned and new candidate component of the Base Implementation? Per the IP Policy , the initial (14.12) Base Implementation has a 90 day review period for all components. All other versions of the Base Implementation have a 30 day review period for each component.
Are there ever exceptions to the AllJoyn Certification Matrix? Yes. In situations where a need arises to request an exception, an applicant may request a waiver (see certification guide for the waiver process). The Alliance will review the request and process the waiver under reasonable circumstances. Waivers are typically granted when there is a justifiable reason for the exception and when the granting of the exception would not undermine the integrity of the certification program.