[
Lists Home |
Date Index |
Thread Index
]
Didier PH Martin wrote:
>
> Hi Paul,
>
> Paul said:
> > My point in the article I referenced is that the web is a system with
> > its own data model. If you want to get the full benefit of the Web you
> > need to map things into that model in the same way that you only get the
> > benefit of SQL by mapping things into the relational model. The web is
> > flexible enough that you can hack your way around the model (much easier
> > than you can in, e.g. SQL) but then you will run into limitations like
> > the SQL encoding issue.
>
> Didier replies:
> If we refer to the Uniform Resource Locators then each resource is
> identified with a "location". if obtaining data/content means that we are
> only allowed to obtain it with an HTTP GET (REST presumption) through a URI,
> for instance a locator (i.e. a URL), then if we use query templates to
> obtain content we will have to perform two operations:
>...
The point is that query templates is not really a first-class part of
the Web model. The Web model would encourage you to use XSLT templates
on the client side as your "query templates." We have to pop up a few
levels to the *real-world problem* you are trying to solve. Perhaps
query templates is not the way to solve it on the Web.
Paul Prescod
|
