Felix Sasaki - Value beyond content creation - Introducing ITS 2.0; soapconf 2014

Sasaki – SOAP! 2014
Value Beyond Content Creation:
Introducing ITS 2.0
Felix Sasaki
DFKI / W3C Fellow
Slides at
http://www.w3.org/Talks/2014/1003-soap-sasaki.pdf
1

If you want to have nice visualization
what ITS 2.0 is: go here 
“Linguini a la translation:
An Introduction to ITS 2.0”
https://www.youtube.com/watch?v=5Goet3hX6Jo
2

What content authors normally do
• Make money by creating
– Content
– Layout
– Apps
• More and more difficult
– Growing amount of content & apps
– What is the differentiator?
3

What content authors may do
in the future
• Make money by enriching content
– Using automatic tools with manual correction
– Create the basis for further processes
• Translation, search engine optimization,
contextualization, personalization, ..
– Authors become content curators 
• Background: R&D projects and their results
4

Background 1: LIDER project
http://lider-project.eu/
• EU funded project – aims:
– Demonstrating the value of multilingual linguistic
linked data sources
– Exploring usage scenarios & requirements in
various domains
– Creating an R&D roadmap around the topic
5

Background 2: ITS 2.0
http://www.w3.org/TR/its20/
• W3C standard to foster multilingual content
creation
• Defines metadata (“data categories”) to
support the multilingual content life cycle
• A way to interlink Web content and
multilingual linked data sources
6

ITS 2.0 data categories
• Translate
• Localization Note
• Terminology
• Directionality
• Language Information
• Elements Within Text
• Domain
• Text Analysis
• Locale Filter
• Provenance
• External Resource
• Target Pointer
• ID Value
• Preserve Space
• Localization Quality Issue
• Localization Quality
Rating
• MT Confidence
• Allowed Characters
• Storage Size
7

ITS 2.0: High level features
• Can be applied to general XML content and to
HTML5
• Partially natively supported in HTML5
– E.g. HTML5 “translate” attribute
• Applying data categories
– locally: ITS attributes in content
– globally: CSS like selector mechanism, using XPath
• Independent data categories: no need to support
(as tool maker or user) everything 
8

Example: “Translate”
local and global
9
The World Wide Web Consortium
is making the World Wide Web worldwide!
<its:rules
xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
<its:translateRule selector="//h:code" translate="no"
xmlns:h="http://www.w3.org/1999/xhtml"/>
</its:rules>

Example: “Localization Note”
10
<data
its:locNote="%1$s is the original text's date in the format YYYY-
MM-DD HH:MM always in GMT" …>
<value>Translated from English content dated %1$s GMT.</value>
</data>

Example: “Elements within Text”
11
<text xmlns:its="http://www.w3.org/2005/11/its"
its:version="2.0">
<body>
<par>Text with <bold its:withinText="yes">bold</bold>.</par>
</body>
</text>

Example: “Locale Filter”
12
<book xmlns:its="http://www.w3.org/2005/11/its">
<info>
<legalnotice its:localeFilterList="en-CA, fr-CA">
<para>This legal notice is only for English and French Canadian
locales.</para>
</legalnotice>
</info>
</book>

Example: “Allowed Characters”
13
Login names can only use letters from A to Z (upper or
lowercase)
and the character underscore (_) and minus (-).
For example:
<code its-allowed-characters=[a-zA-Z_-]>Huck_Finn</code>.

Example: “Terminology”
14
And he said: you need a new
<quote its:term="yes"
its:termInfoRef
="http://www.directron.com/motherboards1.html"
its:termConfidence="0.5">motherboard</quote>

Example: “MT Confidence”
15
<body its-annotators-ref="mt-confidence|file:///tools.xml#T1">

Dublin is the capital of
Ireland.

Example: “Provenance”
16
This paragraph was translated from the machine.

Example: “Localization Quality Issue”
17

<span
data-mytool-qacode=named_entity_not_found
its-loc-quality-issue-comment="Should be Thomas Cahill.”
its-loc-quality-issue-profile-ref=http://example.org/qaMovel/v1
its-loc-quality-issue-severity=100
its-loc-quality-issue-type=inconsistent-entities>
Christian Bale (1867–1934) conceived of an instrument
…

Example: “Text Analysis”
• Identify concepts in content, like named
entities
– persons, places, events, …
• Store identifiers in (Web) content
• Provide a link to multilingual linked data
sources – a basis for content curation
18

Example: “Text Analysis”
19
Dublin is the capital of Ireland.

What content authors can do with multilingual
linked data sources and ITS 2.0
• Add value to content beyond the content itself
• Curate content: provide identifiers, context, cross
lingual information
• Tool examples:
1) Generation of ITS 2.0 “Text Analysis” for ePub, and
Schema.org markup
2) Generation of translation suggestions
3) Working with linked data in the browser – without
understanding details
20

TOOLING 1): GENERATION OF ITS 2.0
“TEXT ANALYSIS” AND SCHEMA.ORG
MARKUP FOR EPUB
21

Setup
• oXygen XML editor, modified for ePub /
XHTML5 author mode
• Input: ePub or XHTML5 documents
• Output: documents enriched with Schema.org
structured information
• User does information generation in a
WYSIYWG mode
22

