[ebxml-dev] Schema Problem?

[Vijaya Kumar <nmvijay@SAMSUNGSDSINDIA.com>]

Hi all,

once again the same question.

when i try to validate the ebXML message ( according to ebXML MS 1.0
spec) using the fallowing schema loaction
http://www.oasis-open.org/committees/ebxml-msg/schema/draft-msg-header-0
0.xsd
i am getting the fallowing Exception

i tried other schemas like 
http://www.oasis-open.org/committees/ebxml-msg/schema/draft-msg-header-0
1.xsd
http://www.oasis-open.org/committees/ebxml-msg/schema/draft-msg-header-0
2.xsd

etc...

but they all fallow ebXML MS spec 2.0

1>	Error:  org.xml.sax.SAXParseException: Error: constraint 3.x.3:
Attribute 'form' cannot appear in element 'attribute'.
2>	Error:  org.xml.sax.SAXParseException: Datatype error: In
element 'eb:TimeToLive' : Value '22:20' is not legal value for
	current datatype. Year separator is missing or misplaced.
3>	Error:  org.xml.sax.SAXParseException: Attribute "eb:status"
must be declared for element type "eb:SequenceNumber".
4>	Error:  org.xml.sax.SAXParseException: Datatype error: In
element 'eb:SequenceNumber' : 0 is out of bounds:[ 1 <= X    ]


what i am doing is explained below.

2>	in my message the value in TimeToLive element is like this

<eb:TimeToLive>22:20</eb:TimeToLive>

is it wrong. i have given value according to what has been specified in
the spec. the sec says
7.2.2	mshTimeAccuracy
The mshTimeAccuracy parameter indicates the minimum accuracy a Receiving
MSH keeps the clocks it uses when checking, for example, TimeToLive.
Its value is in the format "mm:ss" which indicates the accuracy in
minutes and seconds.

3 & 4>	the sequenceNumber element is like this

<eb:SequenceNumber eb:status="Reset">0</eb:SequenceNumber>
what is the problem here?


according to spec
The SequenceNumber element is an integer value that is incremented by
the Sending MSH (e.g. 0, 1, 2, 3, 4...) for each application-prepared
message sent by that MSH within the ConversationId. The next value of
99999999 in the increment is "0". The value of SequenceNumber consists
of ASCII numerals in the range 0-99999999. In following cases,
SequenceNumber takes the value "0":
	1)	First message from the Sending MSH within the
conversation
	2)	First message after resetting SequenceNumber information
by the Sending MSH
	3)	First message after wraparound (next value after
99999999)
The SequenceNumber element has a single attribute, status.  This
attribute is an enumeration, which SHALL have one of the following
values:
*	Reset - the SequenceNumber is reset as shown in 1 or 2 above
*	Continue - the SequenceNumber continues sequentially (including
3 above)


thanks in advance

Vijay Kumar
Software Engineer.