OASIS Darwin Information Typing Architecture (DITA) TC

<spec src=” http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/complete/part3-all-inclusive/archSpec/base/keyScopes.html” ;> A key scope includes the following components: - The scope-defining element - The elements that are contained by the scope-defining element, minus the elements that are contained by child key scopes - The elements that are referenced by the scope-defining element or its descendants, minus the elements that are contained by child key scopes </spec> By virtue of the first bullet, keys defined on a scope-declaring element are in the scope declared by that element. Chris On 1/19/17, 4:57 PM, "dita@lists.oasis-open.org on behalf of Eliot Kimber" <dita@lists.oasis-open.org on behalf of ekimber@contrext.com> wrote: Consider this topicref: <topicref keys=”key-01” keyscope=”scope-01”/> Is the key name “key-01” in the scope “scope-01” or is it in the scope define by the topicref’s nearest scope-defining ancestor? I couldn’t find anything in the 1.3 spec the definitively answers this question and could only find one example of this case, in the discussion of branch filtering and the implications for keys? I’m sure we must have discussed this case at some point but it clearly wasn’t anyone’s focus judging by the lack of examples. Chris N.: You must have the definitive answer to this question. I think the right answer is that key-01 is in the scope scope-01 but I didn’t find any language that absolutely required that interpretation. Cheers, E. -- Eliot Kimber http://contrext.com --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

Hmm, that does seem definitive. Not sure why I didn’t read that first bullet to mean that when I look at it. Cheers, E. -- Eliot Kimber http://contrext.com On 1/19/17, 4:13 PM, "Chris Nitchie" <dita@lists.oasis-open.org on behalf of chris.nitchie@oberontech.com> wrote: <spec src=” http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/complete/part3-all-inclusive/archSpec/base/keyScopes.html” ;> A key scope includes the following components: - The scope-defining element - The elements that are contained by the scope-defining element, minus the elements that are contained by child key scopes - The elements that are referenced by the scope-defining element or its descendants, minus the elements that are contained by child key scopes </spec> By virtue of the first bullet, keys defined on a scope-declaring element are in the scope declared by that element. Chris On 1/19/17, 4:57 PM, "dita@lists.oasis-open.org on behalf of Eliot Kimber" <dita@lists.oasis-open.org on behalf of ekimber@contrext.com> wrote: Consider this topicref: <topicref keys=”key-01” keyscope=”scope-01”/> Is the key name “key-01” in the scope “scope-01” or is it in the scope define by the topicref’s nearest scope-defining ancestor? I couldn’t find anything in the 1.3 spec the definitively answers this question and could only find one example of this case, in the discussion of branch filtering and the implications for keys? I’m sure we must have discussed this case at some point but it clearly wasn’t anyone’s focus judging by the lack of examples. Chris N.: You must have the definitive answer to this question. I think the right answer is that key-01 is in the scope scope-01 but I didn’t find any language that absolutely required that interpretation. Cheers, E. -- Eliot Kimber http://contrext.com --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php