XBRL Conference Archives - Overview Background,...

Overview

I Background, Goals & Benefits

I xEBR Ontology

I Showcases

Background: The Monnet & TrendMiner Projects

I European Integrated ProjectsI Monnet (www.monnet-project.eu)I TrendMiner (www.trendminer-project.eu)

I information extraction fromI stock exchange http pages

Deutsche Borse, NYSE Euronext, Bolsa de MadridI machine-readable financial documents

financial reports from different XBRL jurisdictions

I record extracted data in a Semantic RepositoryI transform data into a meaningful form w.r.t. ontologyI use well-defined standards (e.g., XSD, RDF, OWL)I carry out inferences and queries

I to make implicit knowledge explicitI to unveil inconsistencies

I xEBR ontology mediates between different XBRL jurisdictions

xEBR—What is This ?

I international standard for financial reporting: XBRLI XBRL = eXtensible Business Reporting LanguageI free and open standardI makes use of usual XML technologiesI describes important financial information for one full year

I structure of XBRL document is the same for each jurisdictionI but

I namespace and tag names differI some of the tags in one jurisdiction do not exist in another one

I circumvent these issues (in part): xEBRI xEBR = XBRL Europe Business RegistersI XBRL working group on xEBRI core taxonomy (≈ interlingua) for all XBRL jurisdictionsI information that is shared by all jurisdictionsI canonical namesI further info: other key financial ratios, company identification

Background: Schema—The Monnet Financial Ontology

I green: industry sector classification

I orange: financial reporting

I brown: stock exchange master data

I red: interface axioms

I blue: financial instruments

Background: Instance Data—Company Snapshots

I company information is harvested from stock exchange pages

I caption-value pairs are translated into instance data compliantwith the DAX & EN ontology schemata

I this includesI the proper use of class and property namesI the introduction of fresh URIs for individuals of interestI the syntactical transformation of valuesI the combination of values from different places

I binary facts + temporal duration: quintuplesI DE000A1EWWW0 1324055698213 DE000A1EWWW0 1324055698213

dax:endOfBusinessYear dax:totalCapitalStock

"--12-31"ˆˆxsd:gMonthDay "209216186EUR"ˆˆxsd:monetary"2011-12-21T16:24:20"ˆˆdateTime "2011-12-21T16:24:20"ˆˆdateTime"2011-12-21T16:24:20"ˆˆdateTime "2011-12-21T16:24:20"ˆˆdateTime

Background: Instance Data—xEBR ReportsI financial facts are harvested from XBRL reports

I xEBR serves as a mediator between XBRL jurisdictions

I XML-to-N-Triples translation<pfs:Assets contextRef="CurrentInstant"←↩ % CurrentInstance=2007

decimals="INF" unitRef="U-EUR">128413</pfs:Assets>

rep42 rdf:type xebr:Report

rep42 xebr:start "2007-04-01"ˆˆxsd:daterep42 xebr:end "2008-03-31"ˆˆxsd:daterep42 xebr:hasKeyBalanceSheetFiguresReport kbsfr4711

kbsfr4711 rdf:type xebr:KeyBalanceSheetFiguresReport

kbsfr4711 xebr:hasAssetsPresentation ap217

ap217 rdf:type xebr:AssetsPresentation

ap217 xebr:hasAssetsTotal "128413EUR"ˆˆxsd:monetary

I XEBR2XBRL & IF OWL axiomsxebr:AssetsPresentation ≡ xbrl be:AssetsTitlexebr:AssetsPresentation ≡ xbrl es:ActivoPresentacionxebr:hasAssetsTotal ≡ xbrl be:hasAssetsxebr:hasAssetsTotal ≡ xbrl es:hasTotalActivoen:revenue ≡ xebr:hasNetTurnoveren:operatingProfit ≡ xebr:hasOperatingProfitLossTotal

Using xEBR: Benefits

I the representation of the xEBR taxonomy as an OWLontology enables the use of semantic technologies

I short-time varying stock exchange data can be merged withlong(er)-time static data found in XBRL reports

