Re: [tei-council] anyElement voodoo

After the ODD is compiled all the namespaces should be available there. Maybe this can be solved with a post-compilation step. Though maybe not for RNG schemas. On Tue, Nov 8, 2016 at 11:44 AM, Hugh Cayless wrote:

Maybe...we'd have to inspect the ODD or RNG Schema on the other end of the link, and maybe resolve any includes *that* might have. Not impossible, but perhaps hard. I think the choices are:

1) Try to figure out what namespaces get used in the current and any referenced ODDs or schemas 2) Invent a standard way of defining namespaces to be excluded 3) Use the definition of macro.anyXML as #2

#3 is done, but only because it was convenient, and it means making macro.anyXML special, i.e. unlike other macros, it doesn't get stripped out if not used, and will end up in any derived schema, whether used or not.

On Mon, Nov 7, 2016 at 5:02 PM, Raffaele Viglianti < raffaeleviglianti@gmail.com> wrote:

...

On Mon, Nov 7, 2016 at 4:45 PM, Hugh Cayless wrote:

...

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