The struggle to get people to learn the DTD notation continued, but at least folks were willing to try out the feedback loop.
Think of it an aggregator of observations made by a number of different tools.
But those are not the sole ones, and one is used to edit documents: PUT.
until we get somebody to agree to them and act on them, it hardly makes a difference. On the basis of this test case and its implementation, the specification prose will be written.
As the history of CSS shows, we do a lot better when we add test suites to the mix. For example, somebody who checks the whole text about existing names of books. How much do we eat our own dog food?
He has, for example, just accepted a role as invited expert within the CSS working group. You could call this kind of information more in general "localization notes", because not the translator, but other people who participate in localization may need it. We are testing a prototype internally, and will make it public in the days or weeks to come. I know all sorts of stuff about URIs and Web Architecture, but I have a lot to learn about how bank web sites are designed and built before URIs work like I want them to. In the case of XML, you "internationalize" XML by providing the ITS markup to people who create a document or to localizers. When there will be issues which seems more difficult to overcome, we will explain the solution we have found and adopted to solve them.
This leads to several issues for editing clients, but also for servers.
Being able to get results of validation of HTML, checking of the style sheets, finding broken links, and more, much more, without having to visit ten different pages and services. People can voice their disagreement, pushing their issues. The popular implementations of HTML have never matched the DTD, and even the DTD isn't keeping up with XHTML specifications, let alone SVG or RDF. You are talking about "localization" all the time.
With ruby markup, you can give additional information like pronounciation to a base text.
This sounds like no big deal, but having standardized markup to express such things is a big advantage. How can users determine these qualities? Think of it an aggregator of observations made by a number of different tools.
Being able to get results of validation of HTML, checking of the style sheets, finding broken links, and more, much more, without having to visit ten different pages and services.