Process
1. Automatic generation of entity annotation,
using DBpedia spotlight, producing DBpedia
identifiers
2. Access to DBpedia information with pre-
defined linked data queries
3. Generation of Schema.org markup
23

1. Automatic generation of entity
annotation
• Input:
Welcome to Dublin in Ireland, the home of Samuel
Beckett.
24

annotation
• Output, stored with ITS 2.0 “Text Analysis”
markup:
Welcome to Dublin in Ireland, the home of Samuel Beckett.
25

2. Access to DBpedia information
• Using DBpedia identifiers from previous steps
in linked data query templates. Example query
(part of the query), checking whether entity is
a person:
SELECT ?birthPlace ... WHERE{
<http://dbpedia.org/resource/Samuel_Beckett>
rdf:type foaf:Person.
... }
26

3. Generation of Schema.org
• Using output of previous step (query result)
• Generating Schema.org structured
information
– Taking types derived from DBpedia into account,
currently
• http://schema.org/Person
• http://schema.org/Place
27

• Input: linked data query result and marked-up
document
Welcome to <span
28

• Output: marked-up document with
Schema.org structured information
Welcome to 
<a itemprop="url" href="
http://en.wikipedia.org/wiki/Dublin">Dublin</a>…
29

• Output: auto-generating markup + text
... Samuel Beckett ... (born in 
<a itemprop="url"
href="http://en.wikipedia.org/wiki/Foxrock">
Foxrock</a>)
30

Checking output with
Structured Data Testing Tool
31

Broad review: a view of schema.org
types that may work well
Book (dbpedia-owl:Book)
City (dbpedia-owl:City)
Country (dbpedia-owl:Country)
Event (dbpedia-owl:Event)
Hotel (dbpedia-owl:Hotel)
Library (dbpedia-owl:Library)
Movie (dbpedia-owl:Film)
Person (foaf:Person)
Place (dbpedia-owl:Place)
Organization (dbpedia-owl:Organization)
32

TOOLING 2): GENERATION OF
TRANSLATION SUGGESTIONS
33

Generating translation suggestions
• Input: like before
• Steps:
1. Entity annotations (again)
2. Access to DBpedia and Wikidata to get
translation suggestions
3. Storing the results as a localization note
34

annotation
• Output, stored with ITS 2.0 “Text Analysis”
markup:
Welcome to <span
35

2. Access to DBpedia and Wikidata to
get translation suggestions
• Get translation suggestion from Dbpedia
SELECT ?o WHERE {
<http://dbpedia.org/resource/Samuel_Beckett> rdfs:label ?o
}
36

2. Access to DBpedia and Wikidata to
get translation suggestions
• Get translation suggestion from Wikidata
http://www.wikidata.org/w/api.php?action=
wbgetentities&
sites=itwiki&
titles=Samuel%20Beckett
37

3. Storing the results as ITS 2.0
localization note
• Input: DBpedia + Wikidata query result and
marked-up document
… the home of <span
38

3. Storing the results as localization
note
• Output: Translation suggestions stored as
localization note
… the home of <span
its-loc-note="
TRANSLATION SUGGESTIONS: 1) wikidata:サミュエル・ベケッ
ト
2) dbpedia:サミュエル・ベケット"
39

TOOLING 3: WORKING WITH LINKED
DATA IN THE BROWSER – WITHOUT
UNDERSTANDING DETAILS
40

MLOD4CON
• Working with links to external multilingual
data sources
• Under the hood: lot’ of technology
– ITS 2.0, RDF, SPARQL, JavaScript, …
• Good news: the user does not need to know
about these 
Demo at
http://www.w3.org/People/fsasaki/mlod4con/
41

EVERYTHING DONE?
42

Issues
• Learn from communities what they want to do
with ITS 2.0 and linked data sources
– Content creators and content architects,
translators, XML / Web tool makers, researchers in
the data and language technology area, …
• Provide adequate tooling
• Look carefully into requirements: “Too much
information is no information!”
43

What next for you?
• ITS 2.0 Tooling
https://www.w3.org/International/its/wiki/ITS_Implementations
• Videos explaining ITS 2.0 usage
https://www.youtube.com/user/W3CITS20/videos
• Linked Data for Language Technology Community
Group: discuss use cases and requirements for
multilingual linked data
http://www.w3.org/community/ld4lt/
• ITS Interest Group: Join the community of ITS 2.0
users and implementers
https://www.w3.org/International/its/ig/
44

Value Beyond Content Creation:
Introducing ITS 2.0
Felix Sasaki
DFKI / W3C Fellow
Slides at
http://www.w3.org/Talks/2014/1003-soap-sasaki.pdf
45

Felix Sasaki - Value beyond content creation - Introducing ITS 2.0; soapconf 2014

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Destacado

Destacado (20)

Similar a Felix Sasaki - Value beyond content creation - Introducing ITS 2.0; soapconf 2014

Similar a Felix Sasaki - Value beyond content creation - Introducing ITS 2.0; soapconf 2014 (20)

Más de soapconf

Más de soapconf (11)

Último

Último (20)

Felix Sasaki - Value beyond content creation - Introducing ITS 2.0; soapconf 2014