RE: "status" element in <domain:info> response
"Liu, Hong" <Hong.Liu@neustar.biz> Wed, 11 September 2002 15:00 UTC
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11864
for <provreg-archive@ietf.org>; Wed, 11 Sep 2002 11:00:50 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1])
by nic.cafax.se (8.12.5/8.12.5) with ESMTP id g8BEt0o2023338
for <ietf-provreg-outgoing@nic.cafax.se>;
Wed, 11 Sep 2002 16:55:00 +0200 (MEST)
Received: by nic.cafax.se (8.12.5/8.12.5/Submit) id g8BEt0hb023337
for ietf-provreg-outgoing; Wed, 11 Sep 2002 16:55:00 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to
owner-ietf-provreg@cafax.se using -f
Received: from oak.neustar.com (oak.neustar.com [209.173.53.70])
by nic.cafax.se (8.12.5/8.12.5) with ESMTP id g8BEsxo2023332
for <ietf-provreg@cafax.se>; Wed, 11 Sep 2002 16:54:59 +0200 (MEST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
by oak.neustar.com (8.11.0/8.11.0) with ESMTP id g8BEsuG02767
for <ietf-provreg@cafax.se>; Wed, 11 Sep 2002 14:54:56 GMT
Received: by STNTIMC1 with Internet Mail Service (5.5.2653.19)
id <RZ7WBCJZ>; Wed, 11 Sep 2002 10:56:04 -0400
Message-ID: <5E42C1C85C5D064A947CF92FADE6D82E3EC2EF@STNTEXCH1>
From: "Liu, Hong" <Hong.Liu@neustar.biz>
To: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
Subject: RE: "status" element in <domain:info> response
Date: Wed, 11 Sep 2002 10:54:54 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk
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-
- "status" element in <domain:info> response Liu, Hong
- RE: "status" element in <domain:info> response Hollenbeck, Scott
- RE: "status" element in <domain:info> response Liu, Hong
- RE: "status" element in <domain:info> response Hollenbeck, Scott
- RE: "status" element in <domain:info> response Liu, Hong