Re: [VOTE] Split off GH PR email traffic to a new list.

[Dave Reynolds]

+1

Dave

On 07/01/2020 15:17, Claude Warren wrote:

+1 I like this idea

On Tue, Jan 7, 2020 at 3:02 PM Merlin Bögershausen <
merlin.boegershau...@rwth-aachen.de> wrote:


+1

Am Di, Jan 7, 2020 at 14:44 schrieb Andy Seaborne :

+1

On 07/01/2020 13:58, Aaron Coburn wrote:

+1

Thanks,
Aaron

On Tue, 7 Jan 2020 at 08:42, mailto:aj...@apache.org>> wrote:


+1. This would be great!

Adam

On Tue, Jan 7, 2020, 8:36 AM Andy Seaborne mailto:a...@apache.org>> wrote:


Happy 2020 everyone.

   From the [DISCUSS] around:




<

https://lists.apache.org/thread.html/12988132a86780d1fc14c6f893099cac50875e1d04a360d6046fdc0a%40%3Cdev.jena.apache.org%3E



<

https://lists.apache.org/thread.html/12988132a86780d1fc14c6f893099cac50875e1d04a360d6046fdc0a%40%3Cdev.jena.apache.org%3E




here is the formal vote:

Proposal:
This is the minimal proposal.


Ask INFRA for a new  mailing list, "pr@", and route github repo
email
currently going to dev@ to that list.


Please vote

   [ ] +1 Approve the proposal
   [ ]  0 Don't care
   [ ] -1 Don't make the change because ...


This vote is open to at least:

   Friday 2020-01-10 18:00 UTC.

(for additional discussion either the [DISCUSS] thread or change
"[VOTE]" to "[]".

   Andy

[GitHub] [jena] kinow commented on a change in pull request #666: JENA-1811: Dispatch on Content-Type. Accumulated code and comment cleanup.

[GitBox]

kinow commented on a change in pull request #666: JENA-1811: Dispatch on 
Content-Type. Accumulated code and comment cleanup.
URL: https://github.com/apache/jena/pull/666#discussion_r364095472
 
 

 ##
 File path: 
jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/auth/Auth.java
 ##
 @@ -103,4 +104,20 @@ public static boolean allow(String user, AuthPolicy 
policy, Runnable notAllowed)
 notAllowed.run();
 return false;
 }
