[jira] [Commented] (JENA-907) Change contract on getLocalName/getNameSpace.

["Andy Seaborne (JIRA)" <ji...@apache.org>]

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

Andy Seaborne commented on JENA-907:
------------------------------------

With Jena3, there is an opportunity to make this change.

> Change contract on getLocalName/getNameSpace.
> ---------------------------------------------
>
>                 Key: JENA-907
>                 URL: https://issues.apache.org/jira/browse/JENA-907
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Jena
>            Reporter: Andy Seaborne
>            Priority: Minor
>
> The methods {{getLocalName}} and {{getNamespace}} only split a URI if it is a strict legal RDF/XML value.
> This is becoming a source of questions on users@ as well as various forums.  The expectation of users has moved on toexpect a split more freely, inspired by Turtle.  The usages seem to be more about presentation of data than use in syntax.
> Proposal for Jena3:
> {{getLocalName}} and {{getNamespace}} used outside of syntax creation are considered as being for presentation and more aggressive split URIs.  This is at least as much as Turtle would, and possible at the last {{/}} or {{#}} regardless of legality of the local part.
> Currently found in:
> # {{Node.getLocalName}}
> # {{Property.getLocalName}}
> # {{Resource.getLocalName}}
> To do this, RDF/XML ouput needs its own copy of the origonal code ({{Util.splitNamespace}}).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)