From: Matthew C. <mat...@va...> - 2009-07-28 14:29:51
|
I can't make the call this morning either unfortunately. What I've tried to impress is that whatever option we choose, the version attribute or the schemaLocation, it can only be a hint, because before you know what schema to use there is no concept of attributes being required. Thus, whatever option we choose, it would be something that needs to be documented in the specification doc. So my recommendation is to not remove the version attribute in 1.1.1 but to document that it is meaningless and the schemaLocation hint should be present with the specified xsd filename. The alternative - forcing the version attribute to be a specific version (and presumably documenting that the schemaLocation is meaningless?) - seems unnecessarily un-xml-ish. Thanks, Matt Darren Kessner wrote: > Hi all, > > I just realized that I can't make the meeting this morning. > > Regarding the version attribute, I still agree with Matt that having > an extra version attribute is redundant, and therefore unnecessary. > > It's not difficult to implement, of course, but I just don't see the > point -- implementors will either: > 1) ignore the field, or > 2) read it, and verify that it matches the name of the xsd filename, > reporting error if there is a mismatch > > > Darren > > |