+
+/**
+ * Calculate the value of the "Authentication" HTTP header for basic auth. 
Basic
+ * auth is not secure when used over HTTP (the password can be extracted). 
Use
+ * with HTTPS is better.
+ * 
+ * Unlike digest auth, basic auth can be setup without an extra round trip 
to the
+ * server, making it easier for scripts where teh body is not replayable.
 
 Review comment:
   s/teh/the (I think Java 8+ javadoc is stricter and requires the closing 
``, unless we are passing those args to reduce strictness during build)


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [jena] kinow commented on a change in pull request #666: JENA-1811: Dispatch on Content-Type. Accumulated code and comment cleanup.

[GitBox]

kinow commented on a change in pull request #666: JENA-1811: Dispatch on 
Content-Type. Accumulated code and comment cleanup.
URL: https://github.com/apache/jena/pull/666#discussion_r364094754
 
 

 ##
 File path: 
jena-arq/src/main/java/org/apache/jena/atlas/web/TypedInputStream.java
 ##
 @@ -47,11 +43,11 @@ private TypedInputStream(InputStream in)
 public TypedInputStream(InputStream in, String contentType)
 { this(in, ContentType.create(contentType), null) ; }
 
-public TypedInputStream(InputStream in, String mediaType, String charset)
-{ this(in, mediaType, charset, null) ; }
-
-public TypedInputStream(InputStream in, String mediaType, String charset, 
String baseURI)
-{ this(in, ContentType.create(mediaType, charset), baseURI) ; }
+//public TypedInputStream(InputStream in, String mediaType, String charset)
+//{ this(in, mediaType, charset, null) ; }
+//
+//public TypedInputStream(InputStream in, String mediaType, String 
charset, String baseURI)
+//{ this(in, ContentType.create(mediaType, charset), baseURI) ; }
 
 Review comment:
   Maybe we can delete this?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [jena] kinow commented on a change in pull request #666: JENA-1811: Dispatch on Content-Type. Accumulated code and comment cleanup.

[GitBox]

kinow commented on a change in pull request #666: JENA-1811: Dispatch on 
Content-Type. Accumulated code and comment cleanup.
URL: https://github.com/apache/jena/pull/666#discussion_r364096188
 
 

 ##
 File path: 
jena-rdfconnection/src/main/java/org/apache/jena/rdfconnection/examples/RDFConnectionExample6.java
 ##
 @@ -40,4 +40,3 @@ public static void main(String ...args) {
 }
 }
 }
-
 
 Review comment:
   I thought git asked for this extra newline at the end of the file.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

RE: [VOTE] Split off GH PR email traffic to a new list.

[Dr. Chavdar Ivanov]

+1

-Original Message-
From: Andy Seaborne  
Sent: Tuesday, January 7, 2020 2:36 PM
To: dev@jena.apache.org
Subject: [VOTE] Split off GH PR email traffic to a new list.

Happy 2020 everyone.

 From the [DISCUSS] around:

https://lists.apache.org/thread.html/12988132a86780d1fc14c6f893099cac50875e1d04a360d6046fdc0a%40%3Cdev.jena.apache.org%3E

here is the formal vote:

Proposal:
This is the minimal proposal.


Ask INFRA for a new  mailing list, "pr@", and route github repo email currently 
going to dev@ to that list.


Please vote

 [ ] +1 Approve the proposal
 [ ]  0 Don't care
 [ ] -1 Don't make the change because ...


This vote is open to at least:

 Friday 2020-01-10 18:00 UTC.

  (for additional discussion either the [DISCUSS] thread or change 
"[VOTE]" to "[]".

 Andy

Re: [VOTE] Split off GH PR email traffic to a new list.

[Bruno P. Kinoshita]

+1

Sent from Yahoo Mail on Android 
 
  On Wed, 8 Jan 2020 at 2:36, Andy Seaborne wrote:   Happy 
2020 everyone.

 From the [DISCUSS] around:

https://lists.apache.org/thread.html/12988132a86780d1fc14c6f893099cac50875e1d04a360d6046fdc0a%40%3Cdev.jena.apache.org%3E

here is the formal vote:

Proposal:
This is the minimal proposal.


Ask INFRA for a new  mailing list, "pr@", and route github repo email 
currently going to dev@ to that list.


Please vote

        [ ] +1 Approve the proposal
        [ ]  0 Don't care
        [ ] -1 Don't make the change because ...


This vote is open to at least:

    Friday 2020-01-10 18:00 UTC.

  (for additional discussion either the [DISCUSS] thread or change 
"[VOTE]" to "[]".

    Andy
  

[GitHub] [jena] NSeydoux opened a new pull request #667: JENA-1812 Migrated blank node hashing from MD5 to SHA-256

[GitBox]

NSeydoux opened a new pull request #667: JENA-1812 Migrated blank node hashing 
from MD5 to SHA-256
URL: https://github.com/apache/jena/pull/667
 
 
   Resolves issue [1812](https://issues.apache.org/jira/browse/JENA-1812)


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (JENA-1812) Migrate blank node hash algorithm from MD5 to SHA-256

[Nicolas Seydoux (Jira)]

Nicolas Seydoux created JENA-1812:
-

 Summary: Migrate blank node hash algorithm from MD5 to SHA-256
 Key: JENA-1812
 URL: https://issues.apache.org/jira/browse/JENA-1812
 Project: Apache Jena
  Issue Type: Improvement
  Components: ARQ
Reporter: Nicolas Seydoux
 Fix For: Jena 3.14.0


MD5 is a deprecated hashing algorithm, and even though it is not used on 
sensitive data in the context of Jena, its usage is picked up by security 
softwares as a security flaw. This may reduce the incentive to use Jena in 
commercial products, and computing SHA-256 hashes is not prohibitively more 
expensive than MD5.

 

Therefore, I suggest to migrate from using MD5 hashes to SHA-256.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: documentation update

[Andy Seaborne]

On 07/01/2020 15:51, Claude Warren wrote:

I did some documentation updates (SVN) and think I checked it in.  But I
must have missed a step.


I'm not clear what you are asking.

svn? svn log shows some updated by you on 2019-12-20
The staging site?
The published site?

> Is there documentation somewhere?

https://cwiki.apache.org/confluence/display/JENA/



Claude

documentation update

[Claude Warren]

I did some documentation updates (SVN) and think I checked it in.  But I
must have missed a step.  Is there documentation somewhere?

Claude

-- 
I like: Like Like - The likeliest place on the web

LinkedIn: http://www.linkedin.com/in/claudewarren

Re: [VOTE] Split off GH PR email traffic to a new list.

[Claude Warren]

+1 I like this idea

On Tue, Jan 7, 2020 at 3:02 PM Merlin Bögershausen <
merlin.boegershau...@rwth-aachen.de> wrote:

> +1
>
> Am Di, Jan 7, 2020 at 14:44 schrieb Andy Seaborne :
> > +1
> >
> > On 07/01/2020 13:58, Aaron Coburn wrote:
> >> +1
> >>
> >> Thanks,
> >> Aaron
> >>
> >> On Tue, 7 Jan 2020 at 08:42,  >> > wrote:
> >>
> >>> +1. This would be great!
> >>>
> >>> Adam
> >>>
> >>> On Tue, Jan 7, 2020, 8:36 AM Andy Seaborne  >>> > wrote:
> >>>
>  Happy 2020 everyone.
> 
>    From the [DISCUSS] around:
> 
> 
> 
> 
>  <
> https://lists.apache.org/thread.html/12988132a86780d1fc14c6f893099cac50875e1d04a360d6046fdc0a%40%3Cdev.jena.apache.org%3E
> >
> >>> <
> https://lists.apache.org/thread.html/12988132a86780d1fc14c6f893099cac50875e1d04a360d6046fdc0a%40%3Cdev.jena.apache.org%3E
> >
> 
>  here is the formal vote:
> 
>  Proposal:
>  This is the minimal proposal.
> 
> 
>  Ask INFRA for a new  mailing list, "pr@", and route github repo
>  email
>  currently going to dev@ to that list.
> 
> 
>  Please vote
> 
>    [ ] +1 Approve the proposal
>    [ ]  0 Don't care
>    [ ] -1 Don't make the change because ...
> 
> 
>  This vote is open to at least:
> 
>    Friday 2020-01-10 18:00 UTC.
> 
> (for additional discussion either the [DISCUSS] thread or change
>  "[VOTE]" to "[]".
> 
>    Andy
> 
> >>>
> >>
>
>

-- 
I like: Like Like - The likeliest place on the web

LinkedIn: http://www.linkedin.com/in/claudewarren

Re: [VOTE] Split off GH PR email traffic to a new list.

[Merlin Bögershausen]

+1

Am Di, Jan 7, 2020 at 14:44 schrieb Andy Seaborne :

+1

On 07/01/2020 13:58, Aaron Coburn wrote:

+1

Thanks,
Aaron

On Tue, 7 Jan 2020 at 08:42, > wrote:



+1. This would be great!

Adam

On Tue, Jan 7, 2020, 8:36 AM Andy Seaborne > wrote:



Happy 2020 everyone.

  From the [DISCUSS] around:



 





here is the formal vote:

Proposal:
This is the minimal proposal.


Ask INFRA for a new  mailing list, "pr@", and route github repo 
email

currently going to dev@ to that list.


Please vote

  [ ] +1 Approve the proposal
  [ ]  0 Don't care
  [ ] -1 Don't make the change because ...


This vote is open to at least:

  Friday 2020-01-10 18:00 UTC.

   (for additional discussion either the [DISCUSS] thread or change
"[VOTE]" to "[]".

  Andy

Re: [VOTE] Split off GH PR email traffic to a new list.

[Andy Seaborne]

+1

On 07/01/2020 13:58, Aaron Coburn wrote:

+1

Thanks,
Aaron

On Tue, 7 Jan 2020 at 08:42,  wrote:


+1. This would be great!

Adam

On Tue, Jan 7, 2020, 8:36 AM Andy Seaborne  wrote:


Happy 2020 everyone.

  From the [DISCUSS] around:




https://lists.apache.org/thread.html/12988132a86780d1fc14c6f893099cac50875e1d04a360d6046fdc0a%40%3Cdev.jena.apache.org%3E


here is the formal vote:

Proposal:
This is the minimal proposal.


Ask INFRA for a new  mailing list, "pr@", and route github repo email
currently going to dev@ to that list.


Please vote

  [ ] +1 Approve the proposal
  [ ]  0 Don't care
  [ ] -1 Don't make the change because ...


This vote is open to at least:

  Friday 2020-01-10 18:00 UTC.

   (for additional discussion either the [DISCUSS] thread or change
"[VOTE]" to "[]".

  Andy

Re: [VOTE] Split off GH PR email traffic to a new list.

[Chris Tomlinson]

+1

reduce clutter in 2020

Chris

> On Jan 7, 2020, at 07:36, Andy Seaborne  wrote:
> 
> Happy 2020 everyone.
> 
> From the [DISCUSS] around:
> 
> https://lists.apache.org/thread.html/12988132a86780d1fc14c6f893099cac50875e1d04a360d6046fdc0a%40%3Cdev.jena.apache.org%3E
> 
> here is the formal vote:
> 
> Proposal:
> This is the minimal proposal.
> 
> 
> Ask INFRA for a new  mailing list, "pr@", and route github repo email 
> currently going to dev@ to that list.
> 
> 
> Please vote
> 
>[ ] +1 Approve the proposal
>[ ]  0 Don't care
>[ ] -1 Don't make the change because ...
> 
> 
> This vote is open to at least:
> 
>Friday 2020-01-10 18:00 UTC.
> 
> (for additional discussion either the [DISCUSS] thread or change "[VOTE]" to 
> "[]".
> 
>Andy

[GitHub] [jena] afs opened a new pull request #666: JENA-1811: Diuspatch on Content-type. Accumulated code and comment cleanup.

[GitBox]

afs opened a new pull request #666: JENA-1811: Diuspatch on Content-type. 
Accumulated code and comment cleanup.
URL: https://github.com/apache/jena/pull/666
 
 
   Deprecation of DatasetAccessor etc (Use RDFConnection).
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (JENA-1811) Fuseki: Unexpected query string params interfer with content-type dispatch.

[Andy Seaborne (Jira)]

Andy Seaborne created JENA-1811:
---

 Summary: Fuseki: Unexpected query string params interfer with 
content-type dispatch.
 Key: JENA-1811
 URL: https://issues.apache.org/jira/browse/JENA-1811
 Project: Apache Jena
  Issue Type: Improvement
  Components: Fuseki
Affects Versions: Jena 3.13.1
Reporter: Andy Seaborne
Assignee: Andy Seaborne
 Fix For: Jena 3.14.0


The code checks for unexpected params before looking at the content type.

The comment is correct:
{noformat}
 * Query parameters (URL query string or HTML form)
 * Content-Type header
 * Otherwise it is a plain REST (quads) operation.chooseOperation
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (JENA-1811) Fuseki: Unexpected query string params interfer with content-type dispatch.

[Andy Seaborne (Jira)]

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

Andy Seaborne updated JENA-1811:

Issue Type: Bug  (was: Improvement)

> Fuseki: Unexpected query string params interfer with content-type dispatch.
> ---
>
> Key: JENA-1811
> URL: https://issues.apache.org/jira/browse/JENA-1811
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Jena 3.13.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.14.0
>
>
> The code checks for unexpected params before looking at the content type.
> The comment is correct:
> {noformat}
>  * Query parameters (URL query string or HTML form)
>  * Content-Type header
>  * Otherwise it is a plain REST (quads) operation.chooseOperation
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [VOTE] Split off GH PR email traffic to a new list.

[Aaron Coburn]

+1

Thanks,
Aaron

On Tue, 7 Jan 2020 at 08:42,  wrote:

> +1. This would be great!
>
> Adam
>
> On Tue, Jan 7, 2020, 8:36 AM Andy Seaborne  wrote:
>
> > Happy 2020 everyone.
> >
> >  From the [DISCUSS] around:
> >
> >
> >
> https://lists.apache.org/thread.html/12988132a86780d1fc14c6f893099cac50875e1d04a360d6046fdc0a%40%3Cdev.jena.apache.org%3E
> >
> > here is the formal vote:
> >
> > Proposal:
> > This is the minimal proposal.
> >
> >
> > Ask INFRA for a new  mailing list, "pr@", and route github repo email
> > currently going to dev@ to that list.
> >
> >
> > Please vote
> >
> >  [ ] +1 Approve the proposal
> >  [ ]  0 Don't care
> >  [ ] -1 Don't make the change because ...
> >
> >
> > This vote is open to at least:
> >
> >  Friday 2020-01-10 18:00 UTC.
> >
> >   (for additional discussion either the [DISCUSS] thread or change
> > "[VOTE]" to "[]".
> >
> >  Andy
> >
>

Re: Towards Jena 3.14.0

[Aaron Coburn]

I will have time to review any release candidates between now and Jan 20.

Cheers,
Aaron

On Tue, 7 Jan 2020 at 08:37, Andy Seaborne  wrote:

> It's coming up to time to look at Jena 3.14.0. v3.13.1 was 2019-10-11.
>
> I have time between now and January 19th to do a release or to work with
> anyone who is interested in performing a release. January 20th and after
> is likely to be busy due to new employment.
>
>  Andy
>
> == Contributions and notable JIRA
>
> Pavel Mikhailovskii:
> JENA-1787: SHACL improvement
> JENA-1786: DatasetGraphMonitor exposes unwrapped graphs
> JENA-1785: TDB2 bug fix
> JENA-1784: CacheSimple doesn't check keys for equality
>
> Ken Treimann:
> JENA-1781: Thrift upgrade to 0.13.0 for a CVE.
>
> Georg Schmidt-Dumont:
> JENA-1796: Add missing DV for XSD DateTimeStamp data type
>
> Adrian Wilke:
> JENA-1792: DCat vocabulary update to DCat2
>
>
> JENA-1779: Update to Jackson 2.10.1
>
> 2.10 has a design change to remove the 2.9.x attack point.
> Hopefully, moving to 2.10 will mean the end of recurring CVE's for Jackson.
>
> == JIRA
>
> https://s.apache.org/jena-3.14.0-jira
>
> 36 currently.
>
>

Re: [VOTE] Split off GH PR email traffic to a new list.

[ajs6f]

+1. This would be great!

Adam

On Tue, Jan 7, 2020, 8:36 AM Andy Seaborne  wrote:

> Happy 2020 everyone.
>
>  From the [DISCUSS] around:
>
>
> https://lists.apache.org/thread.html/12988132a86780d1fc14c6f893099cac50875e1d04a360d6046fdc0a%40%3Cdev.jena.apache.org%3E
>
> here is the formal vote:
>
> Proposal:
> This is the minimal proposal.
>
>
> Ask INFRA for a new  mailing list, "pr@", and route github repo email
> currently going to dev@ to that list.
>
>
> Please vote
>
>  [ ] +1 Approve the proposal
>  [ ]  0 Don't care
>  [ ] -1 Don't make the change because ...
>
>
> This vote is open to at least:
>
>  Friday 2020-01-10 18:00 UTC.
>
>   (for additional discussion either the [DISCUSS] thread or change
> "[VOTE]" to "[]".
>
>  Andy
>

Towards Jena 3.14.0

[Andy Seaborne]

It's coming up to time to look at Jena 3.14.0. v3.13.1 was 2019-10-11.

I have time between now and January 19th to do a release or to work with 
anyone who is interested in performing a release. January 20th and after 
is likely to be busy due to new employment.


Andy

== Contributions and notable JIRA

Pavel Mikhailovskii:
JENA-1787: SHACL improvement
JENA-1786: DatasetGraphMonitor exposes unwrapped graphs
JENA-1785: TDB2 bug fix
JENA-1784: CacheSimple doesn't check keys for equality

Ken Treimann:
JENA-1781: Thrift upgrade to 0.13.0 for a CVE.

Georg Schmidt-Dumont:
JENA-1796: Add missing DV for XSD DateTimeStamp data type

Adrian Wilke:
JENA-1792: DCat vocabulary update to DCat2


JENA-1779: Update to Jackson 2.10.1

2.10 has a design change to remove the 2.9.x attack point.
Hopefully, moving to 2.10 will mean the end of recurring CVE's for Jackson.

== JIRA

https://s.apache.org/jena-3.14.0-jira

36 currently.

[VOTE] Split off GH PR email traffic to a new list.

[Andy Seaborne]

Happy 2020 everyone.

From the [DISCUSS] around:

https://lists.apache.org/thread.html/12988132a86780d1fc14c6f893099cac50875e1d04a360d6046fdc0a%40%3Cdev.jena.apache.org%3E

here is the formal vote:

Proposal:
This is the minimal proposal.


Ask INFRA for a new  mailing list, "pr@", and route github repo email 
currently going to dev@ to that list.



Please vote

[ ] +1 Approve the proposal
[ ]  0 Don't care
[ ] -1 Don't make the change because ...


This vote is open to at least:

Friday 2020-01-10 18:00 UTC.

 (for additional discussion either the [DISCUSS] thread or change 
"[VOTE]" to "[]".


Andy

Re: [Discuss] Split the dev@ mailing list?

[Andy Seaborne]

Ok, we can see how it goes.

I'll kick off the VOTE for the minimal proposal in a moment.

Andy

On 13/12/2019 15:32, ajs6f wrote:

I'm +1 to splitting off pr@, -0 to splitting off issues@. I don't see that the 
gain is worth creating another list, managing more subscriptions, missing 
replies when they go to the wrong list, etc., but if other folks would like to 
try it, I'm not -1 against it.

ajs6f


On Dec 13, 2019, at 10:07 AM, Andy Seaborne  wrote:

Adam - where are we on this?

My understanding is that the difference in the discussion is around how JIRA is 
handled after we direct all GH traffic to pr@.

Either we leave JIRA emails coming to dev@ or we direct them to a new issues@.

Even with GH not causing additional JIRA ticket entries, the dev@ list may 
still be a bit busy. JIRA has it's own level of additional emails.

The sender is "j...@apache.org"; reply-to: is "dev@".

How "reply" works is different for different email clients:

GMail:

I only get the option of replying to the dev@list and that will not get put 
back on the ticket.

Thunderbird:

I get "reply" which goes to "j...@apache.org" and will update the ticket, and "reply 
list" to "dev@".

What are you hoping for by having JIRA emails go to dev@


I've just setup a personal JIRA filter subscription and now get a list of new tickets 
from the past 24 hours, sent to me once a day. I use this from JIRA cloud - I wanted to 
make sure it works for the Apache installation. The "watching" controls also 
work so a person can track specific tickets.

Andy

On 10/12/2019 08:44, Andy Seaborne wrote:

On 09/12/2019 20:51, Andy Seaborne wrote:



On 09/12/2019 16:26, ajs6f wrote:

I'm not sure why I would want to use a clunky and less-functional (no reply-to 
to comment on PR, non-formatting-aware) email list instead of the more 
powerful_and_  more pleasant GH system.


No one is asking you to.
It is not either-or.

GH tools remain untouched as they are today.
  >> PR discussion is done on GH

  > any comment on a PR creates at least three email messages in my inbox,

One of the copies, the useful message, you get is direct from GH, not via ASF 
(assuming you have GH notifications on)


1. Turn off auto-mirroring of all PR comments (which now starts once a ticket 
is mentioned) from GH to Jira.


Yes
  >> all PR traffic to pr@

  >2. Put PR comments on a separate pr@ list to record them.

Yes
  >> all PR [email] traffic to pr@


The only difference here is whether JIRA goes to issues@.
Anyone can combine their email into one folder (as they can separate it today). 
The difference is really on the archives.

missing the other big benefit - the dev@ is more approachable for people 
dropping in and showing an interest.


The one thing we still JIRA for because there isn't "issues" on GH
(and they are weak as a long term record IMO).

  Andy

[GitHub] [jena] afs opened a new pull request #665: Update year in NOTICE

[GitBox]

afs opened a new pull request #665: Update year in NOTICE
URL: https://github.com/apache/jena/pull/665
 
 
   Annual updates for NOTICE file which include the year.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Resolved] (JENA-1808) Incorrect validation returned when using the Fuseki SHACL processor

[Andy Seaborne (Jira)]

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

Andy Seaborne resolved JENA-1808.
-
  Assignee: Andy Seaborne
Resolution: Information Provided

> Incorrect validation returned when using the Fuseki SHACL processor
> ---
>
> Key: JENA-1808
> URL: https://issues.apache.org/jira/browse/JENA-1808
> Project: Apache Jena
>  Issue Type: Question
>  Components: Fuseki, SHACL
>Affects Versions: Jena 3.13.1
> Environment: macOS Catalina 10.15.2 (19C57)
> openjdk 13.0.1 2019-10-15
> OpenJDK Runtime Environment AdoptOpenJDK (build 13.0.1+9)
> OpenJDK 64-Bit Server VM AdoptOpenJDK (build 13.0.1+9, mixed mode, sharing)
>Reporter: Steve Roggenkamp
>Assignee: Andy Seaborne
>Priority: Major
> Attachments: upload-data.sh, validate-data.sh, 
> w3-shacl-example01-data.ttl, w3-shacl-example01-shapes.ttl, 
> w3-shacl-example01.ttl
>
>
> I'm new to Jena Fuseki and SHACL, so I thought I would use the example from 
> section 1.4 of the W3C Shapes Constraint Language document to insure I had 
> everything up and running correctly.  Unfortunately, when I upload the 
> example graph and run their example shape graph, Fuseki indicates the data 
> graph is validated:
> {noformat}$ ./validate-data.sh 
> @prefix rdf:  .
> @prefix sh:  .
> @prefix xsd:  .
> @prefix rdfs:  .
> [ a sh:ValidationReport ;
>  sh:conforms true
> ] .
> $
> {noformat}
>  
> I expected a validation report similar to that contained in the 
> recommendation indicating violations in the data graph.
> I have attached the configuration file that I use to configure Fuseki for 
> this test, along with the data and shape graph ttl files defining the graphs 
> and the two shell scripts I use to upload and validate the graph.
> The upload and test shell scripts are based on the curl examples from 
> [https://jena.apache.org/documentation/shacl/]
> When I change the name of the graph, I get a 404, so I expect the code is 
> validating the expected graph.  I can also see the default graph displayed in 
> the Fuseki viewer running locally at [http://localhost:8080/dataset.html] and 
> the triples appear as indicanted in the attached file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (JENA-1808) Incorrect validation returned when using the Fuseki SHACL processor

[Andy Seaborne (Jira)]

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

Andy Seaborne updated JENA-1808:

Fix Version/s: Jena 3.14.0

> Incorrect validation returned when using the Fuseki SHACL processor
> ---
>
> Key: JENA-1808
> URL: https://issues.apache.org/jira/browse/JENA-1808
> Project: Apache Jena
>  Issue Type: Question
>  Components: Fuseki, SHACL
>Affects Versions: Jena 3.13.1
> Environment: macOS Catalina 10.15.2 (19C57)
> openjdk 13.0.1 2019-10-15
> OpenJDK Runtime Environment AdoptOpenJDK (build 13.0.1+9)
> OpenJDK 64-Bit Server VM AdoptOpenJDK (build 13.0.1+9, mixed mode, sharing)
>Reporter: Steve Roggenkamp
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.14.0
>
> Attachments: upload-data.sh, validate-data.sh, 
> w3-shacl-example01-data.ttl, w3-shacl-example01-shapes.ttl, 
> w3-shacl-example01.ttl
>
>
> I'm new to Jena Fuseki and SHACL, so I thought I would use the example from 
> section 1.4 of the W3C Shapes Constraint Language document to insure I had 
> everything up and running correctly.  Unfortunately, when I upload the 
> example graph and run their example shape graph, Fuseki indicates the data 
> graph is validated:
> {noformat}$ ./validate-data.sh 
> @prefix rdf:  .
> @prefix sh:  .
> @prefix xsd:  .
> @prefix rdfs:  .
> [ a sh:ValidationReport ;
>  sh:conforms true
> ] .
> $
> {noformat}
>  
> I expected a validation report similar to that contained in the 
> recommendation indicating violations in the data graph.
> I have attached the configuration file that I use to configure Fuseki for 
> this test, along with the data and shape graph ttl files defining the graphs 
> and the two shell scripts I use to upload and validate the graph.
> The upload and test shell scripts are based on the curl examples from 
> [https://jena.apache.org/documentation/shacl/]
> When I change the name of the graph, I get a 404, so I expect the code is 
> validating the expected graph.  I can also see the default graph displayed in 
> the Fuseki viewer running locally at [http://localhost:8080/dataset.html] and 
> the triples appear as indicanted in the attached file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (JENA-1808) Incorrect validation returned when using the Fuseki SHACL processor

[Andy Seaborne (Jira)]

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

Andy Seaborne updated JENA-1808:

Issue Type: Question  (was: Bug)

> Incorrect validation returned when using the Fuseki SHACL processor
> ---
>
> Key: JENA-1808
> URL: https://issues.apache.org/jira/browse/JENA-1808
> Project: Apache Jena
>  Issue Type: Question
>  Components: Fuseki, SHACL
>Affects Versions: Jena 3.13.1
> Environment: macOS Catalina 10.15.2 (19C57)
> openjdk 13.0.1 2019-10-15
> OpenJDK Runtime Environment AdoptOpenJDK (build 13.0.1+9)
> OpenJDK 64-Bit Server VM AdoptOpenJDK (build 13.0.1+9, mixed mode, sharing)
>Reporter: Steve Roggenkamp
>Priority: Major
> Attachments: upload-data.sh, validate-data.sh, 
> w3-shacl-example01-data.ttl, w3-shacl-example01-shapes.ttl, 
> w3-shacl-example01.ttl
>
>
> I'm new to Jena Fuseki and SHACL, so I thought I would use the example from 
> section 1.4 of the W3C Shapes Constraint Language document to insure I had 
> everything up and running correctly.  Unfortunately, when I upload the 
> example graph and run their example shape graph, Fuseki indicates the data 
> graph is validated:
> {noformat}$ ./validate-data.sh 
> @prefix rdf:  .
> @prefix sh:  .
> @prefix xsd:  .
> @prefix rdfs:  .
> [ a sh:ValidationReport ;
>  sh:conforms true
> ] .
> $
> {noformat}
>  
> I expected a validation report similar to that contained in the 
> recommendation indicating violations in the data graph.
> I have attached the configuration file that I use to configure Fuseki for 
> this test, along with the data and shape graph ttl files defining the graphs 
> and the two shell scripts I use to upload and validate the graph.
> The upload and test shell scripts are based on the curl examples from 
> [https://jena.apache.org/documentation/shacl/]
> When I change the name of the graph, I get a 404, so I expect the code is 
> validating the expected graph.  I can also see the default graph displayed in 
> the Fuseki viewer running locally at [http://localhost:8080/dataset.html] and 
> the triples appear as indicanted in the attached file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (JENA-1808) Incorrect validation returned when using the Fuseki SHACL processor

[Andy Seaborne (Jira)]

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

Andy Seaborne updated JENA-1808:

Description: 
I'm new to Jena Fuseki and SHACL, so I thought I would use the example from 
section 1.4 of the W3C Shapes Constraint Language document to insure I had 
everything up and running correctly.  Unfortunately, when I upload the example 
graph and run their example shape graph, Fuseki indicates the data graph is 
validated:


{noformat}$ ./validate-data.sh 
@prefix rdf:  .
@prefix sh:  .
@prefix xsd:  .
@prefix rdfs:  .

[ a sh:ValidationReport ;
 sh:conforms true
] .

$
{noformat}
 

I expected a validation report similar to that contained in the recommendation 
indicating violations in the data graph.

I have attached the configuration file that I use to configure Fuseki for this 
test, along with the data and shape graph ttl files defining the graphs and the 
two shell scripts I use to upload and validate the graph.

The upload and test shell scripts are based on the curl examples from 
[https://jena.apache.org/documentation/shacl/]

When I change the name of the graph, I get a 404, so I expect the code is 
validating the expected graph.  I can also see the default graph displayed in 
the Fuseki viewer running locally at [http://localhost:8080/dataset.html] and 
the triples appear as indicanted in the attached file.

  was:
I'm new to Jena Fuseki and SHACL, so I thought I would use the example from 
section 1.4 of the W3C Shapes Constraint Language document to insure I had 
everything up and running correctly.  Unfortunately, when I upload the example 
graph and run their example shape graph, Fuseki indicates the data graph is 
validated:

{{}}
{quote}$ ./validate-data.sh 
@prefix rdf:  .
@prefix sh:  .
@prefix xsd:  .
@prefix rdfs:  .

[ a sh:ValidationReport ;
 sh:conforms true
] .

$
{quote}
 

I expected a validation report similar to that contained in the recommendation 
indicating violations in the data graph.

I have attached the configuration file that I use to configure Fuseki for this 
test, along with the data and shape graph ttl files defining the graphs and the 
two shell scripts I use to upload and validate the graph.

The upload and test shell scripts are based on the curl examples from 
[https://jena.apache.org/documentation/shacl/]

When I change the name of the graph, I get a 404, so I expect the code is 
validating the expected graph.  I can also see the default graph displayed in 
the Fuseki viewer running locally at [http://localhost:8080/dataset.html] and 
the triples appear as indicanted in the attached file.


> Incorrect validation returned when using the Fuseki SHACL processor
> ---
>
> Key: JENA-1808
> URL: https://issues.apache.org/jira/browse/JENA-1808
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki, SHACL
>Affects Versions: Jena 3.13.1
> Environment: macOS Catalina 10.15.2 (19C57)
> openjdk 13.0.1 2019-10-15
> OpenJDK Runtime Environment AdoptOpenJDK (build 13.0.1+9)
> OpenJDK 64-Bit Server VM AdoptOpenJDK (build 13.0.1+9, mixed mode, sharing)
>Reporter: Steve Roggenkamp
>Priority: Major
> Attachments: upload-data.sh, validate-data.sh, 
> w3-shacl-example01-data.ttl, w3-shacl-example01-shapes.ttl, 
> w3-shacl-example01.ttl
>
>
> I'm new to Jena Fuseki and SHACL, so I thought I would use the example from 
> section 1.4 of the W3C Shapes Constraint Language document to insure I had 
> everything up and running correctly.  Unfortunately, when I upload the 
> example graph and run their example shape graph, Fuseki indicates the data 
> graph is validated:
> {noformat}$ ./validate-data.sh 
> @prefix rdf:  .
> @prefix sh:  .
> @prefix xsd:  .
> @prefix rdfs:  .
> [ a sh:ValidationReport ;
>  sh:conforms true
> ] .
> $
> {noformat}
>  
> I expected a validation report similar to that contained in the 
> recommendation indicating violations in the data graph.
> I have attached the configuration file that I use to configure Fuseki for 
> this test, along with the data and shape graph ttl files defining the graphs 
> and the two shell scripts I use to upload and validate the graph.
> The upload and test shell scripts are based on the curl examples from 
> [https://jena.apache.org/documentation/shacl/]
> When I change the name of the graph, I get a 404, so I expect 

[jira] [Resolved] (JENA-1810) Add example for adding jena-text-es to Fuseki server jars

[Andy Seaborne (Jira)]

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

Andy Seaborne resolved JENA-1810.
-
Fix Version/s: Jena 3.14.0
 Assignee: Andy Seaborne
   Resolution: Done

> Add example for adding jena-text-es to Fuseki server jars
> -
>
> Key: JENA-1810
> URL: https://issues.apache.org/jira/browse/JENA-1810
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.14.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add comments into the POMs ("fulljar" and "server") on how to add 
> jena-text-es to Fuseki.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (JENA-1810) Add example for adding jena-text-es to Fuseki server jars

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/JENA-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009558#comment-17009558
 ] 

ASF subversion and git services commented on JENA-1810:
---

Commit 828236e53e0e847f0f17ebef840e282a955b5812 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=828236e ]

JENA-1810: Example of including jena-text-es in Fuseki


> Add example for adding jena-text-es to Fuseki server jars
> -
>
> Key: JENA-1810
> URL: https://issues.apache.org/jira/browse/JENA-1810
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add comments into the POMs ("fulljar" and "server") on how to add 
> jena-text-es to Fuseki.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (JENA-1810) Add example for adding jena-text-es to Fuseki server jars

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/JENA-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009559#comment-17009559
 ] 

ASF subversion and git services commented on JENA-1810:
---

Commit 2c99b9500c639efb5ef7dda05aa5c4df8cd4db50 in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=2c99b95 ]

Merge pull request #664 from afs/text-es

JENA-1810: Example of including jena-text-es in Fuseki

> Add example for adding jena-text-es to Fuseki server jars
> -
>
> Key: JENA-1810
> URL: https://issues.apache.org/jira/browse/JENA-1810
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Priority: Minor
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add comments into the POMs ("fulljar" and "server") on how to add 
> jena-text-es to Fuseki.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [jena] afs merged pull request #664: JENA-1810: Example of including jena-text-es in Fuseki

[GitBox]

afs merged pull request #664: JENA-1810: Example of including jena-text-es in 
Fuseki
URL: https://github.com/apache/jena/pull/664
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services