W3C home > Mailing lists > Public > public-openannotation@w3.org > November 2015

Re: First alpha release of Europeana's Annotation API

From: Benjamin Goering <ben@livefyre.com>
Date: Wed, 18 Nov 2015 09:55:00 -0800
Message-ID: <CAA-ozNadjAJnnH8jDYO-kzVmGC6wgePg8-FDR3qi9EBn4oKUmQ@mail.gmail.com>
To: Doug Schepers <schepers@w3.org>
Cc: Hugo Manguinhas <Hugo.Manguinhas@europeana.eu>, W3C Public Annotation List <public-annotation@w3.org>, public-openannotation <public-openannotation@w3.org>
Congrats Hugo! Very cool.

--
Benjamin Goering
Founding Engineer @Livefyre <http://livefyre.com>
@bengo <https://twitter.com/bengo> - github.com/gobengo -
linkedin.com/in/benjamingoering
<https://www.linkedin.com/in/benjamingoering>


On Wed, Nov 18, 2015 at 9:50 AM, Doug Schepers <schepers@w3.org> wrote:

> Hi, Hugo–
>
> Congratulations and thanks! It's great to see uptake of our specs!
>
> A few comments inline…
>
> On 11/18/15 11:33 AM, Hugo Manguinhas wrote:
>
>> Hi all,
>>
>> We (the Europeana Foundation) finally have our annotation API in a state
>> that we can share with the group!
>>
>> The endpoint is available at
>> http://test-annotations.europeana.eu/annotation
>>
>
> I'm getting a 404 for that URL in the browser.
>
> Even if it's only intended as an endpoint for HTTP publications, there
> probably should be some user-readable response (and content) there, right?
> (I don't know the answer to this…)
>
> Note that this URL (and all the others you mention) works fine:
>
> http://test-annotations.europeana.eu/
>
> and you can use for the
>> moment “apidemo” as apikey. A user friendly interface of the API is
>> available at http://test-annotations.europeana..eu/docs/index.html
>> <http://test-annotations.europeana.eu/docs/index.html>, btw we use a
>> tool called Swagger for generating the REST interface and
>> documentation... also, if you would like to see a real annotation coming
>> from the HistoryPin.org plaform, here is the link:
>>
>> http://test-annotations.europeana.eu/annotation/historypin/136290?wskey=apidemo
>> .
>>
>
> Is it within the scope of your project to actually expose the annotations
> to end-users? For example, will the body of the "bus" annotation in your
> HistoryPin example be available on the "target" site [1]? Or on HistoryPin
> itself?
>
> Or are you just intending to serve as a repository for other annotation
> clients to consume and display your content?
>
> Either way is interesting, and I'm curious which direction you're taking.
>
>
> The version that is live follows the version prior to the one from 15th
>> October of the Web Annotation Data Model and the recently published spec
>> of the W3C Annotation Protocol... btw, we will be revising our
>> implementation soon to comply with the latest version. Besides the
>> general CRUD methods it has an additional method for search method for
>> discovering annotations. All methods have an additional flavour using
>> format extensions instead of the Accept Header. We did this to be
>> compliant with our other APIs which do not follow this practice.
>>
>> Finally, if you try to create an annotation in the server, please note
>> that we have only implemented some simple scenarios for now and will be
>> progressively supporting more complex ones as we start to agree on how
>> they should be represented… we followed a more restrictive approach so
>> that we can make sure that annotations coming from different client
>> applications are uniformly represented in the server and therefore shown
>> in our portal.
>>
>
> Makes sense.
>
> Again, this is very exciting!
>
> [1]
> http://www.europeana.eu/portal/record/9200257/BibliographicResource_3000055619928.html
>
> Regards–
> –Doug≠
>
>
Received on Wednesday, 18 November 2015 17:55:48 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 18 November 2015 17:55:49 UTC