On Mon, Nov 7, 2016 at 4:45 PM, Hugh Cayless
So that leads to the question: do we want to come up with a simpler syntax for adding excluded namespaces? I could see putting a new attribute on the moduleRef that pulls in the KML schema, for example…any opinions?
Is there any chance that this can be done automatically on moduleRefs that point to an external schema with @url? Or would it be too much magic and it would be best to allow encoders to list namespaces instead? I also wonder what are the consequences of this on ODD-defined elements in a different namespace, such as user TEI extensions or when combining two different ODD-defined schemata (e.g. TEI + MEI). In this case, perhaps, the Stylesheets should be able to deal with the exclusion themselves, since they can get distinct values of all @ns attributes. Then, when dealing with an elementSpec with content of anyElement, all the collected namespaces can be excluded. Or maybe it's not as simple as this. Raff
I’ve got another problem that may be a bug in trang. There’s a workaround, fortunately. I’ve gone on long enough for one email, I think. :-) -- 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