OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xml-dev] So maybe ID isn't a problem after all.

On Mon, Nov 12, 2001 at 01:40:41PM -0800, Tim Bray wrote:
> At 03:53 PM 09/11/01 -0500, Daniel Veillard wrote:
> >On Fri, Nov 09, 2001 at 12:40:46PM -0800, Tim Bray wrote:
> >> So where's the problem?  When you're trying to process an
> >> XLink/XPointer into something and the only thing you know
> >> about it is that it's XML.  Er..... what's the scenario 
> >> where this happens?  -Tim
> >  In 2 seconds XInclude comes to mind,
> I'm sorry - a day reading follow-ups and I haven't seen my
> point addressed.  Can someone please come up with some 
> plausible use-cases where I would want to do any id-style 
> addressing into some XML without knowing what kind of XML
> it is?

  Hum, you said "process the XPointer", not "create the XPointer"
The action of addressing into, i.e. the design of the XPointer definitely
requires that knowledge. But so far it was considered a good idea to 
have the processing layer being possibly unaware of this.

> I can't see XInclude'ing something if I didn't know what
> vocabulary the something was.  I can't see writing any
> nontrivial XSL without knowing a lot about what I was
> transforming.

  Should the processor have the same level of knowledge ?

> It seems to me that the *right* solution is that any 
> interface to an XPointer/XPath implementation needs to have 
> an argument whereby you pass in internal knowledge of what,
> in the target document, the ID attributes are.  Because
> (a you'll typically have such knowledge, and
> (b) such an override/input could be damn useful in lots of
>     application scenarios anyhow.

  Hum, 2 things:
    - XPointer syntax is expected to be generic across the full
      range of XML resources, it should not be too complex either
    - XPointers must be context independant <regrin/>

But expressing how to find the IDs in the document at the
XPointer syntax level won't be fun. If not in XPointer
then it's either the instance or the DTD. Did I miss something ?

> Since I'm the one that first directed attention at this
> particular molehill, I'm kind of embarrassed at the 
> mountainous dimensions of the ensuing dialogue. -Tim

Hehe, it's XML-Dev, that's normal ...


Daniel Veillard      | Red Hat Network https://rhn.redhat.com/
veillard@redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/