EVP.json

{
    "name": "OMA Enabler Validation Plan",
    "abbreviation": "EVP",
    "data": {
      "resources": [
        {
            "name": "README",
            "resourceType": "Overview",
            "url": "README.txt"
        },
        {
            "name": "Search",
            "resourceType": "API",
            "url": "http://www.openmobilealliance.org/xxx/"
        },
        {
          "name": "Bugs",
          "resourceType": "Issue",
          "url": "mailto:helpdesk@omaorg.org?subject=Feedback"
      }
      ],
      "publications": [
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-ETS-LightweightM2M-V1_0-20151208-C.pdf",
          "file": "OMA-ETS-LightweightM2M-V1_0-20151208-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2015-12-08",
          "contentMediaType": "application/pdf",
          "description": "This document describes in detail available test cases for LightweigthM2M as specified in OMA-TS-LightweightM2M-V1_0. The test cases are split in two categories, conformance and interoperability test cases. The conformance test cases are aimed to verify the adherence to normative requirements described in the technical specifications. The interoperability test cases are aimed to verify that implementations of the specifications work satisfactory. If either conformance or interoperability tests do not exists at the creation of the test specification this part should be marked not available."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-ETS-WMLS-V1_0-20041118-A.pdf",
          "file": "OMA-ETS-WMLS-V1_0-20041118-A.pdf",
          "status": "Approved",
          "version": "V1.0",
          "date": "2004-11-18",
          "contentMediaType": "application/pdf",
          "description": "This document describes test cases for OMA WMLS version 28 September 2001."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-Autho4API-V1_0-20140513-C.pdf",
          "file": "OMA-EVP-Autho4API-V1_0-20140513-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2014-05-13",
          "contentMediaType": "application/pdf",
          "description": ""
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-BCAST-V1_0-20070807-C.pdf",
          "file": "OMA-EVP-BCAST-V1_0-20070807-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2007-08-07",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the BCAST 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the BCAST 1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR). While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan. This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     None 1.2     Exclusions     None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-BCAST-V1_0-20071019-C.pdf",
          "file": "OMA-EVP-BCAST-V1_0-20071019-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2007-10-19",
          "contentMediaType": "application/pdf",
          "description": ""
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-BCAST-V1_0-20080128-C.pdf",
          "file": "OMA-EVP-BCAST-V1_0-20080128-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2008-01-28",
          "contentMediaType": "application/pdf",
          "description": ""
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-BCAST-V1_0-20080226-C.pdf",
          "file": "OMA-EVP-BCAST-V1_0-20080226-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2008-02-26",
          "contentMediaType": "application/pdf",
          "description": ""
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-BCAST-V1_0-20080423-C.pdf",
          "file": "OMA-EVP-BCAST-V1_0-20080423-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2008-04-23",
          "contentMediaType": "application/pdf",
          "description": ""
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-BCAST-V1_0-20080724-C.pdf",
          "file": "OMA-EVP-BCAST-V1_0-20080724-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2008-07-24",
          "contentMediaType": "application/pdf",
          "description": ""
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-BCAST-V1_0-20081014-C.pdf",
          "file": "OMA-EVP-BCAST-V1_0-20081014-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2008-10-14",
          "contentMediaType": "application/pdf",
          "description": ""
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-BCAST-V1_0-20081202-C.pdf",
          "file": "OMA-EVP-BCAST-V1_0-20081202-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2008-12-02",
          "contentMediaType": "application/pdf",
          "description": ""
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-BCAST-V1_0-20090331-A.pdf",
          "file": "OMA-EVP-BCAST-V1_0-20090331-A.pdf",
          "status": "Approved",
          "version": "V1.0",
          "date": "2009-03-31",
          "contentMediaType": "application/pdf",
          "description": ""
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-BCAST-V1_1-20101207-C.pdf",
          "file": "OMA-EVP-BCAST-V1_1-20101207-C.pdf",
          "status": "Candidate",
          "version": "V1.1",
          "date": "2010-12-07",
          "contentMediaType": "application/pdf",
          "description": ""
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-Browsing-V2_3-20080331-C.pdf",
          "file": "OMA-EVP-Browsing-V2_3-20080331-C.pdf",
          "status": "Candidate",
          "version": "V2.3",
          "date": "2008-03-31",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Browsing 2.3 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the Browsing Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of Browsing 2.3, as stated in [ERELD] and [ETR] is according to the following: •“WAE Media Types” [WAEMedia] •”XHTML Mobile Profile Version 1.1”[XHTMLMP] •”XHTML Mobile Profile Version 1.0” [XHTMLMP10] •”Wireless Markup Language Version 1.3” [WML1] •”Wireless Markup Language Version 2.0” [WML2] •“ECMAScript Mobile Profile Version 1.0” [ESMP] •“WMLScript Language” [WMLScript] •“WMLScript Standard Libraries” [WMLStdLib] •“WAP Cascading Style Sheet” [WCSS] •“User Agent Caching Model” [CacheMod] •“HTTP State Management” [HTTPSM] •“Wireless Binary eXtended Markup Language” [WBXML] •”WMLScript Crypto Library” [CryptoLib] 1.1     Assumptions     None. 1.2     Exclusions     None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-Browsing-V2_3-20090213-A.pdf",
          "file": "OMA-EVP-Browsing-V2_3-20090213-A.pdf",
          "status": "Approved",
          "version": "V2.3",
          "date": "2009-02-13",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Browsing 2.3 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the Browsing Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of Browsing 2.3, as stated in [ERELD] and [ETR] is according to the following: •“WAE Media Types” [WAEMedia] •”XHTML Mobile Profile Version 1.1”[XHTMLMP] •”XHTML Mobile Profile Version 1.0” [XHTMLMP10] •”Wireless Markup Language Version 1.3” [WML1] •”Wireless Markup Language Version 2.0” [WML2] •“ECMAScript Mobile Profile Version 1.0” [ESMP] •“WMLScript Language” [WMLScript] •“WMLScript Standard Libraries” [WMLStdLib] •“WAP Cascading Style Sheet” [WCSS] •“User Agent Caching Model” [CacheMod] •“HTTP State Management” [HTTPSM] •“Wireless Binary eXtended Markup Language” [WBXML] •”WMLScript Crypto Library” [CryptoLib] 1.1     Assumptions     None. 1.2     Exclusions     None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-Browsing-V2_4-20100323-C.pdf",
          "file": "OMA-EVP-Browsing-V2_4-20100323-C.pdf",
          "status": "Candidate",
          "version": "V2.4",
          "date": "2010-03-23",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Browsing 2.4 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the Browsing 2.4 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR) for the same version.  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of Browsing 2.4, as stated in [ERELD] is according to the following: • User Agent Caching Model V1.1 • WMLScript Crypto Library  • ECMA Script Mobile Profile V1.1 • HTTP State Management Specification 1.1 • Mobile Application Environment Specification V2.4 • WAP Pictogram Specification, Version 1.1 • Wireless Application Environment Defined Media Type Specification • Wireless Binary eXtended Markup Language • CSS Specification V1.2 • WAP Wireless Markup Language Version 1.3 • WML Specification Information Note 102 • WML Specification Information Note 104 • WML Specification Information Note 105 • Wireless Mark up Language version 2.0 • Wireless Markup Language Script Specification • WML Specification Information Note 101 • Wireless Markup Language Script Standard Libraries Specification • Wireless Markup Language Script Standard Libraries Specification Information Note 103 • HTTP State Management Specification V1.3 As stated in the [ETR], the differences between version 2.3 and 2.4 are: • XHTML MP 1.3 for converged release • WCSS 1.2 for converged release • ESMP 1.1 for converged release • MAEspec24 for restructuring WAEspec23 This EVP is focused on how to validate the additions made to the Browsing 2.4 specifications, inline with the request made on the [ETR]."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-Charging-V1_0-20070508-C.pdf",
          "file": "OMA-EVP-Charging-V1_0-20070508-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2007-05-08",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Charging 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the Charging 1.0 Enabler Release specifications is based on expected testing expectations in the Enabler Test Requirements (ETR)."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-CPNS-V1_0-20120313-C.pdf",
          "file": "OMA-EVP-CPNS-V1_0-20120313-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2012-03-13",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the CPNS v1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the CPNS v1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions None. 1.2     Exclusions None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-DCD-V1_0-20090714-C.pdf",
          "file": "OMA-EVP-DCD-V1_0-20090714-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2009-07-14",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Dynamic Content Delivery Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the Dynamic Content Delivery Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     None so far. 1.2     Exclusions     None so far."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-DCMO-V1_0-20090915-C.pdf",
          "file": "OMA-EVP-DCMO-V1_0-20090915-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2009-09-15",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the DM DCMO 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the DM DCMO 1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     None. 1.2     Exclusions     None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-DiagMon-V1_1-20120110-C.pdf",
          "file": "OMA-EVP-DiagMon-V1_1-20120110-C.pdf",
          "status": "Candidate",
          "version": "V1.1",
          "date": "2012-01-10",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the DiagMon V1.1 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the DiagMon V1.1 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1 Assumptions None. 1.2 Exclusions None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-DLOTA-V2_0-20080331-C.pdf",
          "file": "OMA-EVP-DLOTA-V2_0-20080331-C.pdf",
          "status": "Candidate",
          "version": "V2.0",
          "date": "2008-03-31",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the DLOTA 2.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the DLOTA 2.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     None. 1.2     Exclusions     None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-DM-V1_3-20151208-C.pdf",
          "file": "OMA-EVP-DM-V1_3-20151208-C.pdf",
          "status": "Candidate",
          "version": "V1.3",
          "date": "2015-12-08",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the DM V1.3 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status. The validation plan for the DM V1.3 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1 Assumptions None. 1.2 Exclusions None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-DM_SC-V1_0-20111018-C.pdf",
          "file": "OMA-EVP-DM_SC-V1_0-20111018-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2011-10-18",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the OMA DM Smart Card v1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the OMA DM Smart Card v1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR) [DMSCETR].  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) [DMSCETS] the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1 Assumptions As this enabler re-uses DM 1.2 and SCWS 1.1 it is assumed that products participating to formal OMA Test Fests or Bi-Lateral Testing are fully compliant with these enablers, and have passed the corresponding Conformance Testing. 1.2 Exclusions None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-DPE-V1_0-20100629-C.pdf",
          "file": "OMA-EVP-DPE-V1_0-20100629-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2010-06-29",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Device Profile Evolution Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the Device Profile Evolution Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1   Assumptions None so far. 1.2   Exclusions None so far."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-DRM-V2_1-20070807-C.pdf",
          "file": "OMA-EVP-DRM-V2_1-20070807-C.pdf",
          "status": "Candidate",
          "version": "V2.1",
          "date": "2007-08-07",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the DRM 2.1 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the DRM 2.1 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of DRM 2.1, as stated in [ERELD] is according to the following: -DRM Requirements V2.1 [DRMREQ-v2.1] -DRM Architecture V2.1 [DRMARCH-v2.1] -DRM Specification V2.1 [DRM-v2.1] -DRM Rights Expression Language V2.1 [DRMREL-v2,1] -DRM Content Format V2.1 [DRMCF-v2,1] -DRM ROAP schema V2.1 [DRMROAPXSD-v2.1] In addition to the mentioned specifications comprising the DRM V2.1 enabler a data dictionary (DTD) for the Rights Expression Language as defined in [DRMREL-v2.1], Section 6.2. 1.1     Assumptions     None 1.2     Exclusions     None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-DRM-V2_1-20070831-C.pdf",
          "file": "OMA-EVP-DRM-V2_1-20070831-C.pdf",
          "status": "Candidate",
          "version": "V2.1",
          "date": "2007-08-31",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the DRM 2.1 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the DRM 2.1 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of DRM 2.1, as stated in [ERELD] is according to the following: -DRM Requirements V2.1 [DRMREQ-v2.1] -DRM Architecture V2.1 [DRMARCH-v2.1] -DRM Specification V2.1 [DRM-v2.1] -DRM Rights Expression Language V2.1 [DRMREL-v2,1] -DRM Content Format V2.1 [DRMCF-v2,1] -DRM ROAP schema V2.1 [DRMROAPXSD-v2.1] In addition to the mentioned specifications comprising the DRM V2.1 enabler a data dictionary (DTD) for the Rights Expression Language as defined in [DRMREL-v2.1], Section 6.2. 1.1     Assumptions     None 1.2     Exclusions     None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-DRM-V2_1-20090213-A.pdf",
          "file": "OMA-EVP-DRM-V2_1-20090213-A.pdf",
          "status": "Approved",
          "version": "V2.1",
          "date": "2009-02-13",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the DRM 2.1 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the DRM 2.1 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of DRM 2.1, as stated in [ERELD] is according to the following: -DRM Requirements V2.1 [DRMREQ-v2.1] -DRM Architecture V2.1 [DRMARCH-v2.1] -DRM Specification V2.1 [DRM-v2.1] -DRM Rights Expression Language V2.1 [DRMREL-v2,1] -DRM Content Format V2.1 [DRMCF-v2,1] -DRM ROAP schema V2.1 [DRMROAPXSD-v2.1] In addition to the mentioned specifications comprising the DRM V2.1 enabler a data dictionary (DTD) for the Rights Expression Language as defined in [DRMREL-v2.1], Section 6.2. 1.1     Assumptions     None 1.2     Exclusions     None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-DRM-V2_2-20111206-C.pdf",
          "file": "OMA-EVP-DRM-V2_2-20111206-C.pdf",
          "status": "Candidate",
          "version": "V2.2",
          "date": "2011-12-06",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the DRM 2.2 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the DRM 2.2 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR). While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of DRM 2.2, as stated in [ERELD] is according to the following: - DRM Requirements V2.2 [DRMREQ-v2.2] - DRM Architecture V2.2 [DRMARCH-v2.2] - DRM Specification V2.2 [DRM-v2.2] - DRM Rights Expression Language V2.2 [DRMREL-v2.2] - DRM Content Format V2.2 [DRMCF-v2.2] - DRM ROAP Schema V2.2 [DRMROAPXSD-v2.2] In addition to the mentioned specifications comprising the DRM V2.2 enabler a data dictionary (DTD) for the Rights Expression Language as defined in [DRMREL-v2.2], Section 6.2. 1.1 Assumptions None 1.2 Exclusions None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-LightweightM2M-V1_0-20140819-C.pdf",
          "file": "OMA-EVP-LightweightM2M-V1_0-20140819-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2014-08-19",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Lightweight M2M V1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the Lightweight M2M V1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1 Assumptions None. 1.2 Exclusions None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-MC-V1_0-20120313-C.pdf",
          "file": "OMA-EVP-MC-V1_0-20120313-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2012-03-13",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Mobile Codes V1.0 Candidate Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the Mobile Codes V1.0 Candidate Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions The following aspects pertaining to the validation of the MC V1.0 CER though IOP Testing are in-scope: • Testing of Indirect Codes. • Behaviours of the MC Client, Home CMP, Remote (Resolving) CMP. • Behaviour of the MC Registry, where applicable. • MC Client code scanning analytics Tracking & Reporting, where applicable.   1.2     Exclusions The following aspects pertaining to the validation of the MC V1.0 CER though IOP Testing are out-of-scope: • Testing of Direct Codes. • Latency performance aspects of interactions between the MC Client and CMP, CMP to CMP and CMP to MC Registry as part of the Code Resolution applicable to Indirect Codes testing. • Secure IP data connections are assumed for messaging communications between CMP to CMP and, where applicable, CMP to MCR; however, the manner in which such connections are furnished is implementation specific and not the focus of the Enabler functionality testing. • U/I mechanism or format for communicating notifications received or generated by the MC Client to the end user is implementation specific and not the focus of the Enabler functionality testing. • Consumption of the result (i.e. information or content returned) by the device applications after Code Resolution by the MC Client."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-Presence_SIMPLE-V2_0-20100727-C.pdf",
          "file": "OMA-EVP-Presence_SIMPLE-V2_0-20100727-C.pdf",
          "status": "Candidate",
          "version": "V2.0",
          "date": "2010-07-27",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Presence 2.0 Enabler Release. The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the Presence 2.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1   Assumptions None 1.2   Exclusions None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-Push-V2_2-20071106-C.pdf",
          "file": "OMA-EVP-Push-V2_2-20071106-C.pdf",
          "status": "Candidate",
          "version": "V2.2",
          "date": "2007-11-06",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Push V2.2 Enabler Release.  The successful accomplishment of the validation activities  will be required for the Enabler to be considered for Approved status.  The validation plan for the push Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of Push 2.2, as stated in [ERELD] and [ETR] is according to the following: •Push Architecture Wap 250- PushArchOverview •Push Message Wap 251- Push Message •Push PAP OMA-WAP-TS-PAP_V2_2 •Push OTA OMA-WAP-TS-PushOTA-V2-2  1.1     Assumptions     NONE  1.2     Exclusions     NONE"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-Push-V2_2-20100727-C.pdf",
          "file": "OMA-EVP-Push-V2_2-20100727-C.pdf",
          "status": "Candidate",
          "version": "V2.2",
          "date": "2010-07-27",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Push V2.2 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the Push V2.2 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of Push 2.2, as stated in [ERELD] and [ETR] is according to the following: • Push Architecture OMA-AD-Push-V2_2 • Push Message OMA-TS-Push_Message-V2_2 • Push PAP OMA-TS-PAP-V2_2 • Push OTA OMA-TS-PushOTA-V2_2 • PPG Service OMA-TS-PPGService-V2_2 • Push Client-Application Interface OMA-TS-PushCAI-V1_0 • Push Management Object OMA-TS-Push_MO-V1_0  1.1   Assumptions NONE  1.2   Exclusions NONE"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-REST_NetAPI_Push-V1_0-20130813-C.pdf",
          "file": "OMA-EVP-REST_NetAPI_Push-V1_0-20130813-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2013-08-13",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the RESTful Network API for OMA Push V1.0 Enabler Release (PushREST 1.0).  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for PushREST 1.0 specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of PushREST 1.0, as stated in [ERELD] and [ETR] is according to the following:  RESTful Network API for OMA Push V1.0 Technical Specification OMA-TS-REST_NetAPI_Push-V1_0 [PushREST-TS]  1.1 Assumptions NONE  1.2 Exclusions NONE"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-REST_NetAPI_Push-V1_0-20130910-C.pdf",
          "file": "OMA-EVP-REST_NetAPI_Push-V1_0-20130910-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2013-09-10",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the RESTful Network API for OMA Push V1.0 Enabler Release (PushREST 1.0).  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for PushREST 1.0 specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of PushREST 1.0, as stated in [ERELD] and [ETR] is according to the following:  RESTful Network API for OMA Push V1.0 Technical Specification OMA-TS-REST_NetAPI_Push-V1_0 [PushREST-TS]  1.1 Assumptions NONE  1.2 Exclusions NONE"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-SCOMO-V1_0-20100406-C.pdf",
          "file": "OMA-EVP-SCOMO-V1_0-20100406-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2010-04-06",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Software Component Management Object 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the 1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1   Assumptions None 1.2   Exclusions None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-SIMPLE_IM-V1_0-20090120-C.pdf",
          "file": "OMA-EVP-SIMPLE_IM-V1_0-20090120-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2009-01-20",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation Plan for the SIMPLE IM 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The Validation Plan for the SIMPLE IM 1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS), the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     None. 1.2     Exclusions     None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-SIMPLE_IM-V1_0-20090904-C.pdf",
          "file": "OMA-EVP-SIMPLE_IM-V1_0-20090904-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2009-09-04",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation Plan for the SIMPLE IM 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The Validation Plan for the SIMPLE IM 1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS), the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     None. 1.2     Exclusions     None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-Smartcard_Web_Server-V1_0-20071106-C.pdf",
          "file": "OMA-EVP-Smartcard_Web_Server-V1_0-20071106-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2007-11-06",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Smartcard-Web-Server 1.0 Enabler Release.  The successful accomplishment of the validation activities  will be required for the Enabler to be considered for Approved status.  The validation plan for the Smartcard-Web-Server 1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     None. 1.2     Exclusions     None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-Smartcard_Web_Server-V1_0-20090213-A.pdf",
          "file": "OMA-EVP-Smartcard_Web_Server-V1_0-20090213-A.pdf",
          "status": "Approved",
          "version": "V1.0",
          "date": "2009-02-13",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Smartcard-Web-Server 1.0 Enabler Release.  The successful accomplishment of the validation activities  will be required for the Enabler to be considered for Approved status.  The validation plan for the Smartcard-Web-Server 1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     None. 1.2     Exclusions     None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-Smartcard_Web_Server-V1_1-20081024-C.pdf",
          "file": "OMA-EVP-Smartcard_Web_Server-V1_1-20081024-C.pdf",
          "status": "Candidate",
          "version": "V1.1",
          "date": "2008-10-24",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Smartcard-Web-Server 1.1 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the Smartcard-Web-Server 1.1 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     None. 1.2     Exclusions     None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-Smartcard_Web_Server-V1_1-20090512-A.pdf",
          "file": "OMA-EVP-Smartcard_Web_Server-V1_1-20090512-A.pdf",
          "status": "Approved",
          "version": "V1.1",
          "date": "2009-05-12",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Smartcard-Web-Server 1.1 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the Smartcard-Web-Server 1.1 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions None. 1.2     Exclusions None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-Smartcard_Web_Server-V1_2-20111011-C.pdf",
          "file": "OMA-EVP-Smartcard_Web_Server-V1_2-20111011-C.pdf",
          "status": "Candidate",
          "version": "V1.2",
          "date": "2011-10-11",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Smartcard Web Server 1.2 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the Smartcard Web Server 1.2 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1 Assumptions None 1.2 Exclusions None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-SNeW-V1_0-20130917-C.pdf",
          "file": "OMA-EVP-SNeW-V1_0-20130917-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2013-09-17",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Social Network Web Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the Social Network Web Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1 Assumptions None. 1.2 Exclusions None."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-SRM-V1_0-20080428-C.pdf",
          "file": "OMA-EVP-SRM-V1_0-20080428-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2008-04-28",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the SRM 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the SRM 1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of SRM 1.0, as stated in [ERELD] is according to the following: -SRM Requirements V1.0 [SRM-RD] -SRM Architecture V1.0 [SRM-AD] -SRM Specification V1.0 [SRM-TS] -DRM Specification V2.0 [OMADRMv2] -DRM Specification V2.1 [OMADRMv2.1]  1.1     Assumptions     None 1.2     Exclusions     None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-SRM-V1_0-20080930-C.pdf",
          "file": "OMA-EVP-SRM-V1_0-20080930-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2008-09-30",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the SRM 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the SRM 1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of SRM 1.0, as stated in [ERELD] is according to the following: -SRM Requirements V1.0 [SRM-RD] -SRM Architecture V1.0 [SRM-AD] -SRM Specification V1.0 [SRM-TS] -DRM Specification V2.0 [OMADRMv2] -DRM Specification V2.1 [OMADRMv2.1]  1.1     Assumptions     None 1.2     Exclusions     None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-SRM-V1_0-20081106-C.pdf",
          "file": "OMA-EVP-SRM-V1_0-20081106-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2008-11-06",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the SRM 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the SRM 1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of SRM 1.0, as stated in [ERELD] is according to the following: -SRM Requirements V1.0 [SRM-RD] -SRM Architecture V1.0 [SRM-AD] -SRM Specification V1.0 [SRM-TS] -DRM Specification V2.0 [OMADRMv2] -DRM Specification V2.1 [OMADRMv2.1] 1.1     Assumptions     None 1.2     Exclusions     None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-SRM-V1_0-20090310-A.pdf",
          "file": "OMA-EVP-SRM-V1_0-20090310-A.pdf",
          "status": "Approved",
          "version": "V1.0",
          "date": "2009-03-10",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the SRM 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the SRM 1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of SRM 1.0, as stated in [ERELD] is according to the following: -SRM Requirements V1.0 [SRM-RD] -SRM Architecture V1.0 [SRM-AD] -SRM Specification V1.0 [SRM-TS] -DRM Specification V2.0 [OMADRMv2] -DRM Specification V2.1 [OMADRMv2.1] 1.1     Assumptions     None 1.2     Exclusions     None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-SUPL-V2_0-20090818-C.pdf",
          "file": "OMA-EVP-SUPL-V2_0-20090818-C.pdf",
          "status": "Candidate",
          "version": "V2.0",
          "date": "2009-08-18",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the SUPL 2.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the 2.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     None 1.2     Exclusions     None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-SVG-V1_0-20080428-C.pdf",
          "file": "OMA-EVP-SVG-V1_0-20080428-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2008-04-28",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the SVG 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the SVG1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     The test programme for SVG 1.0 validation utilizes heavily the W3C SVG Tiny 1.2 test suite. The assumption is that this test suite and the accompanying test harness are publicly available. 1.2     Exclusions     N/A"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-SVG-V1_0-20081014-C.pdf",
          "file": "OMA-EVP-SVG-V1_0-20081014-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2008-10-14",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the SVG 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the SVG1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     The test programme for SVG 1.0 validation utilizes heavily the W3C SVG Tiny 1.2 test suite. The assumption is that this test suite and the accompanying test harness are publicly available. 1.2     Exclusions     N/A"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-SVG-V1_0-20090317-A.pdf",
          "file": "OMA-EVP-SVG-V1_0-20090317-A.pdf",
          "status": "Approved",
          "version": "V1.0",
          "date": "2009-03-17",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the SVG 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the SVG1.0 Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     The test programme for SVG 1.0 validation utilizes heavily the W3C SVG Tiny 1.2 test suite. The assumption is that this test suite and the accompanying test harness are publicly available. 1.2     Exclusions     N/A"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-URI_Schemes-V1_0-20080331-C.pdf",
          "file": "OMA-EVP-URI_Schemes-V1_0-20080331-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2008-03-31",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the URI Schemes 1.0 Enabler Release.  The successful accomplishment of the validation activities is usually required for the Enabler to be considered for Approved status. However for the specific case of this enabler IOP BRO thinks there is no need and feasibility for an interoperability validation. The validation plan for the URI Schemes 1.0 Enabler Release specifications is usually based on testing expectations in the Enabler Test Requirements (ETR).  However this document tries to justify that there is no interoperability in URI Schemes 1.0 making the IOP validation not applicable. 1.1     Assumptions     None 1.2     Exclusions     None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-vObject-V1_0-20070807-C.pdf",
          "file": "OMA-EVP-vObject-V1_0-20070807-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2007-08-07",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the vObject 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the vObject Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     None 1.2     Exclusions     None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-vObject-V1_0-20090213-A.pdf",
          "file": "OMA-EVP-vObject-V1_0-20090213-A.pdf",
          "status": "Approved",
          "version": "V1.0",
          "date": "2009-02-13",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the vObject 1.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the vObject Enabler Release specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. 1.1     Assumptions     None 1.2     Exclusions     None"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-WRAPI-V1_0-20131008-C.pdf",
          "file": "OMA-EVP-WRAPI-V1_0-20131008-C.pdf",
          "status": "Candidate",
          "version": "V1.0",
          "date": "2013-10-08",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the Web Runtime API V1.0 Enabler Release (WRAPI 1.0).  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for WRAPI 1.0 specifications is based on testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of WRAPI 1.0, as stated in [ERELD] and [ETR] is according to the following:  OMA-TS-WRAPI_Push-V1_0 [WRAPI-Push]  OMA-TS-WRAPI_Design_Patterns-V1_0  [WRAPI-Patterns]  1.1 Assumptions NONE  1.2 Exclusions NONE"
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/OMA-EVP-XDM-V2_0-20090818-C.pdf",
          "file": "OMA-EVP-XDM-V2_0-20090818-C.pdf",
          "status": "Candidate",
          "version": "V2.0",
          "date": "2009-08-18",
          "contentMediaType": "application/pdf",
          "description": "This document details the Validation plan for the XDM V2.0 Enabler Release.  The successful accomplishment of the validation activities will be required for the Enabler to be considered for Approved status.  The validation plan for the XDM V2.0 Enabler Release specifications is based on expected testing expectations in the Enabler Test Requirements (ETR).  While the specific test activities to be performed are described in the Enabler Test Specification (ETS) the test environment is described in this plan.  This test environment details infrastructure, operational and participation requirements identified for the needed testing activities. The list of specifications, defining the scope of XDM V2.0, as stated in [ERELD_XDMv2] is according the following: -XDM V2.0 Requirements [XDMv2_RD] -XDM V2.0 Architecture [XDMv2_AD] -XDM V2.0 Specification [XDMv2_Core] -XDM V2.0 Management Object [XDMv2_MO] -XDM V1.0 Shared Group [XDMv1_ Group] -XDM V2.0 Shared List [XDMv2_ List] -XDM V1.0 Shared Policy [XDMv1_ Policy] -XDM V1.0 Shared Profile [XDMv1_ Profile] In  addition  to  the  mentioned  specifications  comprising  the  XDM  V2.0  enabler,  a  data  dictionary  (DTD)  is  defined  in  [ERELD_XDMv2], Section 5 (Supporting Files). Interoperability of XDM Enabler is tested based on the latest available XDM INT ETS, and also on XDM V1.0 INT ETS documents. Note that since the OMA XDM test tool is not available at this time, the document specifies the interoperability aspects only. 1.1     Assumptions     The XDM enabler will always be tested with other Enablers, e.g., with PoC, or SIMPLE IM. It is also assumed that XDM V2.0 implementations are backwards compatible in the sense they implement XDM V1.0 mandatory requirements. 1.2     Exclusions     Since XDM test tool is not currently available, it should be noted that it is expected that OMA Trusted Zone will determine participating teams’ readiness by evaluating pre-testing results. Pre-testing is performed during the first day of the TestFest event. Test cases to be performed during pre-testing, as well as logistical guidance for Trusted Zone are presented in Section 5.3.1."
        },
        {
          "url": "http://www.openmobilealliance.org/release/EVP/README.txt",
          "file": "README.txt",
          "status": "",
          "version": "",
          "date": "",
          "contentMediaType": "text/plain"
        }
      ]
    }
  }