Did we explicitly decide to omit @keyscope from subjectScheme or is that an oversight?
ServiceNow is implementing the use of subjectSchemes to manage taxonomies mapped to our content and we need to put the subject scheme maps referenced from our publication maps in key scopes so they don't conflict with our other keys. I was surprised to find that @keyscope was not defined on subjectScheme.
In 1.3 there is no @keyscope, which could simply be a failure to add it when we did 1.3.
In 2.0, the current draft spec has subjectScheme taking the common topicref atts, which includes @keyscope, but the grammar and DTDs use a subjectScheme-specific attribute group that omits @keyscope.
I have a dim memory of us discussing keyscope on subject scheme maps but I don't recall it well enough. In any case, it seems like an oversight in 2.0 to omit @keyscope.
Cheers,
E.
_____________________________________________
Eliot Kimber
Sr. Staff Content Engineer
O: 512 554 9368
servicenow
servicenow.com
LinkedIn | X | YouTube | Instagram