• scheme_map_clarifications

Clarifications to scheme proposal

Robert ran in to several questions while implementing the scheme map proposal. Questions are here, along with statements about implied items in the proposal, with clarifications from the submitter (Erik Hennum).

Open questions:

• No currently open questions

Resolved questions:

• The title attribute has been deprecated on maps in favor of <title>. I've added <title> to subjectScheme, but am unsure about @title give your current usage.

  • I'm okay with not providing a title attribute.
• Should subjectScheme get @outputclass?
  • Yes
• Added -dita-use-conref-target as a value on ennumerated attributes
  • Most kind

• I've added @keys to schemeref. copy-to, outputclass, other (topicref-atts aside from format/type) have not been added. After the fact: also added @scope, which should always go along with href/format/type)

  • Most kind
• Added @keys to hasNarrower, hasKind, hasPart, hasInstance; @query, copy-to, outputclass, (topicref-atts aside from scope/format/type) have not been added
  • Most kind
• hasRelated: Added @keys; @query, copy-to, outputclass, (topicref-atts aside from scope/format/type/collection-type) have not been added
  • Most kind
• Added @keys to subjectdef; did not add copy-to, outputclass, print, search, chunk
  • Most kind
• relatedSubjects: added @keys, did not add copy-to, outputclass, locktitle, toc, print, search, chunk
  • Most kind

• Reltable now has an optional title element (@title is deprecated). I've added <title> to subjectReltable, but left @title.

  • Should be okay to remove @title
• The DTD name you've got is mapScheme, but the module is scheme, and the root element is subjectScheme. I know that the difference between “the glossary specialization”, the module name of glossary, and the root element of glossentry has confused people, so I wonder if we should synchronize the scheme values on one of the 3?
  • I hear you, subjectScheme it is
• Should the indexing or “delayed conref resolution” domains be part of the scheme map?
  • Neither, I think
• Should the public ID be “Map Subject Scheme” or “Subject Scheme Map” — right now, the MOD is one way and the DTD is the other. DTD is Subject Scheme Map, so that's what I'm assuming.
  • Most kind
• Navtitle attribute is being deprecated in favor of navtitle element within topicmeta. Unsure what this means for subjectHead, which requires navtitle but does not have topicmeta? I've left @navtitle required.
  • EH: What are we going to do about topichead? Eventually remove @navtitle and require topicmeta?
  • RA: @navtitle will be optional on topichead, DITA 1.2 will likely require the element
  • EH: We should do the same thing with subjectHead that we do with topichead
  • RA: Subject Head does not allow topicmeta today - should it allow that to get navtitle, or subjectHeadMeta instead?
  • EH: subjectHeadMeta, content model of (navtitle?, shortdesc?)
• Assuming that new elements enumerationdef, elementdef, attributedef, defaultSubject are all specialized from topicref. No attribute listing given — need to know what to use. For each, I've just used navtitle, href, keyref, keys, scope (full list of values), format, type, univ-atts.
  • The elementdef and attributedef elements are both data specializations with a required attribute of name. Each has optional id, conref (and conref atts), status, outputclass, and base attributes. The translate attribute defaults to no. For both, the content consists of the following: (0..* data or data-about)
  • The defaultSubject element has the same attributes as the subjectdef element. It's content consists of the following: (0..* data or data-about)
  • The enumerationdef element is a specialized topicref element that has these optional attributes:
    • %id-atts; (id, conref, conaction, conrefend, conkeyref)
    • status
    • outputclass
    • base (and specializations of base)
  • Also for enumerationdef, I'd recommend changing the content model suggested in the proposal to list the default subject after the categories:
    • 0..1 elementdef
    • 1..1 attributedef
    • 1..* subjectdef
    • 0..1 defaultSubject
    • 0..* data or data-about