Daniel Barclay wrote: > Are you referring to <xs:any> elements (the wildcards they define) > or do you mean type xs:anyType?
Sorry for not being precise. I was talking about xs:anyType, the ur type. > Most of JaxMeXS's object model represents just incremental information, > right? For example, if complex type t1 has an attribute, and complex > type t2 extends t1 and adds an attribute, the XSComplexType object for > t2 does _not_ list both attributes; it only lists what t2 adds. (One > exception I notice is getPatterns().) I do not think so: See the method testExtension() in o.a.w.j.xs.junit.ParserTest. > But you don't build an implicit sequence in other cases, right? Again, I do not think so. > That is, if a complex type extends another type (not xs:anyType), > you don't add an extra XSModelGroup with a 'sequence' compositor > to represent an implicit sequence consisting of the content model > of the type that was extended and the added content from the type > that was derived by extension, right? No, the implicit sequence is always built, the exception being, if either the extended type or the extending type has the content model "empty", in which case the implicit sequence isn't required. > (I don't think you really want to represent that implicit sequence > here, since JaxMeXS general doesn't represent that level of > implicit information--that's for a higher level of processing.) JaxMeXS *is* intended for higher levels. > The representation must be documented. Otherwise, how can users know > what the representation means (e.g., how would a user know that > null represented the content model of xs:anyType) or know what to expect > for a given input? > > (That's why I have complained about the documentation--some of it is > simply wrong, and some important behavior isn't documented.) > > Whatever you choose, make sure the user of your API can know what's > supposed to happen. A point, that I have to admit. However, you've got to understand, that the emphasis of all current committers is in the JaxMe core. JaxMeXS is simply used. If you'd like to jump in, you are really welcome. But, believe me, if I should actually find the time for writing docs again, I'd write docs on the JaxMe core. Jochen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
