[
https://issues.apache.org/jira/browse/JENA-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523290#comment-14523290
]
ASF subversion and git services commented on JENA-907:
------------------------------------------------------
Commit 6d3a74ff00339234d2ddc7792e0b8ea1f2db4b71 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=6d3a74f ]
JENA-907: Rename Util.splitNamespace as Util.splitNamespaceXML
This reflects its usage and enables a separation of use for
XML specifically and revising Node.getLocalName for Turtle.
> 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)
