[jira] [Resolved] (JENA-986) Separate use of AnonId : keep in RDF API, introduce BlankNodeId for Graph SPI

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

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

Andy Seaborne resolved JENA-986.
--------------------------------
       Resolution: Done
    Fix Version/s: Jena 3.0.0

> Separate use of AnonId : keep in RDF API, introduce BlankNodeId for Graph SPI
> -----------------------------------------------------------------------------
>
>                 Key: JENA-986
>                 URL: https://issues.apache.org/jira/browse/JENA-986
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: Jena 3.0.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>             Fix For: Jena 3.0.0
>
>
> {{AnonId}} is a classed used in both the RDF API and the Graph SPI.  It resides in the RDF API package which blocks separating of the Graph SPI from the RDF API.
> The proposal is to 
> # introduce {{BlankNodeId}} as the Graph SPI concept and keep {{AnonId}} as the application-visible class.
> # Introduce a factory operation to create from a string label as the vast majority of uses of {{NodeFactory.createAnon}} do in fact wrap a string in an AnonId to pass it to {{NodeFactory.createAnon}}. The use case is parsers and related persistent data to java object construction.
> # Rename {{NodeFactory.createAnon}} as {{NodeFactory.createBlankNode}} for consistent naming (leaving deprecated versions in place). 



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