Tags

[Henry Barnett]

Hi,
I'm working with FpML and I'm not very knowledgeable about xml when it comes
to standards and what is allowed and was hoping if you guy could answer a
quick question I have.

I have a message as follows
<fpml:ModifyTradeConfirmation xsi:type="fpml:ModifyTradeConfirmation"...>
...
</fpml:ModifyTradeConfirmation>

Which fails validation because xmlbeans expects
<fpml:FpML xsi:type="fpml:ModifyTradeConfirmation"...>
...
</fpml:FpML>

Is the first instance valid considering that fpml:ModifyTradeConfirmation
extends fpml:FpML?

Regards,
Henry


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@...
For additional commands, e-mail: user-help@...

[Jacob Danner-2]

It doesn't exactly work like that. The xsi:type is there to assert its
an elements type, but it does not mean two elements are then
equivalent only that they should conform to the type defined by the
schema. The element names are the key here.

If you are using XMLBeans and you want your FpML document, start
working with the type FpMLDocument type.
HTH,
-jacobd


On Wed, Jul 2, 2008 at 7:58 AM, Henry Barnett <hba@...> wrote:

> Hi,
> I'm working with FpML and I'm not very knowledgeable about xml when it comes
> to standards and what is allowed and was hoping if you guy could answer a
> quick question I have.
>
> I have a message as follows
> <fpml:ModifyTradeConfirmation xsi:type="fpml:ModifyTradeConfirmation"...>
> ...
> </fpml:ModifyTradeConfirmation>
>
> Which fails validation because xmlbeans expects
> <fpml:FpML xsi:type="fpml:ModifyTradeConfirmation"...>
> ...
> </fpml:FpML>
>
> Is the first instance valid considering that fpml:ModifyTradeConfirmation
> extends fpml:FpML?
>
> Regards,
> Henry
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@...
> For additional commands, e-mail: user-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@...
For additional commands, e-mail: user-help@...

[Henry Barnett]

Hi,
Thanks for your swift response, I have constructed some FpML documents with
the FpMLDocument type but at the moment I am validating xml that will be
coming from external systems. I need to know if I should tell them they have
to use the <fpml:FpML...> tag with the xsi:type or if they can use the tag
<fpml:ModifyTradeConfirmation ...> as they already are.
Could you tell me if it is ok by xmlbeans standard that they have to use the
first of the two?

Regards,
Henry

-----Original Message-----
From: Jacob Danner [mailto:jacob.danner@...]
Sent: 02 July 2008 16:53
To: user@...
Subject: Re: Tags

It doesn't exactly work like that. The xsi:type is there to assert its
an elements type, but it does not mean two elements are then
equivalent only that they should conform to the type defined by the
schema. The element names are the key here.

If you are using XMLBeans and you want your FpML document, start
working with the type FpMLDocument type.
HTH,
-jacobd


On Wed, Jul 2, 2008 at 7:58 AM, Henry Barnett <hba@...> wrote:
> Hi,
> I'm working with FpML and I'm not very knowledgeable about xml when it
comes

> to standards and what is allowed and was hoping if you guy could answer a
> quick question I have.
>
> I have a message as follows
> <fpml:ModifyTradeConfirmation xsi:type="fpml:ModifyTradeConfirmation"...>
> ...
> </fpml:ModifyTradeConfirmation>
>
> Which fails validation because xmlbeans expects
> <fpml:FpML xsi:type="fpml:ModifyTradeConfirmation"...>
> ...
> </fpml:FpML>
>
> Is the first instance valid considering that fpml:ModifyTradeConfirmation
> extends fpml:FpML?
>
> Regards,
> Henry
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@...
> For additional commands, e-mail: user-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@...
For additional commands, e-mail: user-help@...



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@...
For additional commands, e-mail: user-help@...