The Zotero API can now export CSL input data for items, either directly
('format=csljson') or embedded within Atom ('content=csljson').
e.g.,
https://api.zotero.org/groups/1/items/top?pprint=1&limit=5&itemType=journalArticle&format=csljson
We're currently serving direct output with the MIME type
application/vnd.citationstyles.csl+json, but we should come to a
consensus on the type to use. (Note that the pprint=1 above forces
text/plain for easier display in browsers.)
I don't have a strong preference here, but here's a rational for
application/vnd.citationstyles.csl+json:
1) "vnd." instead of "x-" per
http://tools.ietf.org/id/draft-saintandre-xdash-considered-harmful-01.txt
2) "citationstyles" instead of "csl" for uniqueness and for consistency
with citationstyles.org
3) "csl+json" because it's JSON data and because everyone calls it "CSL
JSON" already
The argument against #3 is that application/vnd.citationstyles.csl+xml
could be used (in lieu of the current text/x-csl) for CSL styles
themselves, and one could object to having csl+json and a potential
csl+xml refer to two entirely different types of data (rather than, say,
different representations of the same data). An alternative would be
"citeproc+json", since, even though "citeproc" isn't mentioned in the
CSL spec, it's the prefix for all or nearly all of the existing (public)
processors that use this data. But since we rarely call it "citeproc
JSON" anywhere else, it's a little strange to do so in the media type.
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
