Hi, > Do people think we need a syntax for selectors that are handled by the > Sling/microsling framework and not by applications?
I´m not sure about using selectors instead suffixes. IMHO, version and translations are perspectives or different angles of the same hypothetical resource. And the name of the resource would be the "partner" of the extension. If you think about resources in a semantic way [1], it´s clear that we should no understanding two different versions of the same "resource" as two different resources. In this way, it´s more natural for me to have /content/some/resource.html/version1/lang1 than /content/mytext.a4.print.s:version:1:4.s:locale:fr_CH.html WDYT?, BR, Juanjo [1] http://www.w3.org/TR/rdf-primer/ On Dec 12, 2007 4:10 PM, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: > On Dec 10, 2007 12:25 PM, Juan José Vázquez Delgado > <[EMAIL PROTECTED]> wrote: > > > > (1) encode the requested version as part of the URL, such as > > > /content/some/resource.html;v=1.0 (for the resolve(request) method)... > > > > ...IMHO, there are some situations which we can need to retrieve the > same > > resource based on a particular perspective: version, language, anything > > else? > > I think that's what selectors are for - maybe we need to reserve some > of the selector "namespace" for sling-specific stuff? > > For example > > /content/mytext.a4.print.s:version:1:4.s:locale:fr_CH.html > > would mean > > resource path = /content/mytext > application selectors = a4.print > version = 1.4 > locale = fr_CH > output format = html > > As you mention, requesting a version in this way would need encoding > the dots in version numbers as colons, as dots separate selectors. > > Do people think we need a syntax for selectors that are handled by the > Sling/microsling framework and not by applications? > > -Bertrand >
