[
https://issues.apache.org/jira/browse/SLING-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530121
]
Carsten Ziegeler commented on SLING-23:
---------------------------------------
Hmm,yes it makes sense to reserve the paths of our namespace and not use them
for the website. Now, I think we will host the website und
sling.apache.org/site (or website etc.) anyway as this is easier to setup and
manage with the confluence autoexport.
So, if we then reserve /taglibs and /jcr, we don't need the extra qualifier.
> Use correct namespaces (for node types, taglibs etc)
> ----------------------------------------------------
>
> Key: SLING-23
> URL: https://issues.apache.org/jira/browse/SLING-23
> Project: Sling
> Issue Type: Bug
> Reporter: Carsten Ziegeler
>
> As recently discussed, all namespace for sling should start with
> "http://sling.apache.org/"; (and not use the jackrabbit namespace), followed
> by an intermediate path denoting the type (like taglib, jcr namespace etc),
> followed by the version, so we'll have:
> http://sling.apache.org/taglibs/sling/1.0
> http://sling.apache.org/jcr/sling/1.0
> etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
