FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 1
Co-funded by the Horizo...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 2
REMINDER: WHAT IS FREME...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 3
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 4
FREME E-SERVICES – BIRD...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 5
EXAMPLE: E-SERVICE DESI...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 6
WHAT IS NIF?
• Natural ...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 7
NIF EXAMPLE: DESCRIBING...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 8
DESCRIBING STRINGS
<htt...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 9
STORING E-ENTITY ENRICH...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 10
KEEPING PROVENANCE
<ht...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 11
BENEFIT AND DRAWBACKS ...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 12
DEMO: COMBINING E-SERV...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 13
HIDING COMPLEXITY (1/2...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 14
HIDING COMPLEXITY (2/2...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 15
E-LINK EXAMPLE: TEMPLA...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 16
LINKED DATA AND LOCALI...
FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 17
CONTACTS
FELIX SASAKI
...
Nächste SlideShare
Wird geladen in …5
×

Freme at feisgiltt 2015 freme & linked data & localisers

699 Aufrufe

Veröffentlicht am

This presentation is a complement to
http://slideshare.net/atcfsenzoku/freme-at-feisgiltt-2015-freme-use-cases
It provides more details on processing of linked data in FREME, using NIF and with the FREME services e-Entity and e-Link

Veröffentlicht in: Internet
0 Kommentare
0 Gefällt mir
Statistik
Notizen
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

Keine Downloads
Aufrufe
Aufrufe insgesamt
699
Auf SlideShare
0
Aus Einbettungen
0
Anzahl an Einbettungen
28
Aktionen
Geteilt
0
Downloads
2
Kommentare
0
Gefällt mir
0
Einbettungen 0
Keine Einbettungen

Keine Notizen für die Folie
  • e-Translation: “Translate from Dutch to English”
    e-Terminology: “Add terminology annotations”
    e-Entity: “Identify unique entities”
    e-Link: “Add information from (linked open) data sources”
    e-Publishing: “Publish as digital book content”
    e-Internationalisation: “Use standardised metadata for multilingual content production”
    A KEY ASPECT FREME: FREME will allow to combine data and language technologies via adequate software interfaces (APIs) and graphical user interfaces (GUIs)
  • Back Page #1
    Social network icons refer to speaker (he/she has to link his/her accounts)
  • Freme at feisgiltt 2015 freme & linked data & localisers

    1. 1. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 1 Co-funded by the Horizon 2020 Framework Programme of the European Union Grant Agreement Number 644771 FEISGILTT 2015 |BERLIN, 3 JUNE 2015 Felix Sasaki, DFKI / W3C Fellow On behalf of the FREME Consortium FREME TO MAKE LINKED DATA AVAILABLE TO LOCALIZERS www.freme-project.eu
    2. 2. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 2 REMINDER: WHAT IS FREME? • More info: see presentation from yesterday http://slideshare.net/atcfsenzoku/freme-at-feisgiltt-2015-freme-use-cases • Design of FREME takes up work from other projects 1. LIDER http://lider-project.eu/ ◦ In FREME, we deploy best Practices on how to work with linguistic linked data (LLD) ◦ LLD: Linked data used to represent lexica, corpora, language processing workflows etc. 2. FALCON http://falcon-project.eu/ ◦ In FREME, we benefit from experience on working with linked data in localisation scenarios ◦ One lesson learned: hide linked data in the right way from (localisation) developers ◦ No need to process linked data always in the native form, see Babelfy http://babelfy.org/
    3. 3. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 3
    4. 4. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 4 FREME E-SERVICES – BIRDS EYE VIEW • e-Entity ◦ Automatic annotation of named entities • e-Terminology ◦ Annotation of terms and linkage to term databases • e-Link ◦ Enrichment with information from (linked) (open) data sources* • e-Translation ◦ Cloud based machine translation • e-Internationalisation ◦ ITS 2.0 metadata to govern the multilingual & semantic content workflow • e-Publishing ◦ Publish enriched content in ePub format
    5. 5. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 5 EXAMPLE: E-SERVICE DESIGN • RESTFul API • Example http://api.freme-project.eu/0.1/e-entity/dbpedia-spolight • Under each service endpoint: tool specific versions • Parameters for e-Entity ◦ Confidence threshold ◦ Informat. Currently text or NIF (explanation see next slides) ◦ Outformat. • Output: NIF in various serializations ◦ Currently text/turtle or application/json+ld
    6. 6. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 6 WHAT IS NIF? • Natural Language Processing Interchange Format • “The XLIFF of natural language processing workflows” (Phil Ritchie, FEISGILTT 2015) • NIF: Linked data based representation of digital content and NLP related annotations • Anchoring in source format possible -> basis for roundtripping • More info: see http://site.nlp2rdf.org/
    7. 7. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 7 NIF EXAMPLE: DESCRIBING DOCUMENTS @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . @prefix nif: <http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#> . <http://example.org/document/1#char=0,11> a nif:String , nif:Context , nif:RFC5147String ; nif:isString "the content"^^xsd:string; nif:beginIndex "0"^^xsd:nonNegativeInteger; nif:endIndex "11"^^xsd:nonNegativeInteger; nif:sourceUrl <http://differentday.blogspot.com/2007_01_01_archive.html> .
    8. 8. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 8 DESCRIBING STRINGS <http://example.org/document/1#char=0,21> a nif:String , nif:Context , nif:RFC5147String ; nif:isString "We talk about Xiamen."^^xsd:string; nif:beginIndex "0" nif:endIndex "21" nif:sourceUrl <http://differentday.blogspot.com/2007_01_01_archive.html> . <http://example.org/document/1#char=14,20> a nif:String , nif:RFC5147String , nif:Word, nif:Phrase; nif:referenceContext <http://example.org/document/1#char=0,21> ; nif:anchorOf "Xiamen" ; nif:beginIndex "14" ; nif:endIndex "20"; nif:wasConvertedFrom <http://example.org?t=url&f=html&i=http://somewebpage.com#char=0,2820> ;
    9. 9. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 9 STORING E-ENTITY ENRICHMENT <http://example.org/document/1#char=14,20> a nif:String , nif:RFC5147String , nif:Word, nif:Phrase; itsrdf:taIdentRef <http://dbpedia.org/resource/Xiamen> ; itsrdf:taClassRef <http://dbpedia.org/ontology/City> ; itsrdf:taClassRef <http://dbpedia.org/ontology/Settlement> ; itsrdf:taClassRef <http://dbpedia.org/ontology/PopulatedPlace> ; itsrdf:taClassRef <http://dbpedia.org/ontology/Place> . • NIF allows to add multiple annotations to content • No constraints on the structure of annotations
    10. 10. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 10 KEEPING PROVENANCE <http://example.org/document/1#char=0,21> … nif:wasConvertedFrom <http://example.com/?informat=html&intype=url& input= http://differentday.blogspot.com/2007_01_01_archive.html/ &xpath=/html/body[1]/h2[1]/span[1]/text()[1]>. • XPath only an example • nif:wasConvertedFrom can hold source format specific information • Can the the basis for round tripping
    11. 11. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 11 BENEFIT AND DRAWBACKS OF NIF Benefits • NIF can store all information of enrichment services ◦ e-Entity, e-Link, e-Terminology, e-Translation • Via NIF we can chain services easily ◦ No constraints on structures: NIF format constitutes general annotation structure Drawbacks • No tool support of heterogeneous input formats in current tooling ◦ Working on that  -> integration of Okapi and NIF tooling • Size of NIF annotations may be an issue ◦ State: currently gathering implementation experience
    12. 12. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 12 DEMO: COMBINING E-SERVICES VIA NIF • Try things yourself at http://api.freme-project.eu/doc/0.1/ Demo workflow: 1. Input: text 2. Processing via e-Entity 3. Output: NIF, input to step 4 4. Processing via e-Link 5. Output: NIF
    13. 13. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 13 HIDING COMPLEXITY (1/2): NIF AND E-SERVICE USER FREME version 0.1: service endpoints understand text only or NIF content http://api.freme-project.eu/0.1/e-entity/dbpedia-spolight • Future version: support additional formats via integrating Okapi into NIF ◦ Informat: HTML, XML, Word, PDF; … ◦ Outformat: NIF, in some cases (HTML, XML, …) roundtripping • API user sets input and output e.g. via Accept header • NIF is processed internally, “hidden from the user”
    14. 14. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 14 HIDING COMPLEXITY (2/2): THE CASE OF E-LINK • Many users don’t know linked data sources: ◦ What type of data is available? ◦ What linked data vocabularies are used: NIF, LEMON, … ◦ What queries do I need to get information of type X • FREME e-Link allows them to query linked data without looking at it ◦ Input: content plus a query template : “Find my all events close to a given entity” , “Find me all museums close to a given entity”, … ◦ Output: content enriched with information relevant to the query, also as JSON-LD • Concept of query templates: similar to “Schematron for information architects” approach, cf. George Bina at XML Prague 2015 http://archive.xmlprague.cz/2015/files/xmlprague-2015-proceedings.pdf#page=199
    15. 15. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 15 E-LINK EXAMPLE: TEMPLATE “PROVIDE GEO-INFORMATION FOR A GIVEN ENTITY” <http://example.org/document/1#char=0,6> ... nif:anchorOf "Berlin"@en; nif:beginIndex "0“; nif:endIndex "6“; itsrdf:taIdentRef <http://dbpedia.org/resource/Berlin> . ... <http://dbpedia.org/resource/Berlin>; itsrdf:taIdentRef <http://dbpedia.org/resource/Berlin>; geo:lat "52.516666"; geo:long "13.383333" . http://api.freme-project.eu/0.1/e-link/?outformat=turtle&templateid=1
    16. 16. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 16 LINKED DATA AND LOCALISATION: LESSONS LEARNED • Integration of linked data and tooling: loose coupling wins ◦ Localisation tools talking to linked data enabled web services • Hide complexity in the right manner ◦ Cf. e-Link template approach • Give people “their output format” – probably json ◦ json-ld to the rescue • Linked data world can benefit from localisation tooling ◦ Cf. work on OKAPI – NIF integration
    17. 17. FREME To Make Linked Data Available to Localizers – FREME at FEISGILTT 2015 WWW.FREME-PROJECT.EU 17 CONTACTS FELIX SASAKI Senior Researcher DFKI / W3C Fellow On behalf of the FREME consortium E-mail: felix.sasaki@dfki.de CONSORTIUM

    ×