-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
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
access file in zip: mixup absolute/relative url #335
Comments
This command causes the failure:
A script that merely finds and lists the files works ok: ### list-zip.sparql
prefix xyz: <http://sparql.xyz/facade-x/data/>
prefix fx: <http://sparql.xyz/facade-x/ns/>
prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>
prefix xsd: <http://www.w3.org/2001/XMLSchema#>
select ?file
where {
service <x-sparql-anything:> {
bind(coalesce(?__file,".*") as ?pattern)
fx:properties fx:location ?_zip.
fx:properties fx:archive.matches ?pattern.
[] fx:anySlot ?file
}
} Invoking it finds the right files:
|
This issue seems to be caused by |
Which is even more puzzling since this simpler script that RDFizes a single file works ok. ### rdfize.sparql
# sparql-anything -q rdfize.sparql -v file=../samples/class-IfcWall.ELEMENTEDWALL.json
construct {
?s ?p ?o
} where {
SERVICE <x-sparql-anything:media-type=application/json> {
bind(str(bsdd:) as ?bsdd)
fx:properties fx:namespace ?bsdd.
fx:properties fx:location ?_file.
fx:properties fx:use-rdfs-member true.
?s ?p ?o
}
}
PS: I've named the code excerpts for easier reference. |
This looks like a bug |
This script (same as in #334) opens an archive (https://sparql-anything.readthedocs.io/en/latest/Configuration/#from-archive) and rdfizes files from it:
fails with the following error:
I see two problems here:
fx:
are replaced with backward slashes. Maybe that comes from Windows/Cygwintmp\cd81ed69fe4de812bb3928afd960e85d
: WHY?fx:namespace
, but to a different namespace: to renamexyz -> bsdd
(BSDD is the data we're working with)The text was updated successfully, but these errors were encountered: