October 2002 | ||||||
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
1 | 2 | 3 | 4 | 5 | ||
6 | 7 | 8 | 9 | 10 | 11 | 12 |
13 | 14 | 15 | 16 | 17 | 18 | 19 |
20 | 21 | 22 | 23 | 24 | 25 | 26 |
27 | 28 | 29 | 30 | 31 | ||
Sep Nov |
Incoming thought food
Marc, himself, his blogs, and you reading them
Matthew Langham's Radio Weblog
Here's how this works.
Yesterday, I received an answer from Excelon, the manufacturers of Stylus Studio, my beloved XML/XSLT IDE, concerning their current lack of OASIS entity catalog support. They said they (at least) knew that is wasn't there, but that I was the first customer actually requesting it.
Strange. I've been using OASIS catalogs since the SGML-era (yup, I'm in this circus for that long), and especially for DTD-guided authoring and validation, I couldn't live without it. And I can't imagine how people working with XML Schema (the horror) or RELAXNG cope with centralized installation and administration of their documentation grammars without them.
Since we use the Walsh entity resolver for Forrest, I'd rather see all of my tools support those catalogs. Currently only Softquad XMetal does to a decent degree.
8:51:41 AM comment []