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#section-5.8.1

 

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" />

   ...

 

 

http://tools.ietf.org/html/draft-arias-noguchi-dnrd-objects-mapping-05#section-9.15

 

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

 

 

 

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