Spec / schema discrepancy

[Kevin Frender <kfrender@bea.com>]

I think I have noticed a discrepancy between the 
wsrp-2.0-types-pr-04.xsd and the wsrp-2.0-spec-pr-04 regarding the 
publicValues in a NavigationalContext.
In the spec section 5.1.23, 5th bullet point it is stated that (within a 
NavigationalContext) "The semantics of returning a publicValue item 
without a value are to clear any stored value for that item."  In both 
the spec and schema NavigationalContext's publicValues field is of type 
NamedString; in the spec section 5.1.11 defining NamedString, the value 
is marked as optional, which conforms to the statement from section 
5.1.23.  However, the schema definition for NamedString is:

 <complexType name="NamedString">
   <sequence>
     <element name="value" type="xsd:string"/>
   </sequence>
   <attribute name="name" type="xsd:string" use="required"/>
 </complexType>

-- the value is not optional.  Therefore, it is not possible to return a 
publicValue item without a value as stated in section 5.1.23.  Note that 
the empty string value is not the same as the null value-- we must be 
able to support empty string values distinct from null values.  
NamedString is also used as the mimeAttributes type in an UploadContext, 
and it is valid to have empty strings as a value for mime attributes.

As I see it, the schema needs to be changed to set minOccurs="0" on the 
NamedString value element.

 Kevin

Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.