We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unlike collection(), the function uri-collection() makes no attempt at parsing the document it finds in its collection (since Saxon 9.7); it simply just lists all of the URI's in the collection: https://www.saxonica.com/html/documentation/sourcedocs/collections.html.
collection()
uri-collection()
So we could list ALL URIs in the project from the outset and then just resolve paths to see whether or not the thing exists.
The text was updated successfully, but these errors were encountered:
Sounds like a great idea -- but what do you mean by "just resolve paths"?
Sorry, something went wrong.
I meant that, during our path resolution steps, if we have something like:
graphic:myImage.jpeg
And we know that "graphic" resolves to "../../graphics/"
Then we can resolve ../../graphics/myImage.jpeg into a full URI:
../../graphics/myImage.jpeg
/path/to/my/project/graphics/myImage.jpeg
and then simple see if that path exists in the uri-collection() sequence.
Got it, thanks!
joeytakeda
No branches or pull requests
Unlike
collection()
, the functionuri-collection()
makes no attempt at parsing the document it finds in its collection (since Saxon 9.7); it simply just lists all of the URI's in the collection: https://www.saxonica.com/html/documentation/sourcedocs/collections.html.So we could list ALL URIs in the project from the outset and then just resolve paths to see whether or not the thing exists.
The text was updated successfully, but these errors were encountered: