Subject scheme not recognized from customized map

[Frank Ralf]

Hi,

I have some common attribute values defined in a subject scheme Map that is defined with the standard DITA DTD. When I reference this subject scheme map from a standard DITA map and open this map as a root map in oXygen everything works as expected and oXygen picks up the values from the subject scheme map. However, when I reference the same subject scheme map from a customized DITA map, oXygen doesn't pick up the values.

I've already had a closer look at our customized DTD but cannot figure out what could cause this behavior. My only suspect is the deactivated Delayed Resolution Domain but that should only affect @conrefs.

Any pointers welcome.

TIA
Frank

[Radu]

Hi Frank,

I'm not sure. Does the element which refers to the DITA Map have the format="ditamap" attribute set on it?
Does it also have the default class attribute value set so that it identifies a topicref?

- map/topicref ....

If you load the main map in the DITA Maps manager view, is the link to the subject scheme map expandable?

Regards,
Radu

[Frank Ralf]

Thanks for the pointers, Radu. I will check and report back.

Can this be an error in our DITA customization or is it more likely some oXygen mechanism not kicking in?

There's one other difference I noticed between this DITA customization and others we did. This one only has a DTD file for its map document type definition but neither a MOD nor an ENT file. The DTD references the generic map elements like so:

Code: Select all

<!-- ============================================================= -->

<!--                    MAP ELEMENT INTEGRATION                    -->

<!-- ============================================================= -->

<!ENTITY % map-type

PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Map//EN"

"../../base/dtd/map.mod"

>%map-type;

Best regards,
Frank

[Frank Ralf]

If you load the main map in the DITA Maps manager view, is the link to the subject scheme map expandable?

No, it doesn't. This looks similar to the problem we encountered some time ago - "Customized map schema: navtitles not resolved" - so I suppose the reason might indeed be that we messed up the default class attributes and/or the required DITAArchVersion attribute somehow.

I will investigate further and report back.

Frank

[Frank Ralf]

Hm, the @class attributes all look ok to me. But I've noticed something else which is probably related: With our customized map, the "Open map in editor with resolved topics" doesn't work either.

Frank

[Radu]

Hi Frank,

I'm not sure. Maybe the @domains attribute is not properly defined on the map.
If you can send us (support@oxygenxml.com) some sample file + the specialization plugin we could try to look into this.

Regards,
Radu

[Frank Ralf]

Hi Radu,

Thanks for your kind offer. We will have another look ourselves and report back.

Kind regards,
Frank

[Frank Ralf]

Just a follow up. I think we finally found the culprit: In our customized DITA Map framework the Java class DITAMapCustomRuleMatcher was missing from the association rules.

Frank

[Radu]

Hi Frank,

Thanks for the update.

Regards,
Radu