Lists Home |
Date Index |
Just for tidyness, if it isn't well-formed, it isn't XHTML. It is HTML.
And those are quintessential examples of applications that got to duck
out on the problems of recombinatorics by being closed tag stacks. The
problems start when one merges applications. Then the sort of metadata
one gets from a DTD, an arch form, a PSVI, etc. is needed.
The success of an application on its own is not the metric if
cross-language interoperability is the requirement. Sharing
a linking architecture is precisely that requirement. That
is precisely why HyTime, DSSSL etc came to the solutions they
did. That another group is attempting to meet that requirement
is a reason for the solutions being similar. Now it is an issue
of deciding are they the same.
Put the politics aside; we are only asked to solve technical issues.
If the WGs indulged in satisfying egos and deciding what are
political non-starters, then this is the kind of
unprofessionalism expected originally from the W3C. Quit
proving us right on that one. Answer the questions asked;
not the questions expected.
From: Dare Obasanjo [mailto:email@example.com]
Yeah, it is noteworthy that two of the most widespread uses of XML on the Web (XHTML and RSS) are rarely even well-formed XML let alone utilizing other aspects of the XML architecture. This is one of the reasons I have no problem with HLink in the context of XHTML but have many issues with trying to make it applicable to the general XML architecture.