Thank you for your reply, James.
I’m using the Escrow xsd files from your site to validate our deposit and report.
The mapping spec doesn’t match the rde-policy.xsd, but the xsd is the standard for validation.
John
From: Gould, James [mailto:JGould@verisign.com]
Sent: Wednesday, September 10, 2014 9:53 AM
To: John Keating
Cc: David Kipling; gtld-tech@icann.org
Subject: Re: [gtld-tech] Registry Escrow Policy Object
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
James Gould
Principal Software Engineer
jgould@Verisign.com
703-948-3271
12061 Bluemont Way
Reston, VA 20190
VerisignInc.com
On Sep 10, 2014, at 9:21 AM, John Keating <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
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?
5.8.1.
<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" />
...
9.15.
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] On
Behalf Of John Keating
Sent: 05 September 2014 17:56
To: 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 |
|
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). |