KMLM List

[Oliver Pesch <OPesch@xxxxxxxxx>]

The COUNTER-SUSHI schema is what you use for developing. When you examine it, you will see that it is what connects the COUNTER schema to the SUSHI schema to allow SUSHI to deliver COUNTER reports.

 

SUSHI is flexible in that it can carry different kinds of reports; therefore, the report itself is not represented in the SUSHI schema.  An overriding schema is used to join the report with SUSHI…  for example the Cost of Resource Exchange working group wanted to use SUSHI to deliver e-resource cost information so they developed a CORE schema to describe the “report” and a CORE-SUSHI schema to bind the report to SUSHI.

 

Best regards

Oliver

 

From: sushidevelopers@xxxxxxxxxxxxx [mailto:sushidevelopers@xxxxxxxxxxxxx] On Behalf Of Anna Bassols
Sent: Thursday, January 31, 2013 4:02 AM
To: sushidevelopers@xxxxxxxxxxxxx
Subject: [sushidevelopers] advantages/disadvantages XML schema

 

Hi all,

 

We are planning to develop COUNTER project this year. An I have a question about XML Schema.

 

SUSHI supports differents  XML schemas and we will need to choose one of them:

 

- SUSHI Core Schema and WSDL

- COUNTER-SUSHI Schema and WSD

- COUNTER Schema

 

(http://www.niso.org/schemas/sushi)

 

It would be possible if you could let me know the advantages/disadvantages of each one.

 

Any help will be greatly appreciated.

 

Thanks,

Anna

EBSCO Industries

This email and any files transmitted with it are confidential and solely for the use of the intended recipient. It may contain information which is covered by professional or other privilege. If you 
are neither the intended recipient of this email nor the person responsible for delivering it to the intended recipient, be advised that you have received this email in error and that any use of it is strictly 
prohibited. Please notify the sender immediately by reply email and then delete it from your system. EBSCO accepts no liability for any loss or damage suffered by any person arising from the use of this email. 

Please consider the environment before printing this email.