White spaces in token area of xsd - error when importing xsd as ext. def.

[Former Member]

Hello,

we are not sure about this issue.

This is how an area of the xsd (unfortunately an xsd of a published standard message format of german government!)

is defined that we need to import as an external definition:

<xs:complexContent>

<xs:restriction base="tns:WLT_String">

<xs:sequence>

<xs:element name="content">

<xs:simpleType>

<xs:restriction base="xs:token">

<xs:enumeration value="Allgemeine Fahrerlaubnis (§ 5 StVZO) " />

<xs:enumeration value="Dienstfahrerlaubnis-Klassen (bisheriger § 5 i. V. m. § 14 StVZO)" />

<xs:enumeration value="Dienstfahrerlaubnis-Klassen (§ 6 i. V. m. § 26 FeV)" />

<xs:enumeration value="Dienstfahrerlaubnis-Klassen Bundeswehr (bisheriger § 5 i. V. m. § 14 StVZO)" />

</xs:restriction>

</xs:simpleType>

</xs:element>

</xs:sequence>

<xs:attribute name="wl_fassung" type="xs:string" use="optional" default="0" />

<xs:attribute name="wl_version" type="xs:string" use="required" fixed="1.1" />

</xs:restriction>

</xs:complexContent>

So we can see this defintion:

<xs:restriction base="xs:token">

which means per definition:

xsd:token: normalizedString w/o 2 white spaces succeeding and w/o white spaces at start and end.

But you can see that the enumerations contain 2 white spaces succeeding or white space at the end.

Impporting this xsd as an external definition into PI will fail.

So it looks like PI is doing a very restricitve check of the values against the token definition.

We would expect that any xml editor would do the same check but behaviour of xml editors is different means accepting this xsd.

So is it correct that PI is more restrictive at the latest during activation of such an xsd?

This results in the situation that official standard xsds will be used by governement with other tools but only interfaces with PI will fail..

Any ideas how to run with that issue?

Regards

Dirk

[markangelo_dihiansan · Accepted solution]

Hello,

Your issue looks like the one described in this page:

http://www.xmlplease.com/normalized

For reference purposes, here is the link for the supported schema and wsdl in PI 7.1

http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00a9a425-1769-2a10-9196-bd8eeed72...

As a temporary work around, you can try editing the xsd by removing the spaces before importing it into PI.

Hope this helps,

Mark

[Former Member · Accepted solution]

Thanky Mark, for the provided links.

This makes the situation more clear.

So from my understanding it is really a problem with the XML editor the partner is using and the more restrictive way of PI handling xml.

We already followed your recommended work around.

Regards

Dirk