Re: Can we be more concrete?
Eliot replies to Len:
| >> I'm not sure what you mean. I thought use of URLs (and therefore support
| >> for their resolution) was a hard requirement for XML.
| >It is, I believe. It comes under "gotta live with what is working".
| >Can't say I like the #hack. How does this fit with the concept of
| >separately storing queries so that they can be reused by multiple
| >links in multiple documents? I want to point to a query multiple times
| >much like a function is prototyped, then called whereever needed.
| Assuming that XML provides/supports/requires indirect addressing, then you
| should be able to use the #name syntax to address a location address that
| is a query, e.g.:
| <crossref linkend="http://www.mine.com/queries.xml#all-basset-sites">
| Basset hounds</crossref> are slobber monsters.
| <!-- queries.xml: -->
| <!DOCTYPE Queries SYSTEM "queries.dtd" >
| <AltaVistaQuery id=all-basset-sites>basset+hound</AltaVistaQuery>
Yes, assuming that you proclaim that it is part of the XML MIME
type that unqualified fragment addressing into XML entities points to IDs
(not controversial, but I think a necessary step). And this
is a good start on a scenario.
So, what indicates the semantics of the link to the query? It isn't
the HTTP method. Is it the semantics of <crossref>? What
indicates whether the query shall be displayed per se,
the result of the query shall be trancluded (and in what
format), or the result of the query shall be presented as
a menu list, or the most desireable (per some set of preferences)
of the list results shall be traversed to?
Terry Allen Fujitsu Software Corp. email@example.com
"In going on with these experiments, how many pretty systems do we build,
which we soon find outselves obliged to destroy?" - Benjamin Franklin
A Davenport Group Sponsor: http://www.ora.com/davenport/index.html