You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2015/05/01 15:31:06 UTC

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

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

Andy Seaborne updated JENA-907:
-------------------------------
    Description: 
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}}).

  was:
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 Trutle 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}}).


> 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)