XML

  • Creator
    Topic
  • #51286
    Bill May
    Participant

    Dear Clovertechers,

    I’m having some difficulty with and xml/xsd file combination

    The xml validates against the xsd in XML Spy and the xsd compiles in Cloverleaf

    However when I try to run it in the testing tool

    I get

    [0:TEST] Error generated during parsing. – No character data is allowed by content model – Line 143, Col 26

    Is there any way of tracking down exactly what is causing this error ?

    Cheers,

    Bill

Viewing 5 reply threads
  • Author
    Replies
    • #69542
      Bill May
      Participant

      Dear Clovertechers,

      I’ve attached a copy of the xsd and xml files I’m using

      Just in case anyone wanted to test

      Cheers,

      Bill

    • #69543
      Charlie Bursell
      Participant

      Bill:

      f you look at the error message, it tells you which line in the file it does not like.  Forexample NTE.3.  If you fix that one you will find it does not like OBX.5 as well.

      I’ll leave it up to you to fix the schema, I do not have the time.  I believe the problem with the OBX.5 field is it is defined a “varies” datatype.  I.m not sure if that type is yet supported,

      The NTE.3 field is defined as datatype FT.  I don’t know what that is

      Good luck with it and welcome to the world of XML  😀

    • #69544
      Robert Milfajt
      Participant

      Charlie, I read the HL7 2.5.1 spec for NTE-3, and FT replaces TX sometime prior to that version.  Something about allowing for escape characters.

      I got to the same place Charlie did, NTE-3 is the culprit, but why?  If the parser is having a problem with the FT datatype, change it to TX and see iif that works.

      OBX-5 varies, because it’s type is determined by OBX-2 (value type).  I wonder if you could just define it as text and it would work as well.

      Hope this helps,

      Robert Milfajt
      Northwestern Medicine
      Chicago, IL

    • #69545
      Bill May
      Participant

      Thanks

      I am still a little confused

      How is it that this validates fine in XMLSpy2008 but when I try it in Cloverleaf I start getting all these errors ?

      The customer has also validated it in XMLSpy 2009

      Why does Cloverleaf have problems

      Should I try 5.8 ?

      Cheers,

      Bill

    • #69546
      Charlie Bursell
      Participant

      I turned this over to the R&D XML guru and she said:

      “I took a look at the schemas.

      It looks like in the Xerces parser, the NTE.3 field doesn

    • #69547
      Charlie Bursell
      Participant

      Attachment did not make it

      Having trouble with it.  I will mail to you

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

Forum Statistics

Registered Users
4,966
Forums
28
Topics
9,106
Replies
33,627
Topic Tags
248