I kind of like the explicitness of the 'tei' prefix, but probably no harm
done there. Though we might need to be a bit careful about transforms whose
inputs aren't TEI. There's probably no overlap... I do kind of like being
able to search the stylesheets for instances where a particular TEI element
is referenced, and removing the prefix would make that somewhat harder.
What does make me slightly uncomfortable about the interaction of #1 and #3
is that temporary elements (some of which might be legacies of things you
had to do in XSLT 1.0) tend now to be in the null namespace, so this change
pushes you to adopt a new namespace for those. There's not actually any
harm in having temporary elements be in the TEI namespace—there's no
validation happening at that stage, and they're not part of the output.
What's the motivation for #2?
I don't agree that functions need their own namespace: there's no
possibility of ambiguity between functions and elements in XPath that I'm
aware of, so it simply isn't a problem. You could, I suppose, argue for
using a non-TEI namespace for functions if we wanted to start distancing
ourselves from the Stylesheets as a TEI-supported product.
Hugh
On Fri, Dec 29, 2017 at 10:26 PM, Syd Bauman
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