[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
From: "Gould, James" <JGould@verisign.com>
Date: Tue, 18 Dec 2001 10:22:00 -0500
Sender: owner-ietf-provreg@cafax.se
Subject: RE: Empty Text Elements

Scott,

I believe this is a good change.  If an element exists, it should contain
text.

Jim

-----Original Message-----
From: Hollenbeck, Scott [mailto:shollenbeck@verisign.com]
Sent: Tuesday, December 18, 2001 8:38 AM
To: 'ietf-provreg@cafax.se'
Subject: Empty Text Elements


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- 

Home | Date list | Subject list