Re: [ubl-dev] infinite loop

[Stephen Green <stephengreenubl@gmail.com>]

I do concur with Roberto too - the tools for XML, schemas, etc are
these days expected to
handle such loops gracefully and do so by having a limit which can
sometimes be set by the
user.

By the way, I thought some more about the example of the
Signature/../AgentParty/../AgentParty
and it does make sense when you think that an agent can appoint an
agent who can themselves
appoint an agent. Just like a contractor can appoint a subcontractor
who sometimes
can appoint a subcontractor...

Best regards

Steve
---
Stephen D Green




On 25 June 2010 09:57, Stephen Green <stephengreenubl@gmail.com> wrote:
> Hi Elisa
>
> If you think of it like in HTML where a table cell can
> contain a table which contains rows which contain cells ...
> but the difference is that UBL has to make everything
> explicit in the schema (apart from the Extension element)
> so the schemas get these loops. There's nothing abnormal
> about it. In terms of 'meaning' of the loops, it's a bit like
> having a family tree structure where parents 'contain'/have
> children who can themselves be parents having other children
> so any family tree structure will have endless loop possibilities.
>
> Best regards
>
> Steve
> ---
> Stephen D Green
>
>
>
>
> On 25 June 2010 08:53, elisa blasi <elisablasi@gmail.com> wrote:
>> Hi,
>> I' m working on UBL xsd files to obtain a tree viewer of the documents,but
>> the algorithm enter into an infinite loop because of the structure of the
>> xsd.
>> For example, in the Order document there is the element "Signature" of type:
>> Signature type. Signature type,that is a complex type, contains the element
>> "SignatoryParty" of type PartyType. PartyType, that is a complexType,
>> contains AgentParty that is a PartyType and will contain another AgentParty
>> element...and so on.
>> Is it true? I don't understand the meaning of these circular calls.
>> Regards Elisa
>>
>