KMLM List

[Allan Conybeare <Allan.Conybeare@xxxxxxxxxxxxxxxxx>]

Hi,

 

I’m having a bit of difficulty with the sushi1_6.xsd schema and wondered if anyone has any thoughts.

 

I’ve used the EBSCO SDK to develop my service. When I query my web service for the WSDL (http://services_test.portlandpress.com/sushi/sushicounterservice.svc?wsdl) and XSD (http://services_test.portlandpress.com/sushi/sushicounterservice.svc?xsd=xsd1) the returned xsd shows the attributes as elements.

 

Here is the relevant snippet from the XSD (sushi1_6.xsd) -

 

Code:

...

<xs:complexType name="ReportRequest">

                <xs:annotation>

                                <xs:documentation/>

                </xs:annotation>

                <xs:sequence>

                                <xs:element type="s:Requestor" name="Requestor">

                                                <xs:annotation> <xs:documentation>Consumer of the service (client).</xs:documentation> </xs:annotation>

                                </xs:element>

                                <xs:element type="s:CustomerReference" name="CustomerReference">

                                                <xs:annotation> <xs:documentation>Identity of the customer for which data is requested</xs:documentation> </xs:annotation>

                                </xs:element>

                                <xs:element type="s:ReportDefinition" name="ReportDefinition">

                                                <xs:annotation> <xs:documentation>Report paramters including report name, version and filters (e.g. date ranges)</xs:documentation> </xs:annotation>

                                </xs:element>

                </xs:sequence>

                <xs:attribute type="xs:dateTime" name="Created">

                                <xs:annotation> <xs:documentation>Date/time the request was created</xs:documentation> </xs:annotation>

                </xs:attribute>

                <xs:attribute type="xs:string" name="ID">

                                <xs:annotation> <xs:documentation>Identifier may be provided by client application for internal use/diagnostics.</xs:documentation> </xs:annotation>

                </xs:attribute>

</xs:complexType>

...

 

Here is the same snippet after the call to http://services_test.portlandpress.com/sushi/sushicounterservice.svc?xsd=xsd1

 

createdField and idField below should be attributes not elements?

 

Code:

...

<xs:complexType name="ReportRequest">

                <xs:sequence>

                                <xs:element name="createdField" type="xs:dateTime"/>

                                <xs:element name="createdFieldSpecified" type="xs:boolean"/>

                                <xs:element name="customerReferenceField" type="tns:CustomerReference" nillable="true"/>

                                <xs:element name="idField" type="xs:string" nillable="true"/>

                                <xs:element name="reportDefinitionField" type="tns:ReportDefinition" nillable="true"/>

                                <xs:element name="requestorField" type="tns:Requestor" nillable="true"/>

                </xs:sequence>

</xs:complexType>

...

 

Any help will be greatly appreciated.

Cheers Al

Portland Press Ltd registered in England and Wales No. 2453983.

Registered Office: Charles Darwin House, 12 Roger Street, Third Floor, London, WC1N 2JU.

VAT registration number GB 523 2392 69. Portland Customer Services is a division of Portland Press Ltd.

The contents of this email are for the recipient only.

If you are not this person (or not responsible for delivery to this person), then notify the sender and delete the email immediately.

Any opinions contained in this message are those of the author and are not given or endorsed by Portland Press Ltd or the division through which this message is sent unless otherwise clearly indicated in this message.

Charles Darwin House, 12 Roger Street, Third Floor, London, WC1N 2JU