I data redundancy permits consistency checking and thegeneration of financial summaries

I the use of xEBR (and industry sector classification) makes itpossible to compare companies across XBRL jurisdictions

I multilingual labels (e.g., English, French, German) attachedto xEBR concepts ease the work of human analysts

xEBR: Version 7 XML Specification, plus further files

<xsd:element name="KeyBalanceSheetFiguresReport" id="xebr KeyBalanceSheetFiguresReport"

type="xbrli:stringItemType" substitutionGroup="xbrli:item" abstract="true" nillable="true"

xbrli:periodType="instant"/>

<xsd:element name="AssetsPresentation" id="bach AssetsPresentation" type="xbrli:stringItemType"

substitutionGroup="xbrli:item" abstract="true" nillable="true" xbrli:periodType="instant"/>

<xsd:element name="SubscribedCapitalUnpaid" id="bach SubscribedCapitalUnpaid"

type="xbrli:monetaryItemType" substitutionGroup="xbrli:item" nillable="true"

xbrli:balance="debit" xbrli:periodType="instant"/>

<xsd:element name="FixedAssetsPresentation" id="xebr FixedAssetsPresentation"



<xsd:element name="IntangibleFixedAssetsPresentation"

id="bach IntangibleFixedAssetsPresentation" type="xbrli:stringItemType"

substitutionGroup="xbrli:item" abstract="true" nillable="true" xbrli:periodType="instant"/>

<xsd:element name="FormationPreliminaryExpenses" id="bach FormationPreliminaryExpenses"



<xsd:element name="OtherIntangibleFixedAssets" id="bach OtherIntangibleFixedAssets"



<xsd:element name="IntangibleFixedAssetsTotal" id="bach IntangibleFixedAssetsTotal"



<xsd:element name="TangibleFixedAssetsPresentation" id="bach TangibleFixedAssetsPresentation"



..........

xEBR: Version 7 Microsoft Excel Specification

xEBR: From a Taxonomy to an Ontology

I specification: make use of W3C standards RDF & OWLI declarative formalismI precise semanticsI computational properties: decidable, terminating

I taxonomy is a tree, expressing meronymy (not hyponymy !)I every xEBR concept in the specification comes with

I tag (xEBR concept): OWL class and/or propertyI (multilingual) label: annotation property rdfs:labelI xEBR type

I role: 4 fundamental parts of an xEBR report;example: Key Balance Sheet Figures [Report]

I abstract: a presentation has parts;example: Assets [Presentation]

I tuple: like abstract, but parts might be instantiated multipletimes; example: Company Official [List]

I monetary, string, date, etc.: leaves of the taxonomy

xEBR: From a Taxonomy to an Ontology—Idea

I whole (indent i) 3 part (indent i + 1): xEBR typesI role 3 abstract | tupleI abstract | tuple 3 abstract | tupleI abstract | tuple 3 atomic typeI no other combinations possible,

i.e., atomic type 63 abstract | tuple

I transformation to OWLI role, abstract, tuple: OWL classesI xEBR atomic types: XSD typesI parthood (3): dedicated OWL properties

I <whole> has<part> <part>I ... 3 abstract: functional object propertyI ... 3 tuple: (relational) object propertyI ... 3 atomic type: functional datatype property

xEBR: From a Taxonomy to an Ontology—Example

I ontology schema is auto-generated by a Java program

I N-Triples file is transformed into OWL-XML using raptor

I result can be viewed and modified using ontology editors

I example: Assets [Presentation] 3 Fixed Assets [Presentation]

xebr:AssetsPresentation rdf:type owl:Class

xebr:AssetsPresentation rdfs:label "Assets [Presentation]"@en

xebr:AssetsPresentation rdfs:subClassOf xebr:Abstract

xebr:hasFixedAssetsPresentation rdf:type owl:FunctionalProperty

xebr:hasFixedAssetsPresentation rdf:type owl:ObjectProperty

xebr:hasFixedAssetsPresentation rdfs:domain xebr:AssetsPresentation

