Re: </optional> element
"Joel M. Halpern" <[email protected]>
| Newsgroups | gmane.ietf.forces |
|---|---|
| Message-ID | <[email protected]> |
The LFB Class definition (and structure definitions) needs an indication of whether a given element is mandatory or optional. We have that defined as an <optional/> element. We could instead have done it as an attribute of the element declaration itself. The element accessibility property tells whether the element is permitted / supported, thus indicating to the CE whether the FE supports that optional element. (Independent of whether it is present or not.) So, I think what you are asking for is already covered? Yours, Joel At 12:56 PM 10/16/2006, Jamal Hadi Salim wrote: >Joel, > >Should the optional element instead be a property of the element? >Seems to me like it would fit in the basic properties as well and we can >make use of some of those bits? > >cheers, >jamal