KMLM List
View email archives for the history of this mailing list.
|
|
|
|
sushidevelopers - RE: [sushidevelopers] COUNTER XML - three questions
|
Message Thread:
Previous |
Next
|
- To: <sushidevelopers@xxxxxxxxxxxxx>
- From: "Arndt, Dave (LNG-DAY)" <dave.arndt@xxxxxxxxxxxx>
- Date: Fri, 17 Apr 2009 12:44:55 -0400
- Send Email to sushidevelopers@list.niso.org:
- Send new message
- Reply to this message
|
More of a SOAPBox comment :-)
I think many folks will continue to have confusion around the
authentication and name/address/email type information that is put in
the "working" part of the SUSHI payload. Are they to be used for
service or end user authentication? If so which parts?
I believe part of the information in the Requestor and Customer
Reference sections are intended to be used for authentication but don't
provide the SUSHI provider with enough information to do the actual
authentication due to the fact that each SUSHI provider may need
different authentication information and furthermore each client might
want different types of authentication supported for a single SUSHI
provider. Think about all the different types of authentication there
is out there right now.
In my opinion the information in the requestor and customer reference
sections of the request should be purely informational and SUSHI should
defer the implementation of both service authentication and end user
authentication to the SUSHI provider.
I have almost the similar views on platform.
Thanks,
Dave Arndt - Elsevier Services Architect
937-865-6800 x56221
Web Services, Customer System, Reporting and DW
www.sciencedirect.com www.scopus.com
"The significant problems we have cannot be solved at the same level of
thinking with which we created them." Albert Einstein
-----Original Message-----
From: Colin Prince [mailto:colin.prince@xxxxxxxxxxx]
Sent: Friday, April 17, 2009 10:17 AM
To: sushidevelopers@xxxxxxxxxxxxx
Subject: [sushidevelopers] COUNTER XML - three questions
Hello Everyone,
I'm putting together a COUNTER XML report and referencing the schema
here: http://www.niso.org/schemas/sushi/counter3_0.xsd
Attached is my first attempt, report.xml. I'd be grateful for any
comments.
It's not clear to me what I could put in the ItemPlatform element.
From the docs:
"The platform is the name of the online host as determined by the
service provider, e.g., EBSCOhost, ScienceDirect, etc."
We host journals at the University of Toronto Libraries using OJS
software. There are many different publishers.
Perhaps "University of Toronto Libraries" is the platform, or is it
"OJS" maybe?
Two more questions regarding XML details:
Should the ItemPerformance instances be symmetrical, that is, if I put
ft_html in one ItemPerformance instance, do I have to make sure it is in
all of them?
If we do not have a particular piece of data, is it preferable to skip
the element, put an empty element, or put an element containing the
integer zero?
Thanks,
Colin
--
Colin Prince
416-978-7636
Scholarly Communication Initiatives
University of Toronto Libraries
|
|
By Date:
Previous |
Next
|
Current Thread
|
By Thread:
Previous |
Next
|
|
RE: [sushidevelopers] COUNTER XML - three que, Arndt, Dave (LNG-DAY) (you are here)
|
|
|
Mail converted by the most-excellent MHonArc 2.6.16
|