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

RE: First alpha release of Europeana's Annotation API

From: Hugo Manguinhas <Hugo.Manguinhas@europeana.eu>
Date: Thu, 19 Nov 2015 11:23:50 +0000
To: Doug Schepers <schepers@w3.org>, W3C Public Annotation List <public-annotation@w3.org>, public-openannotation <public-openannotation@w3.org>
Message-ID: <6D0598B03E7E9848A4287E110919B4BA0112BF01@MBX-SRV-P200.wpakb.kb.nl>
Hi Doug, Benjamin, all,

Thanks for your great feedback and reaction to our work! It makes us very happy to have finally something concrete to show and to discuss with the group.

... here are the answers to your coments:

http://test-annotations.europeana.eu/annotations, I'm getting a 404 for that URL in the browser.

Hugo: We havenˇ¦t implemented yet the GET methods for the annotation containers such as the main endpoint. We chose to leave their implementation for last as we needed to quickly progress with the basic functionality and the application scenarios that we wish to support... but their are definitely in our todo list.

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ˇK)

Hugo: About the content that we hold, it is available in the portal (http://www.europeana.eu/portal/) and machine accessible through our APIs (http://labs.europeana.eu/api), see also this record for a kind of Trombone in the current portal (http://www.europeana.eu/portal/record/09102/_UEDIN_214.html). The endpoint itself is a separate system that will hold annotations and will power the new portal which is currently under development. About the HTML view of the annotation API, we will probably redirect all HTML request to the Swagger console.

Note that this URL (and all the others you mention) works fine: http://test-annotations.europeana.eu/

Hugo: thanks for pointing it out! this is actually the old console which was purely based on HTML... we will need to redirect it to the new Swagger console.

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]? 

Hugo: the new portal will show annotations made by end-users that can both come directly from the portal (the new one) but also from other platforms that display data that is on our collections.

Or on HistoryPin itself?

Hugo: we have developed as part of our Ev3 project a roundtrip daemon that harvests annotations from HistoryPin.org for objects that came from Europeana and stores/updates them in the AnnotationAPI. It is also envisioned that the daemon will do the reverse process (from our API to HistoryPin) once we have annotations that we can share.

Another follow-upˇK does this mean that HistoryPin is also creating annotations in Web Annotation Model format, or do you somehow mediate/transform their annotations?

Hugo: HistoryPin has their own internal data model but we worked with them to have a way of exporting the data following the Web Annotation Data ModelˇK the roundtrip daemon will still need to do some quality checks and adaptations of some URIs in the data before the annotation is actually stored in the server. btw, we used the oa:equivalentTo to represent the link between the annotation we store in our server and the annotation that can be seen at the HistoryPin portal, but we were discussion on changing it to prov:wasDerivedFrom.

Or are you just intending to serve as a repository for other annotation clients to consume and display your content?

Hugo: the API will be publicly available for reuse, so that other applications can use the annotations (the ones that the user defines as public) for their own purposes. btw, this will allow our data providers a means to access and take advantage of annotations made for objects that they hold. 

Either way is interesting, and I'm curious which direction you're taking.

Hugo: Thanks!

Kind regards,
Hugo

________________________________________
From: Doug Schepers [schepers@w3.org]
Sent: 18 November 2015 18:58
To: Hugo Manguinhas; W3C Public Annotation List; public-openannotation
Subject: Re: First alpha release of Europeana's Annotation API

Hi, HugoˇV

Another followupˇK does this mean that HistoryPin is also creating
annotations in Web Annotation Model format, or do you somehow
mediate/transform their annotations?

ThanksˇV
ˇVDoug

On 11/18/15 12:50 PM, Doug Schepers wrote:
> Hi, HugoˇV
>
> Congratulations and thanks! It's great to see uptake of our specs!
>
> A few comments inlineˇK
>
> 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ˇK)
>
> 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ˇK 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ˇV
> ˇVDougˇÚ
>
Received on Thursday, 19 November 2015 11:26:02 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 19 November 2015 11:26:02 UTC