To:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
cc:
"'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
From:
Sheer El-Showk <sheer@saraf.com>
Date:
Tue, 18 Dec 2001 09:56:38 -0500 (EST)
In-Reply-To:
<3CD14E451751BD42BA48AAA50B07BAD6C5FD68@vsvapostal3.prod.netsol.com>
Sender:
owner-ietf-provreg@cafax.se
Subject:
Re: Empty Text Elements
How would you then unset a value for an optional field? Sheer On Tue, 18 Dec 2001, Hollenbeck, Scott wrote: > One more fix to discuss based on a comment I received some time ago... > > Several text elements in different schemas can currently be sent empty, like > this: > > <org></org> > > This might be confusing or worse to a client or server that fails to account > for the fact that elements can be empty. If it would help make things more > robust, the definitions for such elements can be changed to ensure that the > elements contain at least one character. The definition for the type behind > the <org> element above could be changed from this: > > <simpleType name="postalLineType"> > <restriction base="normalizedString"> > <maxLength value="255"/> > </restriction> > </simpleType> > > to this: > > <simpleType name="postalLineType"> > <restriction base="normalizedString"> > <minLength value="1"/> > <maxLength value="255"/> > </restriction> > </simpleType> > > and the parser would ensure that empty elements don't get through. Would > that be a helpful change? > > -Scott- >