- From: Dean Hiller <dhiller@avaya.com>
- Date: Tue, 02 Dec 2003 12:42:35 -0700
- To: "Ian B. Jacobs" <ij@w3.org>
- Cc: www-tag@w3.org
- Message-ID: <3FCCEB2B.20301@avaya.com>
where is this 'extensibility finding' and how would I add to that. Currently, this is not supported by the xsd specification. I am trying to get something like this supported and I think the only way I can accomplish that is getting it written in some document I can refer to. thanks, dean Ian B. Jacobs wrote: >On Tue, 2003-12-02 at 11:27, Dean Hiller wrote: > > >>Hi all, >> I had a comment on the new section on extensibility and versioning. >> Particularly on these two statements.... >>1. "Must ignore": The agent ignores any content it does not recognize. >>2. "Must understand": The agent treats markup from an unrecognized >>namespace as an error condition. >> >>I am wondering if we can add one here....(this goes back to my use case >>which I currently know 2 projects using xsd's that way) >>3. "Must understand items from same namespace but can ignore extensions >>in other namespaces" >> >> > >Hi Dean, > >We discussed this sort of mixing at yesterday's teleconf [1]. I think >we decided to keep the document shorter by not adding more examples. >The extensibility finding may be a better home for this level of >detail. > > _ Ian > >[1] http://www.w3.org/2003/12/01-tag-summary.html > > >
Received on Tuesday, 2 December 2003 14:44:56 UTC