[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: "'asbjorn.rrp@theglobalname.org'" <asbjorn.rrp@theglobalname.org>, ietf-provreg@cafax.se
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Date: Wed, 27 Feb 2002 09:22:42 -0500
Sender: owner-ietf-provreg@cafax.se
Subject: RE: statusResultDataType

> -----Original Message-----
> From: asbjorn.rrp@theglobalname.org
> [mailto:asbjorn.rrp@theglobalname.org]
> Sent: Wednesday, February 27, 2002 8:58 AM
> To: ietf-provreg@cafax.se
> Subject: statusResultDataType
> 
> 
> Hi,
> 
> reading through the 05/06 drafts, I found the following:
> 
>   <complexType name="statusResultDataType">
>     <sequence>
>       <element name="clTRID" type="epp:trIDStatusType"
>        minOccurs="0"/>
>     </sequence>
>   </complexType>
> 
> In the 06-draft (Page 32) it states:
> 
> "Multiple elements MAY be returned if the server recognizes 
> the identifier and 
> the client does not enforce identifier uniqueness."
> 
> Am I missing something, or doesn't this mean that the element 
> should have a 
> maxOccurs="unbounded"?

Asbjorn,

Yes, someone else brought that error to my attention off-list.  It should
have a maxOccurs="unbounded" attribute, and it'll be added at the next
editing opportunity - most likely to deal with IESG or IETF last call
comments.

-Scott-

Home | Date list | Subject list