Community
Participate
Working Groups
Scenario: Many of the W3C standards are in flux all the time and many drafts are published that all have the same public key (see for example the CCXML and VoiceXML standards). In the Voice Tools Project we have to support multiple versions of these standards and need to cache them all locally, so the XMLCatalog now has to have multiple entries with the same public key. The question now becomes: how does the uri resolver find the one the user wants to use? The XMLCatalog could support these scenarios by adding some type of preference UI that allows the user to pick a "default" in these cases. The URI Resolver would then use the default to resolve the DOCTYPE PUBLIC directives.
Changed Version field given new release numbering.
*** Bug 100611 has been marked as a duplicate of this bug. ***
I *think* this is an enhancement request, rather than a bug, so will change it to that for bugzilla book-keeping. If I'm mistaken, please do not hesitate to change it back. As support for this use-case is improved, I'd also like to make sure the solution is coordinated with out "documentType" extension point (currently undocument). BTW, some of this type of "special resolution" could probably sometimes be improved by making use of "content type" in the process of resolving ambiguous references. (That is, content type might be able to be used to "break ties".)
Is manually choosing an 'active' catalog entry the best way to do this? It's definitely do-able... but I'm just wondering if this would lead to cases where half of the XML files in a users workspace are always invalid depending on which DTD they 'activate' (active a different DTD and some files become correct and then other become incorrect). Perhaps having support for an XML Catalog per project would help? As David suggests there may be ways to utilize additional information in the XML files to associate the correct DTD. Any thoughts?
IN the New FIle Wizard you can select to have the file build based on a DTD (Selected from a catalog). When the file is created the DOCTYPE statement is added which includes the DTD. In the Voice Tools project we have allowed our users to set a default DTD so that the do not have to select a DTD each time a new file is created. This does open the possibility of having files in the workspace using different DTDs but we do not see this as a major problem at this time. The problem we are having is the need to define and use a different version of a DTD for an emerging standard. They will have the same public key. I'm not sure having an XML catalog for each project would fully resolve this problem. What we are looking for is a way to identify which of the DTDs (that have same public key) that our new file wizard should use when creating the new file.
it's an interesting idea, but we don't have people to work on this just now. We would accept high quality patches, though, especially if they address Craig's usability concerns.
