• State Not Answered
  • Replies 1 reply
  • Subscribers 46 subscribers
  • Views 957 views
  • Users 0 members are here
Options
Related

XSD causes web editor to fail

Bill Burns

I have updated a specialized DITA XSD to include an attribute specialization. The XSD validates in Oxygen, and I can create validating topics in both Oxygen and XMetal. However, when I attempt to open topics that use this specialized attribute, the web editor churns and never finishes opening the topic. When I validate the topic in Stylus Studio, it fails with the following message:

file:///c:/sandbox/1.2/healthwise/xsd/hwActionTask/hwActionTask.xsd:102,58: 'file:///c:/sandbox/1.2/healthwise/xsd/hwActionTask/commonElements.mod.xsd' has already been included or redefined
file:///c:/sandbox/active_task.xml:2,294: attribute 'iconType' is not declared for element 'p'

I can see nothing in the developer tools log to explain why it stops loading. The log blows right past the modified XSD file and the associated XSL but stops after loading custom.css. I get nothing more after that.

I have a hard time believing that Stylus is correct since Oxygen 19 validates the file. 

Here's the attribute declaration in the DITA shell XSD: 

   <xs:redefine schemaLocation="commonElements.mod.xsd">

      <xs:attributeGroup name="select-atts">

          <xs:attributeGroup ref="select-atts"/>

          <xs:attributeGroup ref="iconType-d-attribute"/>

      </xs:attributeGroup>     

  </xs:redefine>

 

and

 

      <xs:attributeGroup name="domains-att">

        <xs:attribute name="domains" type="xs:string" default="a(base iconType)"/>

    </xs:attributeGroup>

 

I thought <xs:redefine schemaLocation="commonElements.mod.xsd"> might create a circular reference, but neither XMetal and Oxygen choke.

Any suggestions?

Thanks,

Bill Burns

Content Architect | Healthwise

bburns@healthwise.org | www.healthwise.org

208.331.6917 (office)  |  208.345.1897 (fax)

 

Healthwise helps people make better health decisions.
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Here's a little bit more information.

    I compared the copy of commonElementMod.xsd in my specialization to the copy in the base folder. It has been heavily modified from the original DITA 1.2 XSDs, with all kinds of hooks into InfoShare. In addition, each specialized topics has its own folder and its own copy of this file (as well as many other base mod files).

    The original of commonElementMod.xsd defines the base-attribute-extensions and base attribute thus:

    <xs:attribute name="base" type="xs:string"/>
    <xs:attributeGroup ref="base-attribute-extensions"/>

    The modified file has the following:

    <xs:attribute name="base"/>

    I traced this file back to what was delivered to us on the installation media, and the same redefinition of the base attribute is there as well. I'm not sure if this is the problem or if something else is causing the specialization architecture to break, but the web editor can't seem to cope with it. Changing it back to the original doesn't help, so something else is at fault/

    I need to understand what the web editor requires that is different from the standard DITA attribute specialization mechanism.

    P.S. The Stylus issues seems to have something to do with not being able to parse the schemaLocations, so I think it has other issues.

    Thanks,

    Bill Burns

    Content Architect | Healthwise

    bburns@healthwise.org | www.healthwise.org

    208.331.6917 (office)  |  208.345.1897 (fax)

     

    Healthwise helps people make better health decisions.
Reply
  • 0

    Here's a little bit more information.

    I compared the copy of commonElementMod.xsd in my specialization to the copy in the base folder. It has been heavily modified from the original DITA 1.2 XSDs, with all kinds of hooks into InfoShare. In addition, each specialized topics has its own folder and its own copy of this file (as well as many other base mod files).

    The original of commonElementMod.xsd defines the base-attribute-extensions and base attribute thus:

    <xs:attribute name="base" type="xs:string"/>
    <xs:attributeGroup ref="base-attribute-extensions"/>

    The modified file has the following:

    <xs:attribute name="base"/>

    I traced this file back to what was delivered to us on the installation media, and the same redefinition of the base attribute is there as well. I'm not sure if this is the problem or if something else is causing the specialization architecture to break, but the web editor can't seem to cope with it. Changing it back to the original doesn't help, so something else is at fault/

    I need to understand what the web editor requires that is different from the standard DITA attribute specialization mechanism.

    P.S. The Stylus issues seems to have something to do with not being able to parse the schemaLocations, so I think it has other issues.

    Thanks,

    Bill Burns

    Content Architect | Healthwise

    bburns@healthwise.org | www.healthwise.org

    208.331.6917 (office)  |  208.345.1897 (fax)

     

    Healthwise helps people make better health decisions.
Children
No Data