OASIS Darwin Information Typing Architecture (DITA) TC

From Jarno Elovirta: "What is the interaction between key scopes and <subjectdef>? Should subject scheme maps be processed with the same rules for key scopes as normal keys?" -- Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 682-2290; kriseberlein (skype)

As for whether the subject scheme processing should be the same for other maps with regard to key scopes, I think the answer is an unambiguous yes. Now, whether it makes sense to include the @keyscope attribute on the subject scheme-specific topicref specializations is something I don't feel particularly qualified to address. I suspect not, but that's a relatively ignorant and weakly-held opinion. Chris Chris Nitchie (734) 330-2978 chris.nitchie@oberontech.com www.oberontech.com < http://www.oberontech.com/ > Follow us: < https://www.facebook.com/oberontech > < https://twitter.com/oberontech > < http://www.linkedin.com/company/oberon-technologies > On 7/19/14, 7:26 PM, "Kristen James Eberlein" <kris@eberleinconsulting.com> wrote: > From Jarno Elovirta: > >"What is the interaction between key scopes and <subjectdef>? Should >subject scheme maps be processed with the same rules for key scopes as >normal keys?" > >-- >Best, >Kris > >Kristen James Eberlein >Chair, OASIS DITA Technical Committee >Principal consultant, Eberlein Consulting >www.eberleinconsulting.com >+1 919 682-2290; kriseberlein (skype) > > >--------------------------------------------------------------------- >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 >

I suggest that we do NOT include @keyscope on the subjectScheme and classification specializations of <topicref>. Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 682-2290; kriseberlein (skype) On 7/21/2014 9:11 AM, Chris Nitchie wrote: As for whether the subject scheme processing should be the same for other maps with regard to key scopes, I think the answer is an unambiguous yes. Now, whether it makes sense to include the @keyscope attribute on the subject scheme-specific topicref specializations is something I don't feel particularly qualified to address. I suspect not, but that's a relatively ignorant and weakly-held opinion. Chris Chris Nitchie (734) 330-2978 chris.nitchie@oberontech.com www.oberontech.com < http://www.oberontech.com/ > Follow us: < https://www.facebook.com/oberontech > < https://twitter.com/oberontech > < http://www.linkedin.com/company/oberon-technologies > On 7/19/14, 7:26 PM, "Kristen James Eberlein" <kris@eberleinconsulting.com> wrote: From Jarno Elovirta: "What is the interaction between key scopes and <subjectdef>? Should subject scheme maps be processed with the same rules for key scopes as normal keys?" -- Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 682-2290; kriseberlein (skype) --------------------------------------------------------------------- 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

I can imagine cases where it could be useful to have scoped subject schemes. For example, if they are being used to control metadata values in attributes, and group A has defined one set of allowed values for product, and group B has defined another set, then including the scoped schemes would allow the values to continue to be validated even when both groups' content sets are processed together. Michael Priestley, Senior Technical Staff Member (STSM) Total Information Experience (TIE) Technology Strategist mpriestl@ca.ibm.com http://dita.xml.org/blog/25 From:         Kristen James Eberlein <kris@eberleinconsulting.com> To:         Chris Nitchie <chris.nitchie@oberontech.com>, DITA TC <dita@lists.oasis-open.org>, Date:         07/21/2014 09:20 AM Subject:         Re: [dita] Review #1 comment re subjectdef elements and key scopes Sent by:         <dita@lists.oasis-open.org> I suggest that we do NOT include @keyscope on the subjectScheme and classification specializations of <topicref>. Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 682-2290; kriseberlein (skype) On 7/21/2014 9:11 AM, Chris Nitchie wrote: > As for whether the subject scheme processing should be the same for other > maps with regard to key scopes, I think the answer is an unambiguous yes. > Now, whether it makes sense to include the @keyscope attribute on the > subject scheme-specific topicref specializations is something I don't feel > particularly qualified to address. I suspect not, but that's a relatively > ignorant and weakly-held opinion. > > Chris > > > Chris Nitchie > (734) 330-2978 > chris.nitchie@oberontech.com > www.oberontech.com >   < http://www.oberontech.com/ > > Follow us: >   < https://www.facebook.com/oberontech > >   < https://twitter.com/oberontech > >   < http://www.linkedin.com/company/oberon-technologies > >   >   > > > > > > > On 7/19/14, 7:26 PM, "Kristen James Eberlein" > <kris@eberleinconsulting.com> wrote: > >>  From Jarno Elovirta: >> >> "What is the interaction between key scopes and <subjectdef>? Should >> subject scheme maps be processed with the same rules for key scopes as >> normal keys?" >> >> -- >> Best, >> Kris >> >> Kristen James Eberlein >> Chair, OASIS DITA Technical Committee >> Principal consultant, Eberlein Consulting >> www.eberleinconsulting.com >> +1 919 682-2290; kriseberlein (skype) >> >> >> --------------------------------------------------------------------- >> 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 >> > > > --------------------------------------------------------------------- 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

When a subject scheme is representing a codified taxonomy you would expect the keys used in the subject scheme map to be the assigned subject IDs from the taxonomy. In that case, it would not make sense to use key scopes because the effective keys would not match the original subject IDs. On the other hand, if you wanted to combine several independently-developed taxonomies into a single subject scheme map and you don't care about the actual subject ID values, then it would make sense to use key scopes in order to avoid any clash of subject IDs across the taxonomies being combined. For example, you might have taxonomies where the subject IDs are automatically generated, say by simple numbering of rows in a spreadsheet (this is something I do quite often when working with publishers that have ad-hoc taxonomies defined in spreadsheets). So I don't think it could be appropriate to disallow @keyscope on subject scheme topicrefs or maps. But I agree with Chris that the behavior should be the same as all other maps. Cheers, E. ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com On 7/21/14, 8:11 AM, "Chris Nitchie" <chris.nitchie@oberontech.com> wrote: >As for whether the subject scheme processing should be the same for other >maps with regard to key scopes, I think the answer is an unambiguous yes. >Now, whether it makes sense to include the @keyscope attribute on the >subject scheme-specific topicref specializations is something I don't feel >particularly qualified to address. I suspect not, but that's a relatively >ignorant and weakly-held opinion. > >Chris > > >Chris Nitchie >(734) 330-2978 >chris.nitchie@oberontech.com >www.oberontech.com > < http://www.oberontech.com/ > >Follow us: > < https://www.facebook.com/oberontech > > < https://twitter.com/oberontech > > < http://www.linkedin.com/company/oberon-technologies > > > > > > > > > >On 7/19/14, 7:26 PM, "Kristen James Eberlein" ><kris@eberleinconsulting.com> wrote: > >> From Jarno Elovirta: >> >>"What is the interaction between key scopes and <subjectdef>? Should >>subject scheme maps be processed with the same rules for key scopes as >>normal keys?" >> >>-- >>Best, >>Kris >> >>Kristen James Eberlein >>Chair, OASIS DITA Technical Committee >>Principal consultant, Eberlein Consulting >>www.eberleinconsulting.com >>+1 919 682-2290; kriseberlein (skype) >> >> >>--------------------------------------------------------------------- >>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 >> > > >--------------------------------------------------------------------- >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 > >