[jira] [Assigned] (OAK-4252) Separate Handling for Meta Infomation

["Angela Schreiber (Jira)" <ji...@apache.org>]

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

Angela Schreiber reassigned OAK-4252:
-------------------------------------

    Assignee:     (was: Angela Schreiber)

> Separate Handling for Meta Infomation
> -------------------------------------
>
>                 Key: OAK-4252
>                 URL: https://issues.apache.org/jira/browse/OAK-4252
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: core, jcr, security
>            Reporter: Angela Schreiber
>            Priority: Major
>
> Today there is no way to properly identity, protect and secure (read and write access) additional meta information associated with a given {{Node}}.
> With the current state of the JCR API and the implementation present in Oak the only kind of 'meta' is achieved by built-in functionality that consequently is able to mark special items {{protected}}, which comes with 2 drawbacks:
> - read access to protected items is in accordance with the specification handled in the same way than regular non-protected items
> - applications cannot write protected items through the JCR API which leaves these items ultimately 'system-maintained'. This is not particularly suitable for application driven meta-data that nevertheless should be identifiable and properly secured as such without having to come up with overly complex workaround nor access control setup.
> Introducing the concept of meta-information in a more generic way would provide us (and the application developers using Oak) with easier ways to mark data that are different from the default content (thinking of an image, a title, a text) and offer built-in support for properly secure them (both read and write access).



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