Hello,

Reading the draft RESTXQ spec[1], I have a question about path preference. Namely, can a bare trailing slash serve as a valid path segment?

I am thinking about the pattern used by some linked data services to accommodate httpRange-14[2]. For example, VIAF (Virtual International Authority File), a popular service for library data, uses a trailing slash to differentiate between the URI for a real-world object and the URI for the Web resource that represents it.

So, a GET request on the URI http://viaf.org/viaf/71387829 triggers a 303 redirect to http://viaf.org/viaf/71387829/

The RESTXQ implementation in BaseX does not seem to permit this pattern at present. If I create a resource function with a path annotation that ends in a trailing slash, the GET request returns 404.

Any chance this feature could be supported? :)

Best regards,
Tim

[1] http://exquery.github.io/exquery/exquery-restxq-specification/restxq-1.0-specification.html
[2] https://en.wikipedia.org/wiki/HTTPRange-14

--
Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library