Clovertech

XML schema error – Element reference could not be found

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › XML schema error – Element reference could not be found

  • Creator
    Topic
  • May 31, 2012 at 4:58 pm #53125
    Jason Gross
    Participant

      Hello, I apologize as I’m not trained in xml at all so I’m not going to be very helpful on my end with any questions.

      I’m trying to compile a .xsd that was provided to me by a foreign system. We’ll then take that XML message and translate it into an HL7 message. They swear the file is fine through their checks and tools and that the schema is accurate. They are not familiar with Cloverleaf or any specific issue one might have there however.

      Anyway I copy the file into Server Package Viewer and try to compile it and always get the same error: “Error – Element reference could not be found. caption_cd”. Can anybody help me address this error so I can compile?

      I had to change it to .doc from .xsd to get it to post.

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • June 1, 2012 at 4:31 pm #76647
        Mark Thompson
        Participant

          Jason,

          I reviewed your schema.  The caption_cd element appears to be properly defined.  Moving it higher in the schema (ahead of any references) did not help — I’m getting the same error compiling the schema.

          Here is my suggestion:  Download a trial version of a schema validator (like Altova XMLSpy) to confirm the schema.  If it checks out OK, Cloverleaf product support is probably your next stop.

          Sorry I don’t have a better solution for you.

          - Mark Thompson
          HealthPartners

        • June 1, 2012 at 4:44 pm #76648
          Jason Gross
          Participant

            I really appreciate your time in looking at it. I went to a site that could automatically generate the .xsd and it also created a schema that generated the same error message so it seems like the .xsd is not the problem. I will pursue other avenues that may include Cloverleaf support. Thanks!

          • June 6, 2012 at 9:00 am #76649
            Richard Hart
            Participant

              Hi Jason.

              I found that many Microsoft generated schema definitions ‘failed’ a Cloverleaf validation and was fixed by ensuring that all the namespace aliases are included at the top level.

              eg

              <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema&#8221; … xmlns:b=”http://ns./Schema/HCAL/Core/Base&#8221;  …

            • June 6, 2012 at 1:50 pm #76650
              Jason Gross
              Participant

                Thanks for pointing me in that direction! I removed the xmlns=”” from the schema and it compiled!

                <xs:schema id="levelone" xmlns="" xmlns:xs="http://www.w3.org/2001/XMLSchema&#8221; xmlns:msdata=”urn:schemas-microsoft-com:xml-msdata”>[/b]

            • Author
              Replies
            Viewing 3 reply threads
            • The forum ‘Cloverleaf’ is closed to new topics and replies.