xebr:hasFixedAssetsPresentation rdfs:range xebr:FixedAssetsPresentation

xebr:FixedAssetsPresentation rdf:type owl:Class

xebr:FixedAssetsPresentation rdfs:label "Fixed Assets [Presentation]"@en

xebr:FixedAssetsPresentation rdfs:subClassOf xebr:Abstract

xEBR: Version 7 OWL Ontology—Protege View

xEBR: Version 7 OWL Ontology—Protege View, Cont.

xEBR: From a Taxonomy to an Ontology—Alternative

I meronymy can not be expressed intensionally for all reportsI OWL’s TBox axiom constructors: ≡ and vI geared towards hyponymyI no constructor for parthood 3I our solution: individual properties for part-whole pairsI but: introduces a great number of (possibly empty) container

objects over and over again during ontology population

I solution: meta-model 3 as a TBox axiom constructorI 3 ⊆ owl:Class × owl:ClassI no longer OWL-DL, but still RDF, accessible through SPARQLI requires property belongsTo to link concrete data (e.g.,

financial numbers) to a specific xEBR reportI relational properties (tuple !) can not be modeled properly

xEBR: Problems With Hyponymy

I problem: change of xEBR type; true example:role → tuple → abstract → tuple → string ??

I hyponymy would lead to the “inheritance” of properties

I hasTangibleFixedAssets defined on FixedAssets is valid forTangibleFixedAssets and PropertyPlantAndEquipment, givenPropPlantEquip v TangibleFixedAssets v FixedAssets

I solution: local cardinality (= 0) restriction defined on classes

I more serious problem: entailment (universal instantiation) +querying (SPARQL): more than 1 value

I SELECT ?t WHERE {?p rdf:type xebr:FixedAssets .

?p xebr:hasTotal ?t}

Showcases

showcases make use of HFC, an in-memory semantic repositoryand extended forward chainer, going beyond RDF & OWL

I connecting snapshots and reports

I multilingual properties and classes

I evolution of financial data

I finding competitors across borders

I financial summaries: filling missing data

I consistency checking

Showcase: Connecting Snapshots and Reports

snapshots (quintuples) and reports (triples) are not related whenthey are uploaded; this rule connects them through if:hasReport

rules and queries below depend on the application of this rule

?comp rdf:type dax:Company ?s1 ?e1

?comp dax:isin ?isin ?s1 ?e1

?rep rdf:type xebr:Report

?rep xebr:hasCompanyIdentificationReport ?idrep

?idrep xebr:hasCompanyIdNumberList ?idlist

?idlist xebr:hasCompanyIdValue ?isin

?rep xebr:starts ?s2

?rep xebr:ends ?e2

->

?comp if:hasReport ?rep ?s2 ?e2

Showcase: Multilingual Properties and Classes

interface axioms and multilingual labels can ease the work of ahuman analyst in a specialized GUI (not shown here, only query)

xebr:hasAssetsTotal ≡ xbrl be:hasAssetsxebr:hasAssetsTotal ≡ xbrl es:hasTotalActivoxebr:hasKeyBalanceSheetFiguresReport ≡ xbrl es:hasBalanceSituacionPresentacionxebr:KeyBalanceSheetFiguresReport ≡ xbrl es:BalanceSituacionPresentacionxebr:AssetsPresentation ≡ xbrl es:ActivoPresentacion

xbrl be:hasAssets rdfs:label "Summe der Aktiva"de

xbrl be:hasAssets rdfs:label "Total assets"en

xbrl be:hasAssets rdfs:label "Total de l’actif"fr

xbrl be:hasAssets rdfs:label "Totaal van de activa"nl

xbrl es:hasTotalActivo rdfs:label "Total activo"es

xebr:hasAssetsTotal rdfs:label "Assets [Total]"en

Showcase: Multilingual Properties and Classes, Cont.

Spanish analyst looking for FDC’s total assets for 2007 (start ofbusiness year can be obtained elsewhere, viz., stock exchange)

SELECT ?total assets

WHERE ?rep rdf:type xebr:Report



?idlist xebr:hasCompanyIdValue "BE0468567012"

?rep xebr:starts "2007-04-01"ˆˆxsd:date?rep xbrl es:hasBalanceSituacionPresentacion ?kbsf

?kbsf xbrl es:hasActivoPresentacion ?ap

?ap xbrl es:hasTotalActivo ?total assets

Showcase: Evolution of Financial Data

query tangible & intangible fixed assets for adidas over the years(not listed on German DAX pages)

SELECT ?start2 ?end2 ?tass ?iass

WHERE ?comp rdf:type dax:Company ?start ?end

?comp dax:isin "DE000A1EWWW0" ?start ?end

?comp if:hasReport ?rep ?start2 ?end2

?rep xebr:hasKeyBalanceSheetFiguresReport ?kbsf

?kbsf xebr:hasAssetsPresentation ?ap

?ap xebr:hasFixedAssetsPresentation ?fap

?fap xebr:hasTangibleFixedAssetsPresentation ?tfap

?tfap xebr:hasTangibleFixedAssetsTotal ?tass

?fap xebr:hasIntangibleFixedAssetsPresentation ?ifap

?ifap xebr:hasIntangibleFixedAssetsTotal ?iass

Showcase: Finding Competitors Across Borders

we are looking for competitors of Deutsche Bank and theirfinancial numbers (xEBR reports), both on DAX & Euronext

IF interface axiom (DAX ↔ EN): financial institutionsicb:ICB8300 ≡ dax:Banks ≡ nace:nace 64.1

SELECT DISTINCT ?rival ?rep ?s3 ?e3

WHERE ?db dax:name "Deutsche Bank" ?s ?e

?db rdf:type ?type ?s ?e

?rival rdf:type ?type ?s2 ?e2

?rival if:hasReport ?rep ?s3 ?e3

FILTER ?db != ?rival

Showcase: Financial Summaries—Filling Missing Data

information that should be listed on DAX/EN is missing, but isavailable in the xEBR report for the same company (vice versa)

example: EADS’ net profit for 2007-2012 on Euronext

?rep rdf:type xebr:Report



?idlist xebr:hasCompanyIdValue "NL0000235190"

?rep xebr:starts ?start

?rep xebr:ends ?end

?rep xebr:hasKeyBalanceSheetFiguresReport ?kbsf

?kbsf xebr:hasEquityAndLiabilitiesPresentation ?elp

?elp xebr:hasEquityPresentation ?ep

?ep xebr:hasProfitLossForThePeriodTotal ?prof

?comp if:hasReport ?rep ?start ?end

->

?comp en:netProfit ?prof ?start ?end

Showcase: Consistency Checking

consistency checking through rules implements conditions thatshould never happen (like LTL safety properties):

I leave a memento in the repository when things go wrongI by marking URIs as being inconsistent (assign bottom type)

?p rdf:type owl:FunctionalProperty

?p rdf:type owl:DatatypeProperty

?x ?p ?y ?s1 ?e1

?x ?p ?z ?s2 ?e2

->

?x rdf:type owl:Nothing ?s ?e

@test

?y != ?z

IntersectionNotEmpty ?s1 ?e1 ?s2 ?e2

@action

?s = Max2 ?s1 ?s2

?e = Min2 ?e1 ?e2

Thank you!

Questions?

Translating XBRL Into Description Logic. An Approach UsingProtege, Sesame & OWL. BIS 2006.

A Temporal Extension of the Hayes/ter Horst Entailment Rulesand an Alternative to W3C’s N-ary Relations. FOIS 2012.

The MONNET Financial Ontology: Integrating IndependentOntologies Using OWL. KEOD 2012.

The xEBR Ontology: Transforming the XBRL Europe BusinessRegister Taxonomy into an OWL Ontology. XBRL 2013.

XBRL Conference Archives - Overview Background,...

Documents

Transcript of XBRL Conference Archives - Overview Background,...