KMLM List
View email archives for the history of this mailing list.
|
|
|
|
sushidevelopers - RE: [sushidevelopers] Values in XML Reports
|
Message Thread:
Previous |
Next
|
- To: Christian Jägle <christian.jaegle@xxxxxxxxxxxxxxxxxx>, <sushidevelopers@xxxxxxxxxxxxx>
- From: "Oliver Pesch" <OPesch@xxxxxxxxx>
- Date: Mon, 20 Jun 2011 09:56:28 -0500
- Send Email to sushidevelopers@list.niso.org:
- Send new message
- Reply to this message
|
This is a good suggestion... Some of the fields like "identifier" are in the
schema as "required"; however, the reality is this is more of a business
"requirement" than a technical one. The identifier is "required if there is
one"... which of course cannot be enforced in a schema. As a result, if there
is no ISSN available, then the empty tag needs to be included so that the XML
validates. "N/A" should never be used...
In terms of trying to enforce the nature and structure of the identifier value,
this can only be something for a profile or, at a minimum, the FAQ. Since the
identifier "types" include ISSN, ISBN, DOI and proprietary. The rules for the
value are determined by the "type"...
As we look at the COUNTER-4 XML I agree that fields that may not contain values
should be optional to avoid confusion -- and the "profile" should set
expectations for the values to be used.
Good input,
Thanks!
-----Original Message-----
From: sushidevelopers@xxxxxxxxxxxxx [mailto:sushidevelopers@xxxxxxxxxxxxx] On
Behalf Of Christian Jägle
Sent: Monday, June 20, 2011 9:48 AM
To: sushidevelopers@xxxxxxxxxxxxx
Subject: [sushidevelopers] Values in XML Reports
Hi,
I have a similar issue like in my last thread.
If you look through the xml reports, there often are element values,
where the vendor doesn't have a value or doesn't want to fill in a
value. Still the Elements are used in the report and in some cases they
are not needed to fullfill the schema.
A good example and the main reason for my post is the ItemIdentifier
Element. You often see "N/A" or an empty string or an Element in
minimized syntax form (<Value/>) as value, even if there already is an
ItemIdentifier given.
The question is if it shouldn't be more precise outlined what strings
those elements should contain or if they have to be ommited if there is
no information and the report would be valid without them?
Maybe there is still time left to consider this and similar issues for
the COUNTER 4 release and the mentioned "Community Profile".
Christian Jägle
--
Christian Jägle
Albert-Ludwigs-Universität Freiburg
Universitätsbibliothek
Rempartstraße 10-16 | Postfach 1629
D-79098 Freiburg | D-79016 Freiburg
Telefon: +49 761 203-3886
E-Mail: christian.jaegle@xxxxxxxxxxxxxxxxxx
Internet: www.ub.uni-freiburg.de
CONFIDENTIALITY NOTICE
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.
|
|