[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Unwrapping urn:public:...
/ Tony Coates <Tony.Coates@reuters.com> was heard to say: | On 07/05/2001 15:36:51 Norman Walsh wrote: | | >Are you suggesting that | > | > urn:publicid:-:OASIS:DTD+DocBook+XML+V4.1.2:EN | > | >should *match* | > | > PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "docbook.dtd" | | Interesting idea this, but so far we have only defined a mapping | from FPIs to URNs. For this to work robustly, we need to define the | reverse mapping, and we need to be able to round-trip without | introducing changes. If we can do that, then I guess we could allow | either format to appear in the catalogue, depending on the local | preference. That's an even greater extension and I think it's going to far. Right now: urn:publicid:* would match "urn:publicid:*" The proposal, as I understand it, is that we should allow urn:publicid:-:* to match "-//*" I think going the last step and allowing -//* to match "urn:publicid:-:*" is adding unnecessary confusion for users and burden for implementors. Be seeing you, norm -- Norman.Walsh@Sun.COM | It is a general error to imagine the loudest XML Standards Engineer | complainers for the public to be the most Technology Dev. Group | anxious for its welfare.--Edmund Burke, 1769 Sun Microsystems, Inc. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC