Hopefully the HTML table that I embedded in my previous message was legible for Hugh and others even though it was converted to plain text in Hugh's reply. You're right that the current namespaces don't have terminal slashes, but the issue for me is that the URIs for those namespaces currently resolve to pages that are served by OpenCMS, which I am working to replace with WordPress. If we want these pages to continue being delivered by a CMS (always including the latest menu links etc.) rather than being static pages, then the pages might need to be served with a slash at the end. Or, as you suggest, we might be able to do something on the Apache level to override WordPress behavior. We can avoid Apache stuff by moving the pages for these namespaces URIs outside of a CMS and delivering them as static pages. But then we'll need to remember to update them as things change. Dealing with this is rising near the top of my list of tasks for the website, so I welcome any thoughts on how to proceed. Kevin On 1/2/18 7:11 AM, Hugh Cayless wrote:
Kevin, I'm a bit confused about this. The current namespaces don't have terminal slashes. Are you saying they will have to? Could we make use of Apache rewriterules instead of relying on WordPress to do this?
On the other hand, the current setup doesn't work properly either...
Hugh
On Fri, Dec 29, 2017 at 11:02 PM, Kevin Hawkins < kevin.s.hawkins@ultraslavonic.info> wrote:
Regarding item 3, note that this relates to https://github.com/TEIC/TEI/is sues/1592 . Here's where things stand:
*Old site URL** * *Current URL on new site** * *New site URL needs to be** * http://www.tei-c.org/ns/1.0/ http://www-dev.tei-c.org/tei-namespace/ http://www-dev.tei-c.org/ns/1.0 (no slash at end) http://www.tei-c.org/ns/Examples/ http://www-dev.tei-c.org/tei-e xamples-namespace/ http://www-dev.tei-c.org/ns/Examples (no slash at end)
You can use the WordPress dashboard to update a permalink, but WordPress requires a slash at the end and won't allow a dot in the URL. One of the things on my list is to figure out if there's an alternative here. If not, I may need to find a way to move these two files outside of WordPress like the various directories that were excluded from the migration.
However, if we're up for changing namespace URLs, our use of WordPress will be made easier if we agree to add a slash at the end of the namespace URL.
Kevin
On 12/29/17 9:26 PM, Syd Bauman wrote:
Three things I'd like to change in the Stylesheets:
1) Use xpath-default-namespace="http://www.tei-c.org/ns/1.0", and stop using "tei:" all over.[1]
2) Change the prefix for our examples namespace[2] from "teix:" to "xmp:" or something similar.
3) Change the namespace used for functions and temporary elements to something other than "http://www.tei-c.org/ns/1.0". I'm thinking of xmlns:tp="http://www.tei-c.org/ns/programming" or some such.
(1) and (2) are just conveniences, but the very kind of thing that a rub-a-dub-dub should clean up. (3), on the other hand, is needed because using the same namespace for functions in our XSLT as we do for elements in conformant documents is just plain wrong. The name "tei:duck" means something very different when it is the name of tei:duck(), an XSLT function, vs tei:duck, an element for manuscript description. Since they are different things, they should have different names. Not that we have any collisions at the moment, but namespaces were designed specifically to help avoid such collisions. So I think this is an important change, but want input as to what the namespace (and its prefix) should be.
Notes ----- [1] Actually, I've already done this in odd2odds.xsl. [2] http://www.tei-c.org/ns/Examples
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived