[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [xtm-wg] Correct use of published subjects
Lars Marius Garshol wrote: > > * Murray Altheim > | > | As I mentioned previously, the set of PSIs established by the > | existing language.xtm and country.xtm work completely well as PSIs, > | even if there are perceived errors in the topic map itself. There is > | no emergency here; we can wait six weeks. The xml:base problem you > | cite is simply a matter of Lars Marius misunderstanding the xml:base > | specification, > > If that's the case it would be great, since it would mean that this > particular problem is a tiny one of some people possibly being > mislead, rather than the rather major one it seems to be at the moment > (from my point of view). > > There are two issues here: > > a) what is the URI of an element with an ID attribute in the presence > of an xml:base attribute? It's the URI to the document (as modified by xml:base) plus the fragment ID. > b) what is the URI in an xlink:href attribute in the presence of an > xml:base attribute? It's the URI (as modified by xml:base). These aren't exactly tautologies. As I've now said on several occasions, these are both answered quite explicitly by the xml:base Recommendation. I would think that if the entire W3C XML Linking WG and then the entire W3C community were able to make sense enough of the xml:base spec to allow it to reach Recommendation, that perhaps there is something wrong with it, but that seems extremely unlikely given that this is essentially a one page spec. You make an awful fuss over something that seems so explicitly clear. If you look at the example markup in Section 3: http://www.w3.org/TR/xmlbase/#syntax you'll find a number of examples, any one of which should make it clear. The URI reference to use in any situation is the combination of the base URI for a document plus the fragment identifier. The base URI of the document is composed of its path plus its file name. If xml:base supplies the path (as is the case in the XTM files you cite), then one appends the filename and any fragment identifier. In our case, path: http://www.topicmaps.org/xtm/1.0/ filename: country.xtm id: #en PSI: http://www.topicmaps.org/xtm/1.0/ + country.xtm + #en Your idea of http://www.topicmaps.org/xtm/1.0/#en doesn't really make much sense. The file name is missing. I don't know why you have difficulty with this, why it is such a burning issue. It's in the xml:base Recommendation, it's been discussed by the XML Linking WG ad nauseum for the past two years, and we've had it in our spec since December. If you really think I'm wrong, I'd suggest bringing it up with the W3C Linking WG. I didn't invent this, I'm just following the spec, which has the same functionality that's been in HTML's <base> since HTML 2.0. And the example in the xml:base spec seems to make whatever possible confusion you might have pretty clear. Murray ........................................................................... Murray Altheim <mailto:murray.altheim@sun.com> XML Technology Center Sun Microsystems, Inc., MS MPK17-102, 1601 Willow Rd., Menlo Park, CA 94025 In the evening The rice leaves in the garden Rustle in the autumn wind That blows through my reed hut. -- Minamoto no Tsunenobu To Post a message, send it to: xtm-wg@eGroups.com To Unsubscribe, send a blank message to: xtm-wg-unsubscribe@eGroups.com Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC