I hadn't checked but I was thinking that Jena Permissions is the name of the package while jena-permissions is the Maven artifact ID. I tend to use them interchangeably but perhaps the documentation should use the name except where referencing the maven artifact id or the jar. Feel free to make the changes.
On Wed, Dec 9, 2015 at 12:37 AM, Bruno P. Kinoshita (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/JENA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047783#comment-15047783 > ] > > Bruno P. Kinoshita commented on JENA-955: > ----------------------------------------- > > Hi Claude! > > Looking great, thanks! > > The only minor issue I noted is that the title uses "Jena Permissions", > then in the first paragraph it says "Jena-permissions", but in other pages > (eg Assembler) it says "Jena Permissions in the first paragraph. > > Should we refer to the module as Jena Permissions, Jena-permissions or > both interchangeably? > > > Review security documentation > > ----------------------------- > > > > Key: JENA-955 > > URL: https://issues.apache.org/jira/browse/JENA-955 > > Project: Apache Jena > > Issue Type: Documentation > > Components: Security > > Reporter: Bruno P. Kinoshita > > Assignee: Claude Warren > > Priority: Trivial > > Labels: documentation > > Fix For: Jena 3.0.0 > > > > > > Review the current documentation for the security module, and check if > there's any enhancements, or if anything changed after the Jena3 branch. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) > -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
