<?xml version="1.0" encoding="UTF-8"?>
<!-- Pieter Kasselman (Betrusted) -->
<xs:schema targetNamespace="urn:oasis:names:tc:dss:1.0:profiles:codesigning:1.0:J2ME:1.0" 
                    xmlns:xs="http://www.w3.org/2001/XMLSchema" 
                    xmlns:ds="http://www.w3.org/2000/09/xmldsig#" 
                    xmlns:dss="urn:oasis:names:tc:dss:1.0:core:schema" 
                    xmlns:async="urn:oasis:names:tc:dss:1.0:profiles:asynchronousprocessing:1.0" 
                    xmlns:dsscs="urn:oasis:names:tc:dss:1.0:profiles:codesigning:1.0" 
                    xmlns:dsscsj2me="urn:oasis:names:tc:dss:1.0:profiles:codesigning:1.0:J2ME:1.0" 
                    elementFormDefault="qualified" 
                    attributeFormDefault="unqualified">

	<xs:import namespace="urn:oasis:names:tc:dss:1.0:profiles:codesigning:1.0" schemaLocation="http://docs.oasis-open.org/dss/v1.0/oasis-dss-profiles-codesigning-schema-v1.0-r1.xsd"/>
	
	<!--J2ME codesigning profile provides a concrete profile of the abstract codesigning profile for generating signatures for MIDP 2.0 devices.-->
	<!--X509CertificatePath-->
	<!--The J2ME codesigning server may return multiple certificate paths for a single signing certificate. The order of the elements are significant. The first <X509CertificatePath> element represents the first certificate path and maps to a certificate path of n=1 in the JAD, the second  <X509CertificatePath> element represents the second certificate path and maps to a certificate path of n=2 in the JAD, and so on. Refer to Chapter 4 of the MIDP 2.0 specification.-->
	<xs:element name="X509CertificatePath" type="dsscsj2me:X509CertificatePathType"/>
	<!--The X509CertificatePath contains a number of <X509Certificate> elements. The first <X509Certificate> element contains the Base64 encoded signing certificate, corresponding to the m=1 for the certificate in the JAD file in the current <X509CertificatePath>, the seond certificate represents the intermediary certificate that issued the signing certificate ("m=2" in the JAD file) in the current <X509CertificatePath>, the m'th certificate represents the m-1'st intermediary certificate that issued the m-2'nd certificate in the current <X509CertificatePath>.-->
	<xs:element name="X509Certificate" type="dsscsj2me:X509CertificateType"/>
	<xs:complexType name="X509CertificatePathType">
		<xs:sequence maxOccurs="unbounded">
			<xs:element ref="dsscsj2me:X509Certificate"/>
		</xs:sequence>
	</xs:complexType>
	<xs:simpleType name="X509CertificateType">
		<xs:restriction base="xs:base64Binary"/>
	</xs:simpleType>
</xs:schema>
