[ 
https://issues.apache.org/jira/browse/ANY23-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280768#comment-13280768
 ] 

Hudson commented on ANY23-91:
-----------------------------

Integrated in Any23-trunk #209 (See 
[https://builds.apache.org/job/Any23-trunk/209/])
    Improved literal type parsing. Related to issue #ANY23-91. (Revision 
1341039)

     Result = SUCCESS
mostarda : 
Files : 
* 
/incubator/any23/trunk/core/src/main/java/org/apache/any23/io/nquads/NQuadsParser.java
* 
/incubator/any23/trunk/core/src/test/java/org/apache/any23/io/nquads/NQuadsParserTest.java

                
> NQuadsParser does not fail on prefixed datatypes
> ------------------------------------------------
>
>                 Key: ANY23-91
>                 URL: https://issues.apache.org/jira/browse/ANY23-91
>             Project: Apache Any23
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.7.0
>            Reporter: Peter Ansell
>
> The NQuadsParser should not parse either of the following lines into a 
> Statement, but instead it should throw an error:
> <http://www.ex.eu> <http://purlo.org/1.1/title> "yyy"^^xsd:datetime 
> <http://path.to.graph> .
> <http://www.ex.eu> <http://purlo.org/1.1/title> "yyy"^^xsd:datetime .
> The second statement is valid N3/Turtle as long as the prefix is defined 
> before hand, but the first statement is not valid in any of the Nx languages.
> The bug is inside of parseLiteralAttribute, where there is no validation that 
> the URI actually started. It may also be a good chance to cleanup this method 
> as it currently tries to parse languages and datatype URIs in the same code 
> which makes it difficult to patch as URIs don't look like language tags.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to