n Nitin
on

 

Hi i am getting this error when using OCC 2.01 and define v2.0. I have following statements in the define similar to CDISC example:

<ODM

    xmlns="http://www.cdisc.org/ns/odm/v1.3" 

    xmlns:xlink="http://www.w3.org/1999/xlink"

    xmlns:def="http://www.cdisc.org/ns/def/v2.0"

 

Thanks.

Forums: Define.xml

j Jozef
on June 16, 2015

You might want to add the following on the ODM element:

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

However, this namespace declaration is only required if you also have:
xsi:schemaLocation="..."

As is well explained in the define.xml 2.0 specification on page 52, section 5.3.3.

I also encourage you to first validate your define.xml file against the XML-Schema. This should ALWAYS be the first validation step. If you do indeed really have a missing namespace declaration, schema validation will also tell you for which elements or attributes the namespace declaration is missing.

n Nitin
on June 17, 2015

Hi, I don't have namespace xsi:schemaLocation="..." but for some reason i do not get this error anymore either. I am using style sheets and schema's provided in the define 2.0 example from CDISC. Do i still need to validate define against schema? if so how do i do that?

Thanks.

j Jozef
on June 17, 2015

Well, I cannot force you to ...

How XML-Schema validation for define.xml can be done is very well explained in the "XML Schema Validation White Paper" published by CDISC at: http://cdisc.org/define-xml . The white paper is still for define.xml 1.0 (we are currently working on a new version), but essentially everything still applies, except that you now need to validate against define2-0-0.xsd.

Not a bad idea to start learning principles of XML, namespaces and schema validation though. I teach it to my undergrade students in just 2x 1.5 hours...

Want a demo?

Let’s Talk.

We're eager to share and ready to listen.

Cookie Policy

Pinnacle 21 uses cookies to make our site easier for you to use. By continuing to use this website, you agree to our use of cookies. For more info visit our Privacy Policy.