What do you have in mind? I think that documenting the architecture/dependencies between the W3C specs would be a fabulous start. Then issues can be raised and categorized.
Seems to be a fair bit of misunderstanding about the TAG and it's charter. It's not going to make browsers implement the same version of xhtml, it's not going to stop innovation or solve world hunger.
At least what it can do is actually document what the current web architecture is, maybe prevent messes like absolute/relative URI xml namespace names, arbitrate on overlaps between W3C working groups, and liase better with non-W3C working groups.
Cheers,
Dave Orchard
Slashdot Mirror
What do you have in mind? I think that documenting the architecture/dependencies between the W3C specs would be a fabulous start. Then issues can be raised and categorized.
Seems to be a fair bit of misunderstanding about the TAG and it's charter. It's not going to make browsers implement the same version of xhtml, it's not going to stop innovation or solve world hunger. At least what it can do is actually document what the current web architecture is, maybe prevent messes like absolute/relative URI xml namespace names, arbitrate on overlaps between W3C working groups, and liase better with non-W3C working groups. Cheers, Dave Orchard