You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@any23.apache.org by "Hans Brende (JIRA)" <ji...@apache.org> on 2018/04/06 13:33:00 UTC

[jira] [Updated] (ANY23-342) Have a look at rdf4j's ParsedIRI class

     [ https://issues.apache.org/jira/browse/ANY23-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans Brende updated ANY23-342:
------------------------------
    Description: 
We often do lots of normalizing, fixing, parsing, and relativizing of URLs, URIs, and IRIs. 

We should have a look at rdf4j 2.3's ParsedIRI class, which seems to provide a lot of this functionality out of the box, to see where we can eliminate some (probably inconsistent) boilerplate across the codebase, and improve our existing URL/URI/IRI utility functions.

  was:
We often do lots of normalizing, fixing, parsing, and relativizing of URLs, URIs, and IRIs. 

We should have a look at rdf4j 2.3's ParsedIRI class, which seems to provide a lot of this functionality out of the box, to see where we can eliminate some (probably inconsistent) boilerplate across the codebase.


> Have a look at rdf4j's ParsedIRI class
> --------------------------------------
>
>                 Key: ANY23-342
>                 URL: https://issues.apache.org/jira/browse/ANY23-342
>             Project: Apache Any23
>          Issue Type: Improvement
>            Reporter: Hans Brende
>            Priority: Major
>
> We often do lots of normalizing, fixing, parsing, and relativizing of URLs, URIs, and IRIs. 
> We should have a look at rdf4j 2.3's ParsedIRI class, which seems to provide a lot of this functionality out of the box, to see where we can eliminate some (probably inconsistent) boilerplate across the codebase, and improve our existing URL/URI/IRI utility functions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)