These are quite possible. For the former, look to the Wikpedia
> * To be able to capture the reference information in wiki syntax to
> expose it back as OpenURL COinS
> * To be able to request the rich text version under a specific
> formatting (ie Harvard) in rich text (HTML works), to preserve
> consistency on the website
Citation Templates [1] export translator for some inspiration. You
may even want to add support for WP citation templates to Tikiwiki, to
be able to benefit from tools other than Zotero. If you do want to
make a custom exporter, you might first look into the citation style
language [2]. The citation style would be easier to program and
maintain and still works with the zotero quick copy [3]. If you
really want rich text to be output into regular HTML forms, it may be
appropriate to make a zotero plugin [4] (because this is most often
not what is desired)
[1] https://www.zotero.org/trac/browser/extension/trunk/translators/Wikipedia%20Citation%20Templates.js
[2] http://www.zotero.org/support/dev/creating_citation_styles
[3] http://www.zotero.org/support/creating_bibliographies#quick_copy
[4] http://www.zotero.org/support/dev/sample_ Export translator seems to be the right concept.plugin
Given that the OO.o export is built within your software, it would
> * When copying back in OpenOffice.org, it would be nice if references
> were converted from the OpenURL tags
seem that you would need to build this capability in if you wanted
it. I don't see how the Zotero client would be of much help.
There is a server-side API as well. There is some unofficial
> 1. Get the users to input some reference ID, query the Zotero API from
> the backend. Obviously, I then realized that the server was solely
> used for synchronization and that the API were client side.
documentation already & official documentation is forthcoming.
What do you expect that call-back to do, precisely? It seems to me
> 3. Register a callback for Zotero to call when dropping a source.
> Firefox extensions won't let you do that as I could find. However,
> that lead me to adding a listener on a custom event, which seems
> reasonable.
that you could create either a CSL file or an export translator to
format a dropped reference properly.
Hi -
Apologies in advance for thread hi-jacking.
Respectfully, I don’t think COinS is a good option. It is not a
standard or recommendation or internet draft, it is a very convoluted
way to embed metadata in HTML, and I don’t myself care about or use
OpenURL, so any time spent learning its idiosyncrasies is time wasted.
I am not happy with unAPI, either, though I like it much more than
COinS. It uses a custom, unAPI-specific mechanism which could easily
be replaced with links, plain old HTTP, and content negotiation. While
not particularly difficult to implement, it is harder than it could
be, and the time spent coding it is not easily reused for linked data
applications. It is, as far as I can tell, supported on the client
side only by Zotero.
If I visit “Make your site Zotero ready” [1], it is suggested that I
use one of the two above options. For a project I am working on, what
I would like to do is be able to leverage work done to support linked
data to also support Zotero. Some thoughts about this follow.
For instance, how could I let Zotero know how to get metadata for an
item using content negotiation or, alternately, a different URI? In a
linked data sense, if I have a URI A which represents a book (the
non-information resource), and A' which is the HTML describing the
book, how can I let Zotero know when a user is viewing A' that there
exists an alternative representation of A' that provides
machine-readable metadata about A?
For instance, I can imagine supplying, in the HTML <head>,
<link rel="alternate" type="application/rdf+xml" href="...">
to let Zotero know that an RDF representation of information contained
at A' was available at a given location.
On a page that represents search results, I can imagine using:
<div xmlns:dc="http://purl.org/dc/elements/1.1/"
about="/a_book">
<span property="dc:creator">John Doe</span>.
<a href="/a_book"><span property="dc:title">A book</span>.</a>
<a type="application/rdf+xml" href="/a_book"/>
</div>
A little complicated, true, combining RDFa with links to more
information, but it gives some metadata about a book and a link to the
full metadata about the book.
While I have in the past done extra work to support Zotero, by
implementing unAPI, I would prefer, going forward, to be able to save
development time by re-using linked data work for Zotero. I don’t
think this should be difficult, but I don’t see a way to do it in
Zotero as it currently stands. I am willing to work on translators to
support this, but I want to get some feedback from the community first
as to the best way forward with this.
Thanks for Zotero, and thanks for reading this!
best,
Erik Hetzner
1. http://www.zotero.org/support/make_your_site_zotero_ready
I am not sure if I am looking at an overhaul. I would like to have the
following extractors for Zotero:
1. An easy way to link to machine-readable metadata in a form that
Zotero understands, (e.g., MARC or MODS), for instance with a <link>
element.
2. An extractor for RDFa, probably using bibo ontology.
I believe that (1) would be simpler to implement than unAPI, and more
in tune with linked data, and (2) is a good way forward for embedded
data in HTML, again in tune with linked data.
Thanks for all the responses. I am sorry that these have not been
implemented previously, but as it sounds like there is interest, I
will begin looking at implementation.
best,
Erik
Hi -
This makes me realize that it would be great if Zotero could output
HTML with embedded RDFa that could be imported back into Zotero.
I will look at using the python csl HTML output as initial input for
an RDFa Zotero translator.
best, Erik
Hi -
I don’t want to encourage or discourage anybody else from using COinS
or unAPI, if it works for you. I myself think there is a better way,
and would like to make that possible, but I am very happy that Zotero
does not demand that web pages conform to it, but is willing to
conform to web pages in order to extract the metadata it requires.
(As an aside, you might find that unAPI is only a little more work
than COinS, but that being able to generate richer metadata than COinS
makes your job easier in the long term.)
My concern is that a user interested in supporting linked data &
Zotero is not able to repurpose code used to support the former to
help support the latter, and vice versa.
best, Erik
Unless I am mistaken, you could output:
<span property="address:localityName" content="Oakland, CA"/>
But there is no requirement that RDFa embed all triples, so you could
simply link to a fuller representation and exclude the place. I do not
know which solution is best.
best, Erik
This would be very helpful. I'll need examples in order to begin
working on RDFa support in the citeproc-js processor.
Frank
Yes, please do put RDFa examples on the bibliontology page. It will
make it much easier to get a Zotero translator up & running. Thanks.
best, Erik
I forwarded this to the BIBO list.
FWIW, Frank, you can take a look at my get_property function to get a
sense of how I'm tackling this:
<http://github.com/bdarcus/citeproc-py/blob/master/citeproc.py>
I use a hash/dict to map CSL variable names to the equivalent RDF/BIBO
structures.
Bruce
Thanks. The function gives mappings for a dozen variables. If it can
be filled out for the 50 or so remaining, that would be great.
>
> Bruce
On my TODO.
On May 26, 2010 4:49 PM, "Frank Bennett" <bierc...@gmail.com> wrote:
On May 27, 3:03 am, "Bruce D'Arcus" <bdar...@gmail.com> wrote:
> On Wed, May 26, 2010 at 10:42 AM, Erik Hetzner <ehetz...@gmail.com> wrote:
> > At Wed, 26 May 2010...
Thanks. The function gives mappings for a dozen variables. If it can
be filled out for the 50 or so remaining, that would be great.
>
> Bruce
--
You received this message because you are subscribed to the Google Groups "zotero-d...
<article class="article-text">
<header>
<h1 property="dc:title">BP's Photo Blockade of the Gulf
Oil Spill</h1>
<h2 class="subhead"
property="dc:description">Photographers say BP and government
officials are preventing them from documenting the impact of the
Deepwater Horizon disaster.</h2>
</header>
Raises the point that RDFa support in Zotero would want to be flexible
about what sorts of properties and such they'd want to understand
(Newsweek isn't using BIBO; just DC, FOAF, SIOC).
Bruce
Last night I put together the beginnings of an RDFa translator for
Zotero, using the RDFa implementation in JS available at [1].
This morning I noticed that Zotero has it’s own RDF store, Zotero.RDF.
If I can modify the RDFa parser to parse into this, it seems I could
use existing RDF translators to parse the RDF graph into Zotero items.
However, so far I have been unable to access Zotero.RDF. I believe
this may be because I am on a page that is not RDF/XML. Here is the
error:
Zotero(2): Translate: Translation using RDFa failed:
message => Zotero.RDF is undefined
and attached is a minimal translator. Any thoughts? Thanks!
best, Erik
Just guessing, but try adding Zotero.configure("dataMode", "rdf"); to
the translator. That appears to add Zotero.RDF to the sandbox (in
translate.js).
Oh, sorry, you have that already. Don't know, then.
<http://www.w3.org/TR/2010/WD-rdfa-api-20100608/>
Bruce
Thanks for the link. It does not appear to have any implementations
yet. If/when it is implemented we could probably use it.
However it did lead me to an alternate RDFa javascript parser which
may be better than the one I was using. [1]. We’ll see.
best, Erik
Hi Simon,
Thanks for the very fast response. I needed to change the UUID to:
translator.setTranslator("5e3ad958-ac79-463d-812b-a86a9235c28f");
But it works great.
Would it be possible to dump the data from one Zotero.RDF to the
other, rather than parse the RDFa twice, if I understand you
correctly?
best, Erik
Thanks, Simon. I will do that.
If you have the time, another feature I would like to enable is
fetching alternative representations in RDF via linking as described
in [1], from HTML that looks like:
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<title>Alice's Homepage</title>
<link rel="alternate" type="application/rdf+xml"
title="RDF Representation"
href="http://www.example.com/data/alice" />
</head> ...
I haven’t yet figured how to do this; I’m hoping I can pass it off to
the RDF translator as well.
I only mention this to ask you to keep this use case in mind as well
when making any API additions.
best, Erik
How does this (conversation below about RDF, changes in 2.1) currently
stand? There was some chatter online today about RDFa, and it would be
nice to get at least some preliminary support into Zotero in the near
future.
Avram
2010/6/10 Erik Hetzner <ehet...@gmail.com>:
On Thu, Jun 10, 2010 at 12:20 PM, Erik Hetzner <ehet...@gmail.com> wrote:
> At Thu, 10 Jun 2010 12:05:47 -0400,
> Bruce D'Arcus wrote:
>>
>> I don't know if this has any relevance, but the W3C has just published
>> a draft of an RDFa DOM API document:
>>
>> <http://www.w3.org/TR/2010/WD-rdfa-api-20100608/>
>
> Thanks for the link. It does not appear to have any implementations
> yet. If/when it is implemented we could probably use it.
Here's a JS implementation (with notes that it is, or will be, node.js
compatible):
<https://github.com/webr3/rdfa-api>
Bruce
Hi Avram,
No progress here, I’m afraid. But the link Bruce sent out earlier
looks promising as a way forward for RDFa processing.
best, Erik