RE: 11.5: why submission/@separator?

While researching this, I found that section 3.3 lists the attribute as:

separator (';' | '&')

In other words, only two possible choices.

also, the XML Schema defines it as

       <xsd:attribute name="separator" use="optional" default=";">
         <xsd:simpleType>
           <xsd:restriction base="xsd:string">
             <xsd:enumeration value=";" />
             <xsd:enumeration value="&amp;" />
           </xsd:restriction>
         </xsd:simpleType>
       </xsd:attribute>

Is this sufficient?

Thanks,

.micah

-----Original Message-----
From: Klotz, Leigh [mailto:Leigh.Klotz@pahv.xerox.com]
Sent: Thursday, September 05, 2002 5:41 PM
To: 'Joe Schaefer'; 'Leigh L. Klotz'
Cc: 'XForms List'
Subject: RE: 11.5: why submission/@separator?



Thank you.  That part is an editorial oversight.  We'll fix it.
Leigh.

-----Original Message-----
From: Joe Schaefer [mailto:joe@sunstarsys.com] 
Sent: Thursday, September 05, 2002 10:52 AM
To: Leigh L. Klotz
Cc: XForms List
Subject: Re: 11.5: why submission/@separator?


"Leigh L. Klotz" <klotz@adoc.xerox.com> writes:

[...]

> Since we have a requirement to support legacy formats, and since it
> appears that "&" is required for interoperability, we added the option
> for force its use.

I'm perfectly happy with both ";" and "&" as possible separators, 
and leaving the decision up to the xforms author.  But I don't see 
the need for allowing any _other_ choice of separator character.  

To my knowledge, the restriction to either ";" or "&" is not 
spelled out in the current draft.

-- 
Joe Schaefer

Received on Friday, 6 September 2002 15:55:04 UTC