David, My github site ( https://github.com/james-f-gould/draft-ryde ) is the most up to date; although I need to rollback the updates to the csvHost-1.0.xsd, csvDomain-1.0.xsd, and csvContact-1.0.xsd schemas based on the lack of interest in the changes to support the launch extension (application and claims). The xsd folder under the github site contains the latest version of rde-policy-1.0.xsd. Let me know if you run into any issues. Thanks, — JG [cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com] James Gould Principal Software Engineer jgould@Verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 VerisignInc.com<http://VerisignInc.com> On Sep 10, 2014, at 9:21 AM, John Keating <John.Keating@cira.ca<mailto:John.Keating@cira.ca>> wrote: Hi, I’m using the xsd files from James Gould’s github site. Where are the correct files? Thanks for your answer, John From: David Kipling [mailto:David.Kipling@nccgroup.com] Sent: Wednesday, September 10, 2014 4:52 AM To: John Keating; gtld-tech@icann.org<mailto:gtld-tech@icann.org> Subject: RE: Registry Escrow Policy Object Hi, Looking at the specification draft-arias-noguchi-dnrd-objects-mapping-05 online all seems fine. Where did you get rde-policy-1.0.xsd from as scope was added during the revisions to version 5? http://tools.ietf.org/html/draft-arias-noguchi-dnrd-objects-mapping-05#secti... 5.8.1<http://tools.ietf.org/html/draft-arias-noguchi-dnrd-objects-mapping-05#secti...>. <rdePolicy:policy> object The OPTIONAL <policy> contains the following attributes: o An <element> that defines that the referenced <element> is REQUIRED. o <scope> that defines the XPath of the element referenced by <element>. Example of <rdePolicy:policy> object: ... <rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain" element="rdeDom:registrant" /> ... http://tools.ietf.org/html/draft-arias-noguchi-dnrd-objects-mapping-05#secti... 9.15<http://tools.ietf.org/html/draft-arias-noguchi-dnrd-objects-mapping-05#secti...>. Policy Object <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="urn:ietf:params:xml:ns:rdePolicy-1.0" xmlns:rdePolicy="urn:ietf:params:xml:ns:rdePolicy-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <annotation> <documentation> Registry Data Escrow Policy schema </documentation> </annotation> <import namespace="urn:ietf:params:xml:ns:rde-1.0"/> <element name="policy" type="rdePolicy:policyType" substitutionGroup="rde:content"/> <complexType name="policyType"> <complexContent> <extension base="rde:contentType"> <attribute name="scope" type="token" use="required"/> <attribute name="element" type="anyURI" use="required"/> </extension> </complexContent> </complexType> </schema> Regards David From: gtld-tech-bounces@icann.org<mailto:gtld-tech-bounces@icann.org> [mailto:gtld-tech-bounces@icann.org] On Behalf Of John Keating Sent: 05 September 2014 17:56 To: gtld-tech@icann.org<mailto:gtld-tech@icann.org> Subject: [gtld-tech] Registry Escrow Policy Object Hi, There seems to be a discrepancy between the way an Escrow Deposit Policy object is defined. In section 5.8.1 of version 5 of the Object mapping doc it’s defined as: The OPTIONAL <policy> contains the following attributes: o An <element> that defines that the referenced <element> is REQUIRED. o <scope> that defines the XPath of the element referenced by <element>. Example of <rdePolicy:policy> object: <rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain" element="rdeDom:registrant" /> In rde-policy-1.0.xsd it’s defined as: <element name="policy" type="rdePolicy:policyType" substitutionGroup="rde:content"/> <complexType name="policyType"> <complexContent> <extension base="rde:contentType"> <attribute name="element" type="anyURI" use="required"/> </extension> </complexContent> </complexType> Which says it has one attribute named ‘element’ of type ‘anyURI’, and the attribute ‘scope’ is not mentioned and so is not allowed. Has this difference in definitions been mentioned before? Thanks, John ________________________________ David Kipling Solutions Architect NCC Group Manchester Technology Centre, Oxford Road Manchester, M1 7EF Telephone: +44 161 209 5430 Mobile: Fax: Website: www.nccgroup.com<http://www.nccgroup.com/> Twitter: @NCCGroupplc<https://twitter.com/NCCGroupplc> Email: David.Kipling@nccgroup.com<mailto:David.Kipling@nccgroup.com> <image001.jpg><http://www.nccgroup.com/> ________________________________ This email is sent for and on behalf of NCC Group. NCC Group is the trading name of NCC Services Limited (Registered in England CRN: 2802141). Registered Office: Manchester Technology Centre, Oxford Road, Manchester, M1 7EF. The ultimate holding company is NCC Group plc (Registered in England CRN: 4627044). Confidentiality: This e-mail contains proprietary information, some or all of which may be confidential and/or legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail and then delete the original. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on any information contained in this e-mail. You must not inform any other person other than NCC Group or the sender of its existence. For more information about NCC Group please visit www.nccgroup.com<http://www.nccgroup.com/> P Before you print think about the ENVIRONMENT
