First of all, thanks for taking the time to look at this. I've started to look at this, but I realize that right now, you know much more than me. So I will have to do a refresh of looking at our code for this before I will be able to respond to this email.
I will try to do this early next week. On Tue, Apr 10, 2012 at 10:36, Dmitry <[email protected]> wrote: > Q1. If there is no difference between <element> and <type> how to > distinguish them? > It looks like an element is represented as a ComplexTypeDescriptor with > one TypeDescriptor in its elements list (?) > Q2. When ArrayTypeDecriptor is used? Is it the "soapEncoding" thing or > there is a use for doc/lit also > I found that an element "id" is represented as an ArrayTypeDecriptor (?) > it is not unbound thought. > <part name="parameters" element="ns1:WhichNameSpaceForIDRequest"/> > <xs:element name="WhichNameSpaceForIDRequest" > type="tns:WhichNameSpaceForIDRequest"/> > <xs:complexType name="WhichNameSpaceForIDRequest" > > <xs:sequence> > <xs:element name="id" type="ns1:NemusObject" form="qualified" > minOccurs="0"/> > </xs:sequence> > </xs:complexType> > For the simple types/elements there is a BaseTypeDescriptor. I see no > support for the Unions and Lists. For the simple restriction a first (in > inheritance tree) XML Schema basic type is set as a type. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/ Developers Guide: http://www.taverna.org.uk/developers/
