Re: [tei-council] anyElement decisions

Maybe we should be using a different attribute to exclude an element ? Sent from my Honor Mobile -------- Original Message -------- Subject: Re: [tei-council] anyElement decisions From: Hugh Cayless To: TEI Council CC: The problem is that it can contain namespaces and/or prefixed element names, and has to, so that we can exclude just the egXML element from the Examples namespace. Therefore it's not strictly a container for namespaces. On Mon, Nov 21, 2016 at 12:34 PM, Raffaele Viglianti < raffaeleviglianti@gmail.com> wrote:

I think @defaultExclusions should indicate that it's about namespaces. Especially because it's on schemaSpec, it could mean anything. What about just @exludens? This is to say that dropping "default" is better than dropping "namespace" because the fact that the attribute is on schemaSpec already indicates its broad scope.

On Nov 21, 2016 12:17 PM, "Lou Burnard" wrote:

On 20/11/16 19:33, Hugh Cayless wrote:

...

Following up by posting a summary of the decisions we made during Thursday's Council meeting regarding anyElement:

1. The @include attribute on anyElement will be renamed @require, which better summarizes its function.

Agreed

2. A new attribute will be added to schemaSpec which will list the default

...

name/namespace exceptions for RelaxNG schemas. Suggested name is defaultExceptionNS. I'm not 100% certain on that, because I'd like to allow single name exclusions as well, like teix:egXML (i.e. the egXML element itself, which can have an @xml:id). Maybe just @defaultExclusions?

I'm not crazy about the name either: @defaultExclusions is fine

3. Specify how #2 interacts with @require and @except on anyElement.

...

If @require is present on anyElement, all default exceptions apply in the generated RNG, and no additional exceptions should be specified on the anyElement. But if a namespace in the default exclusion list is in @require, it will not be excluded.

Can we stick to one terminology pls? ("exclusion" and "exception" are not quite the same thing: in my SGML-addled mind you can have an "inclusion exception")

So I think we have

@defaultExclusions on schemaSpec

@exclude on anyElement @require on anyElement

If anyElement supplies neither, then names and namespaces specified by schemaSpec are excluded. If anyElement supplies @require, then names and namespaces it specifies must be permitted even if they are excluded by schemaSpec or by @exclude attributes? or is that an error? or a warning?) If anyElement supplies @exclude, the names and namespaces specified are combined with any specified by schemaSpec

...

If @except is present on anyElement, its content overrides the default exclusions.

I would say (as indeed I just have) the ns it suppolies are additrional to those specified by the schemaSpec.

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