Skip to content
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

Report command fails for some textual content when the output format is JSON #1016

Closed
psiotwo opened this issue Jun 22, 2022 · 3 comments
Closed

Comments

@psiotwo
Copy link
Contributor

psiotwo commented Jun 22, 2022

Having input.owl:

<rdf:RDF
     xmlns:obo="http://purl.obolibrary.org/obo/"
     xmlns:owl="http://www.w3.org/2002/07/owl#"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
     xmlns:xml="http://www.w3.org/XML/1998/namespace">
    <owl:Ontology rdf:about="http://test.org/test"/>

    <owl:ObjectProperty rdf:about="http://test.org/test#A">
        <obo:IAO_0000115>skos:Concept interferes with &quot;quoted text&quot;</obo:IAO_0000115>
    </owl:ObjectProperty>
</rdf:RDF>

and running

java -jar robot.jar report --input input.owl --output output.json

ends up with

-----------------
ERROR:      4
WARN:       0
INFO:       1
while parsing a block collection
 in 'reader', line 19, column 9:
            - "skos:Concept interferes with  ... 
            ^
expected <block end>, but found '<scalar>'
 in 'reader', line 19, column 44:
     ... skos:Concept interferes with \\"quoted text\\""
                                         ^

 at [Source: (StringReader); line: 19, column: 44]
Use the -vvv option to show the stack trace.
Use the --help option to see usage information.

Looks like some correlation inside the text field - removing the skos: prefix or the escaped double quotes makes things working. Also, textual output format (not JSON) works too.

@matentzn
Copy link
Contributor

I have to say @psiotwo your tickets are great :) Thanks for that. Its a bit hard right now to find resources to fix such bugs, but, regardless, your issues are really well reported and helpful! Thanks!

@psiotwo
Copy link
Contributor Author

psiotwo commented Jun 22, 2022

👍 Sure, clear ... will try to help resolving the stuff, as time permits ... .

psiotwo added a commit to psiotwo/robot that referenced this issue Jun 28, 2022
jamesaoverton added a commit to psiotwo/robot that referenced this issue Oct 28, 2022
jamesaoverton added a commit that referenced this issue Oct 28, 2022
@psiotwo
Copy link
Contributor Author

psiotwo commented Oct 31, 2022

Checked, works as of 1.9.1.

@psiotwo psiotwo closed this as completed Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants