Re: [tei-council] rub-a-new-namespace

I’m with Raff in all cases. 1) I like the explicitness of prefixing element names 2) why do you want to change an established prefix/name? 3) No complaints here Happy new Year, everybody! Best Peter

Am 02.01.2018 um 22:11 schrieb Raffaele Viglianti :

1) I'm used to using prefixes in XSLT and prefer to have them explicit, but will go with the majority. 2) teix sounds nice and seems clear, what's wrong with it? 3) This is a good idea. Even if Hugh were correct that XPath won't mix up element and function names, I think it makes sense to keep these processing functions in a different namespace. We don't define or document them as part of the TEI standard (or its implementation)

On Tue, Jan 2, 2018 at 8: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

-- 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

-- 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