Also note that a change to the resource class will require a change to the
permission class that wraps it.  Not that that is a big deal but it will
need to be done.

I think that the proposal to filter by languages as specified by Soroka is
correct.  Empty list returns no solutions.  Null list returns all?  I think
if you dont want to filter you will use the other form of the method.

On 29 Sep 2016 14:19, "A. Soroka (JIRA)" <[email protected]> wrote:

>
>     [ https://issues.apache.org/jira/browse/JENA-1238?page=
> com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=15533937#comment-15533937 ]
>
> A. Soroka commented on JENA-1238:
> ---------------------------------
>
> Not sure it's much more convenient to put the method on that class, rather
> than a {{static}} helper, but there are some other semantics to define
> anyway. How to deal with multiple values? In a helper method, I could
> accept that a random choice will be made, but in a method on the type, I
> would like to see something better defined. Or a single method that returns
> a {{Collection<Statement>}}, which may be empty.
>
> > Add methods on Resource class that look for Properties in a specific
> language
> > ------------------------------------------------------------
> -----------------
> >
> >                 Key: JENA-1238
> >                 URL: https://issues.apache.org/jira/browse/JENA-1238
> >             Project: Apache Jena
> >          Issue Type: Improvement
> >          Components: Core
> >    Affects Versions: Jena 3.1.0
> >            Reporter: Ramiro Pereira de Magalhães
> >
> > It would be very convenient to have in the 
> > {{org.apache.jena.rdf.model.Resource}}
> interface methods such as:
> > {code}
> >     public Statement getProperty( Property p, String lang );
> >     public Statement getRequiredProperty( Property p, String lang );
> > {code}
> > They'd work like very much like {{org.apache.jena.rdf.model.
> ModelCon.listStatements(Resource, Property, String, String)}}.
> > This would simplify queries to a Resource's language-specific properties.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Reply via email to