You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
RDF example encoding differs between source file and build-local/tests copy fed to transforms #80
Comparing my source example file to the copy the postprocessor writes under build-local/tests/<register>/<block>/example_N_N.ttl (the file actually fed to the transform), one RDF value is encoded differently between the two:
Both are valid Turtle, but the second form (an xsd:QName-typed literal) is not accepted by prov's deserializer, so my transform fails only when run through the postprocessor.
This suggests the postprocessor re-serializes/normalizes RDF examples at some point before running transforms against them, and that step changes this value's encoding. I haven't been able to find exactly where in the codebase this happens.
Question
Does the postprocessor re-serialize or canonicalize text/turtle examples before passing them to transforms (e.g. for validation)?
If so, could that be why the RDF encoding of a value changes between my source file and the copy used for the transform?
Activity