[jira] [Commented] (SLING-10996) RepoInit Parser doesn't properly define JCR Names

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

    [ https://issues.apache.org/jira/browse/SLING-10996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458972#comment-17458972 ] 

Angela Schreiber commented on SLING-10996:
------------------------------------------

linking to SLING-10952, which reports that the {{STRING}}  definition above doesn't properly reflect string values as they can be used for principal names and user/groupIds.

> RepoInit Parser doesn't properly define JCR Names
> -------------------------------------------------
>
>                 Key: SLING-10996
>                 URL: https://issues.apache.org/jira/browse/SLING-10996
>             Project: Sling
>          Issue Type: Bug
>          Components: Repoinit
>            Reporter: Angela Schreiber
>            Priority: Major
>
> the repoinit parser defines 2 types of string values, neither of which properly reflects JCR names:
> {code}
> < NAMESPACED_ITEM: (["a"-"z"] | ["A"-"Z"])+ ":" (["a"-"z"] | ["A"-"Z"])+ >
> < STRING: (["a"-"z"] | ["A"-"Z"] | ["0"-"9"] | ["-"] | ["_"] | ["."] | ["/"] | [":"] | ["*"]) + >
> {code}
> see https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/3_Repository_Model.html#3.2%20Names for the details on how a JCR name is defined and what characters are considered illegal.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)