Github changes : issues and discussions features enabled.

[Andy Seaborne]

Hi - we've enabled the github "issues" and "discussions" areas on the 
code repo.


These are additional channels for the project.

There are no chanages to JIRA and no existing JIRA reports are lost.

Gihub allows people to subscribe and get notifications to your github 
inbox. As well as github notifications about issues, there is also an 
archive mailing list "issues@"


"discussions" are open for users to ask questions and exchange practice 
and experience. It is not the place for issues, bug reports etc. though 
we can create an issues from a discussion and turn an issue into a 
discussion if necessary.


For pull requests, please either create a JIRA or a github issue and 
include it at the start of the description line.


The Jena mailing lists are all available at 
https://lists.apache.org/list.html


users@
dev@
issues@ -- from github
pr@ -- from github
commits@
jira@

There isn't a discussions archive at the moment, - the Apache Foundation 
team are awaiting the API control of the discussions area to be declared 
stable.


Andy

SPARQL optional limiting results

[Mikael Pesonen]

Hi, not directly related to Jena, but I have a query in which optional 
clause limits the number of results. I thought it's never possible. So 
below query returns less results with optional enabled. Wonder why is 
that and what would be the correct way to get optional data so than all 
rows are returned?


SELECT *
WHERE
{
    VALUES ?graph { 
}

    GRAPH ?graph
    {
    {
        SELECT DISTINCT ?concept ?prefLabelm ?altLabelm WHERE
        {
            {
                (?concept ?score1 ?prefLabelm) text:query 
(skos:prefLabel "aamiainen*") .

    FILTER ( (lang(?prefLabelm) = "fi" ))
            }
    }
    }
   # OPTIONAL { ?concept skos:broader* [ skos:topConceptOf ?graph] }
    }
}