[jira] Commented: (SLING-23) Use correct namespaces (for node types, taglibs etc)
[ https://issues.apache.org/jira/browse/SLING-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530376 ] Bertrand Delacretaz commented on SLING-23: -- +1 for sling.apache.org, using the htttp://sling.apache.org/QUALIFIER/MODULE/VERSION scheme as proposed. I think it's best to avoid changing the namespaces later on. 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.
[jira] Commented: (SLING-23) Use correct namespaces (for node types, taglibs etc)
[ https://issues.apache.org/jira/browse/SLING-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530070 ] Carsten Ziegeler commented on SLING-23: --- Rethinking this, I think we should use the following schema: htttp://sling.apache.org/QUALIFIER/MODULE/VERSION where QUALIFIER is one of taglibs, jcr etc and MODULE specifies the module, like core, content, event etc. 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.
[jira] Commented: (SLING-23) Use correct namespaces (for node types, taglibs etc)
[ https://issues.apache.org/jira/browse/SLING-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530073 ] Bertrand Delacretaz commented on SLING-23: -- Maybe add a constant prefix before QUALIFIER? For example htttp://sling.apache.org/ns/... This would allow adding pages to our website under /ns/ to describe the namespaces later, if needed, by reserving this ns website path for this purpose. 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.
[jira] Commented: (SLING-23) Use correct namespaces (for node types, taglibs etc)
[ 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.
[jira] Commented: (SLING-23) Use correct namespaces (for node types, taglibs etc)
[ https://issues.apache.org/jira/browse/SLING-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530277 ] Bertrand Delacretaz commented on SLING-23: -- I'm fine with your opinions - my wish for having ns or namespaces in the URLs probably comes from too much teaching, where students would enter URLs such as http://sling.apache.org/jcr/sling/1.0 in their browsers as soon as they saw them, and complain about getting a 404 ;-) 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.
