[Ietf-not43] IRIS Open Issues

[David Blacka]

On Thursday 13 November 2003 10:37 am, Andrew Newton wrote:
> The following are the items from the IRIS open issues presentation given
> Wednesday during the working group meeting.  Please provide comments if
> you have them.

> Status in Domain
> o New change to <sequence> forces server to sort them before sending them.

This isn't a show-stopper.  It is just annoying.

> o Maybe it should be <choice minOccurs='0' maxOccurs='unbounded'>
>      - With the addition of a boolean valued 'current' attribute on
> <appliedDate>, this allows servers to convey the history of the domain
> if they want.

Nothing else in CRISP has pointed toward using it to see historical data 
about a registration object.  I would be somewhat reluctant to start with 
this.

>      - Or simply specify that only one type of status element be used
> (must be expressed in words... not possible in XML Schema).

To be clear, the way you represent an "unordered set" in XMLSchema is to 
create a sequence of choices.  When you do that, you make it impossible to 
enforce the property of uniqueness.  So you could have:

  <dreg:status>
     <dreg:active>some date</dreg:active>
     <dreg:registrarHold>some date</dreg:registrarHold>
     <dreg:active>some other date</dreg:active>
  </dreg:status>

-- 
David Blacka    <davidb at verisignlabs.com> 
Sr. Engineer    Verisign Applied Research