Re: Inconsistency in number of status values in draft-tan-epp-launchphase-12 ?

Patrick,

Good catch. My recommendation is for the text to be tightened up to
support only a single status, since the status really reflects the status
or state within the state diagram of Figure 1.  Adding support for
multiple statuses in the XML schema would make it more difficult for the
client to determine the state of the application. Thoughts?

-- 
 
JG
 

 
James Gould
Principal Software Engineer
[email protected]
 
703-948-3271 (Office)
12061 Bluemont Way
Reston, VA 20190
VerisignInc.com




On 3/5/14, 10:23 AM, "Patrick Mevzek" <[email protected]> wrote:

>Hello,
>
>the text says :
>Certain status values MAY be combined.  For example, an application
>   or registration may be both "invalid" and "rejected"
>
>the schema says :
><complexType name="infDataType">
>       <sequence>
>         <element name="phase" type="launch:phaseType"/>
>        <element name="applicationID"
>         type="launch:applicationIDType"
>         minOccurs="0"/>
>        <element name="status" type="launch:statusType"
>         minOccurs="0"/>
>
>so maybe a maxOccurs="unbounded" should be added there ?
>or maxOccurs="7" to be extra conservative ?
>
>-- 
>Patrick Mevzek
>
>_______________________________________________
>provreg mailing list
>[email protected]
>https://www.ietf.org/mailman/listinfo/provreg

_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg