RE: "status" element in <domain:info> response

["Liu, Hong" <Hong.Liu@neustar.biz>]

Scott, please see my comments below. 

-----Original Message-----
From: Hollenbeck, Scott [mailto:shollenbeck@verisign.com]
Sent: Wednesday, September 11, 2002 9:48 AM
To: 'Liu, Hong'; 'ietf-provreg@cafax.se'
Subject: RE: "status" element in <domain:info> response


> I have another question for clarification regarding the 
> "status" element in
> <domain:info> response for Domain -05. (Actually, similar 
> text appears in
> Domain -04).
> 
> On page 12, in describing <domain:status>, it says "One or 
> more OPTIONAL".
> But in the domain-1.0.xsd schema on page 38, the cardinality 
> of <status> in
> "infDataType" is minOccurs="0" and maxOccurs="12".
> 
> There are two issues involved:
> (1) Should the description on page 12 be changed from "One" to "Zero"?

No, because there always has to be at least one status value.  It should be
changed to remove the word "OPTIONAL".  The schema should be changed to
remove minOccurs="0".

<HL>
Thanks for the clarification. If at least one status tag should exist, then
the example on page 15 as well as the domain_info_unauth_result.xml in the
example package need to be fixed to include at least one status value.
</HL>

> (2) Should a cap be put on the number of statii returned? If 
> so, is the cap
> value "12" or "17"? When I check the "statusValueType" on 
> page 39, there are
> 17 values defined in the schema.

Re-read section 2.3.  There may be 17 values defined, but they can't all be
present at the same time.

<HL>
You are right, not all 17 values are allowed to co-exist at the same time
according to section 2.3. But I am having difficulty understanding how 12 is
derived from the complex rules in section 2.3. Could you explain that to me?
Thanks! 
</HL>

-Scott-