57
2 First Working Group Meeting e-procurement ontology workshop 23 March 2017 Luxembourg

e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

  • Upload
    others

  • View
    1

  • Download
    0

Embed Size (px)

Citation preview

Page 1: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

First Working Group Meeting

e-procurement

ontology workshop

23 March 2017

Luxembourg

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

2

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

3

2

4

Round table

2

5

Introduction to the project

2

Background to the project

Legal background Directives

Landscaping exercise 2016

Conclusions of earlier work

Two phases

bull Inception phase to prepare the ground

bull Development phase to build consensus on ontology in Working Group of stakeholders

Final result e-procurement ontology allowing wide range of applications to access and reuse procurement data

6

2

Two phases and final result

Two phases

bull Inception phase to prepare the ground

bull Development phase to build consensus on ontology in Working Group of stakeholders

Final result e-procurement ontology allowing wide range of applications to access and reuse procurement data

7

2

The problem and its impact

The problem

bull Concepts and relationships not fully documented

bull Data inherited from legacy paper-based origins

bull Different incompatible formats

The impact

bull Low transparency and monitoring

bull Difficulty to provide value-added services

bull Low interconnection between public procurement systems

bull Low reuse and access to data

8

2

Why an ontology

In general1

bull To share common understanding of the structure of information

bull To enable reuse of domain knowledge

bull To make domain assumptions explicit

In our case

bull Provide a conceptual model across existing procurement standards

bull model in standard Ontology Web Language (OWL)2

bull Enable procurement data to play in Linked Data3 environment for access by third-party applications

1See httpprotegestanfordedupublicationsontology_developmentontology101-noy-mcguinnesshtml2See httpswwww3orgOWL3See httpswwww3orgstandardssemanticwebdata

9

2

ltXMLgt

Closed world

e-procurement

silo

Message and process

based specifying all

information for

application integration

Linked Data

e-procurement

ontology

Open world

Application

independent

RDF

Exportand convert

CPV

NUTS

Eurostat

MDR

PPROC

Dublin Core

Match with budget amp spending

data

3rd-party procurement

services

NGOtransparency

watchdog

Journalists

Linked Open

Data Cloud

10

2

What is an ontology

A formal explicit description of concepts with their attributes and relationships including restrictions on values

In practical terms an ontology

bull defines classes ndash the things of interest

bull arranges classes in a hierarchy ndash subclasssuperclass

bull defines properties and allowed values ndash eg data types

bull defines relationships between classes

bull fills in values for the properties ndash eg controlled vocabularies

The definition of these semantics enable interoperability among different systems and applications

11

2

How is an ontology different

Other initiatives eg UBL1 CEN WSBII2

bull Focus on messaging to support the procurement process

bull Express information in XML structures (tree-container approach)

bull Operate in closed-world environments full specification for application integration ndash what is not specified is false

The e-procurement ontology

bull Formalises the semantics of all entities properties and relationships

bull Expresses information in RDF (Subject-Predicate-Object triples)

bull Operates in open-world of Linked Data specification of common elements for data integration ndash what is not specified is unknown

1 Universal Business Language See httpswwwoasis-openorgcommitteesubl2 CEN Business Interoperability Interfaces httpwwwcenbiieu

12

2

ltxml version=10 encoding=utf-8 gt

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns

xmlnsns0=httpdataeuropaeuontologygt

ltrdfDescription rdfabout=httpdataeuropaeuInvoice123gt

ltns0hasADeterminedgt

ltrdfDescription rdfabout=httpdataeuropaeuValue234gt

ltns0hasCurrency rdfresource=httppublicationseuropaeuresourceauthoritycurrencyEURgt

ltns0hasAmount rdfdatatype=httpwwww3org2001XMLSchemadecimalgt498730ltns0hasAmountgt

ltrdfDescriptiongt

ltns0hasADeterminedgt

ltrdfDescriptiongt

httpdataeuropaeuontologyhasADetermined

httpdataeuropaeuontologyhasCurrency httpdataeuropaeuontologyhasAmount

httpdataeuropaeuInvoice123

httpdataeuropaeuValue234

httppublicationseuropaeuresourceauthoritycurrencyEUR 498730

13

2

A Linked Data example in RDFCALL FOR TENDER

Direct linking to

references on the web

(RDF)

hellipMDR

(RDF)

(RDF)

(RDF)

NUTS

CPV

MDR

hellip NUTS

hellip CPV

RDF for Call For

Tender

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns gtltrdfDescription rdfabout=CfT-Xgtltrdftype rdfresource=eprocCallForTender gtlteprochasCPV rdfresource=httpcpv30197220-4 link to CPV RDFlteprochasNUTS rdfresource=httpnutsLU000 link to NUTS RDFltdctpublisher rdfresource=httpcorporate-bodyPUBL Link to MDR RDF

ltrdfDescriptiongtltrdfRDFgt

14

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 2: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

2

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

3

2

4

Round table

2

5

Introduction to the project

2

Background to the project

Legal background Directives

Landscaping exercise 2016

Conclusions of earlier work

Two phases

bull Inception phase to prepare the ground

bull Development phase to build consensus on ontology in Working Group of stakeholders

Final result e-procurement ontology allowing wide range of applications to access and reuse procurement data

6

2

Two phases and final result

Two phases

bull Inception phase to prepare the ground

bull Development phase to build consensus on ontology in Working Group of stakeholders

Final result e-procurement ontology allowing wide range of applications to access and reuse procurement data

7

2

The problem and its impact

The problem

bull Concepts and relationships not fully documented

bull Data inherited from legacy paper-based origins

bull Different incompatible formats

The impact

bull Low transparency and monitoring

bull Difficulty to provide value-added services

bull Low interconnection between public procurement systems

bull Low reuse and access to data

8

2

Why an ontology

In general1

bull To share common understanding of the structure of information

bull To enable reuse of domain knowledge

bull To make domain assumptions explicit

In our case

bull Provide a conceptual model across existing procurement standards

bull model in standard Ontology Web Language (OWL)2

bull Enable procurement data to play in Linked Data3 environment for access by third-party applications

1See httpprotegestanfordedupublicationsontology_developmentontology101-noy-mcguinnesshtml2See httpswwww3orgOWL3See httpswwww3orgstandardssemanticwebdata

9

2

ltXMLgt

Closed world

e-procurement

silo

Message and process

based specifying all

information for

application integration

Linked Data

e-procurement

ontology

Open world

Application

independent

RDF

Exportand convert

CPV

NUTS

Eurostat

MDR

PPROC

Dublin Core

Match with budget amp spending

data

3rd-party procurement

services

NGOtransparency

watchdog

Journalists

Linked Open

Data Cloud

10

2

What is an ontology

A formal explicit description of concepts with their attributes and relationships including restrictions on values

In practical terms an ontology

bull defines classes ndash the things of interest

bull arranges classes in a hierarchy ndash subclasssuperclass

bull defines properties and allowed values ndash eg data types

bull defines relationships between classes

bull fills in values for the properties ndash eg controlled vocabularies

The definition of these semantics enable interoperability among different systems and applications

11

2

How is an ontology different

Other initiatives eg UBL1 CEN WSBII2

bull Focus on messaging to support the procurement process

bull Express information in XML structures (tree-container approach)

bull Operate in closed-world environments full specification for application integration ndash what is not specified is false

The e-procurement ontology

bull Formalises the semantics of all entities properties and relationships

bull Expresses information in RDF (Subject-Predicate-Object triples)

bull Operates in open-world of Linked Data specification of common elements for data integration ndash what is not specified is unknown

1 Universal Business Language See httpswwwoasis-openorgcommitteesubl2 CEN Business Interoperability Interfaces httpwwwcenbiieu

12

2

ltxml version=10 encoding=utf-8 gt

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns

xmlnsns0=httpdataeuropaeuontologygt

ltrdfDescription rdfabout=httpdataeuropaeuInvoice123gt

ltns0hasADeterminedgt

ltrdfDescription rdfabout=httpdataeuropaeuValue234gt

ltns0hasCurrency rdfresource=httppublicationseuropaeuresourceauthoritycurrencyEURgt

ltns0hasAmount rdfdatatype=httpwwww3org2001XMLSchemadecimalgt498730ltns0hasAmountgt

ltrdfDescriptiongt

ltns0hasADeterminedgt

ltrdfDescriptiongt

httpdataeuropaeuontologyhasADetermined

httpdataeuropaeuontologyhasCurrency httpdataeuropaeuontologyhasAmount

httpdataeuropaeuInvoice123

httpdataeuropaeuValue234

httppublicationseuropaeuresourceauthoritycurrencyEUR 498730

13

2

A Linked Data example in RDFCALL FOR TENDER

Direct linking to

references on the web

(RDF)

hellipMDR

(RDF)

(RDF)

(RDF)

NUTS

CPV

MDR

hellip NUTS

hellip CPV

RDF for Call For

Tender

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns gtltrdfDescription rdfabout=CfT-Xgtltrdftype rdfresource=eprocCallForTender gtlteprochasCPV rdfresource=httpcpv30197220-4 link to CPV RDFlteprochasNUTS rdfresource=httpnutsLU000 link to NUTS RDFltdctpublisher rdfresource=httpcorporate-bodyPUBL Link to MDR RDF

ltrdfDescriptiongtltrdfRDFgt

14

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 3: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

3

2

4

Round table

2

5

Introduction to the project

2

Background to the project

Legal background Directives

Landscaping exercise 2016

Conclusions of earlier work

Two phases

bull Inception phase to prepare the ground

bull Development phase to build consensus on ontology in Working Group of stakeholders

Final result e-procurement ontology allowing wide range of applications to access and reuse procurement data

6

2

Two phases and final result

Two phases

bull Inception phase to prepare the ground

bull Development phase to build consensus on ontology in Working Group of stakeholders

Final result e-procurement ontology allowing wide range of applications to access and reuse procurement data

7

2

The problem and its impact

The problem

bull Concepts and relationships not fully documented

bull Data inherited from legacy paper-based origins

bull Different incompatible formats

The impact

bull Low transparency and monitoring

bull Difficulty to provide value-added services

bull Low interconnection between public procurement systems

bull Low reuse and access to data

8

2

Why an ontology

In general1

bull To share common understanding of the structure of information

bull To enable reuse of domain knowledge

bull To make domain assumptions explicit

In our case

bull Provide a conceptual model across existing procurement standards

bull model in standard Ontology Web Language (OWL)2

bull Enable procurement data to play in Linked Data3 environment for access by third-party applications

1See httpprotegestanfordedupublicationsontology_developmentontology101-noy-mcguinnesshtml2See httpswwww3orgOWL3See httpswwww3orgstandardssemanticwebdata

9

2

ltXMLgt

Closed world

e-procurement

silo

Message and process

based specifying all

information for

application integration

Linked Data

e-procurement

ontology

Open world

Application

independent

RDF

Exportand convert

CPV

NUTS

Eurostat

MDR

PPROC

Dublin Core

Match with budget amp spending

data

3rd-party procurement

services

NGOtransparency

watchdog

Journalists

Linked Open

Data Cloud

10

2

What is an ontology

A formal explicit description of concepts with their attributes and relationships including restrictions on values

In practical terms an ontology

bull defines classes ndash the things of interest

bull arranges classes in a hierarchy ndash subclasssuperclass

bull defines properties and allowed values ndash eg data types

bull defines relationships between classes

bull fills in values for the properties ndash eg controlled vocabularies

The definition of these semantics enable interoperability among different systems and applications

11

2

How is an ontology different

Other initiatives eg UBL1 CEN WSBII2

bull Focus on messaging to support the procurement process

bull Express information in XML structures (tree-container approach)

bull Operate in closed-world environments full specification for application integration ndash what is not specified is false

The e-procurement ontology

bull Formalises the semantics of all entities properties and relationships

bull Expresses information in RDF (Subject-Predicate-Object triples)

bull Operates in open-world of Linked Data specification of common elements for data integration ndash what is not specified is unknown

1 Universal Business Language See httpswwwoasis-openorgcommitteesubl2 CEN Business Interoperability Interfaces httpwwwcenbiieu

12

2

ltxml version=10 encoding=utf-8 gt

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns

xmlnsns0=httpdataeuropaeuontologygt

ltrdfDescription rdfabout=httpdataeuropaeuInvoice123gt

ltns0hasADeterminedgt

ltrdfDescription rdfabout=httpdataeuropaeuValue234gt

ltns0hasCurrency rdfresource=httppublicationseuropaeuresourceauthoritycurrencyEURgt

ltns0hasAmount rdfdatatype=httpwwww3org2001XMLSchemadecimalgt498730ltns0hasAmountgt

ltrdfDescriptiongt

ltns0hasADeterminedgt

ltrdfDescriptiongt

httpdataeuropaeuontologyhasADetermined

httpdataeuropaeuontologyhasCurrency httpdataeuropaeuontologyhasAmount

httpdataeuropaeuInvoice123

httpdataeuropaeuValue234

httppublicationseuropaeuresourceauthoritycurrencyEUR 498730

13

2

A Linked Data example in RDFCALL FOR TENDER

Direct linking to

references on the web

(RDF)

hellipMDR

(RDF)

(RDF)

(RDF)

NUTS

CPV

MDR

hellip NUTS

hellip CPV

RDF for Call For

Tender

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns gtltrdfDescription rdfabout=CfT-Xgtltrdftype rdfresource=eprocCallForTender gtlteprochasCPV rdfresource=httpcpv30197220-4 link to CPV RDFlteprochasNUTS rdfresource=httpnutsLU000 link to NUTS RDFltdctpublisher rdfresource=httpcorporate-bodyPUBL Link to MDR RDF

ltrdfDescriptiongtltrdfRDFgt

14

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 4: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

4

Round table

2

5

Introduction to the project

2

Background to the project

Legal background Directives

Landscaping exercise 2016

Conclusions of earlier work

Two phases

bull Inception phase to prepare the ground

bull Development phase to build consensus on ontology in Working Group of stakeholders

Final result e-procurement ontology allowing wide range of applications to access and reuse procurement data

6

2

Two phases and final result

Two phases

bull Inception phase to prepare the ground

bull Development phase to build consensus on ontology in Working Group of stakeholders

Final result e-procurement ontology allowing wide range of applications to access and reuse procurement data

7

2

The problem and its impact

The problem

bull Concepts and relationships not fully documented

bull Data inherited from legacy paper-based origins

bull Different incompatible formats

The impact

bull Low transparency and monitoring

bull Difficulty to provide value-added services

bull Low interconnection between public procurement systems

bull Low reuse and access to data

8

2

Why an ontology

In general1

bull To share common understanding of the structure of information

bull To enable reuse of domain knowledge

bull To make domain assumptions explicit

In our case

bull Provide a conceptual model across existing procurement standards

bull model in standard Ontology Web Language (OWL)2

bull Enable procurement data to play in Linked Data3 environment for access by third-party applications

1See httpprotegestanfordedupublicationsontology_developmentontology101-noy-mcguinnesshtml2See httpswwww3orgOWL3See httpswwww3orgstandardssemanticwebdata

9

2

ltXMLgt

Closed world

e-procurement

silo

Message and process

based specifying all

information for

application integration

Linked Data

e-procurement

ontology

Open world

Application

independent

RDF

Exportand convert

CPV

NUTS

Eurostat

MDR

PPROC

Dublin Core

Match with budget amp spending

data

3rd-party procurement

services

NGOtransparency

watchdog

Journalists

Linked Open

Data Cloud

10

2

What is an ontology

A formal explicit description of concepts with their attributes and relationships including restrictions on values

In practical terms an ontology

bull defines classes ndash the things of interest

bull arranges classes in a hierarchy ndash subclasssuperclass

bull defines properties and allowed values ndash eg data types

bull defines relationships between classes

bull fills in values for the properties ndash eg controlled vocabularies

The definition of these semantics enable interoperability among different systems and applications

11

2

How is an ontology different

Other initiatives eg UBL1 CEN WSBII2

bull Focus on messaging to support the procurement process

bull Express information in XML structures (tree-container approach)

bull Operate in closed-world environments full specification for application integration ndash what is not specified is false

The e-procurement ontology

bull Formalises the semantics of all entities properties and relationships

bull Expresses information in RDF (Subject-Predicate-Object triples)

bull Operates in open-world of Linked Data specification of common elements for data integration ndash what is not specified is unknown

1 Universal Business Language See httpswwwoasis-openorgcommitteesubl2 CEN Business Interoperability Interfaces httpwwwcenbiieu

12

2

ltxml version=10 encoding=utf-8 gt

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns

xmlnsns0=httpdataeuropaeuontologygt

ltrdfDescription rdfabout=httpdataeuropaeuInvoice123gt

ltns0hasADeterminedgt

ltrdfDescription rdfabout=httpdataeuropaeuValue234gt

ltns0hasCurrency rdfresource=httppublicationseuropaeuresourceauthoritycurrencyEURgt

ltns0hasAmount rdfdatatype=httpwwww3org2001XMLSchemadecimalgt498730ltns0hasAmountgt

ltrdfDescriptiongt

ltns0hasADeterminedgt

ltrdfDescriptiongt

httpdataeuropaeuontologyhasADetermined

httpdataeuropaeuontologyhasCurrency httpdataeuropaeuontologyhasAmount

httpdataeuropaeuInvoice123

httpdataeuropaeuValue234

httppublicationseuropaeuresourceauthoritycurrencyEUR 498730

13

2

A Linked Data example in RDFCALL FOR TENDER

Direct linking to

references on the web

(RDF)

hellipMDR

(RDF)

(RDF)

(RDF)

NUTS

CPV

MDR

hellip NUTS

hellip CPV

RDF for Call For

Tender

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns gtltrdfDescription rdfabout=CfT-Xgtltrdftype rdfresource=eprocCallForTender gtlteprochasCPV rdfresource=httpcpv30197220-4 link to CPV RDFlteprochasNUTS rdfresource=httpnutsLU000 link to NUTS RDFltdctpublisher rdfresource=httpcorporate-bodyPUBL Link to MDR RDF

ltrdfDescriptiongtltrdfRDFgt

14

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 5: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

5

Introduction to the project

2

Background to the project

Legal background Directives

Landscaping exercise 2016

Conclusions of earlier work

Two phases

bull Inception phase to prepare the ground

bull Development phase to build consensus on ontology in Working Group of stakeholders

Final result e-procurement ontology allowing wide range of applications to access and reuse procurement data

6

2

Two phases and final result

Two phases

bull Inception phase to prepare the ground

bull Development phase to build consensus on ontology in Working Group of stakeholders

Final result e-procurement ontology allowing wide range of applications to access and reuse procurement data

7

2

The problem and its impact

The problem

bull Concepts and relationships not fully documented

bull Data inherited from legacy paper-based origins

bull Different incompatible formats

The impact

bull Low transparency and monitoring

bull Difficulty to provide value-added services

bull Low interconnection between public procurement systems

bull Low reuse and access to data

8

2

Why an ontology

In general1

bull To share common understanding of the structure of information

bull To enable reuse of domain knowledge

bull To make domain assumptions explicit

In our case

bull Provide a conceptual model across existing procurement standards

bull model in standard Ontology Web Language (OWL)2

bull Enable procurement data to play in Linked Data3 environment for access by third-party applications

1See httpprotegestanfordedupublicationsontology_developmentontology101-noy-mcguinnesshtml2See httpswwww3orgOWL3See httpswwww3orgstandardssemanticwebdata

9

2

ltXMLgt

Closed world

e-procurement

silo

Message and process

based specifying all

information for

application integration

Linked Data

e-procurement

ontology

Open world

Application

independent

RDF

Exportand convert

CPV

NUTS

Eurostat

MDR

PPROC

Dublin Core

Match with budget amp spending

data

3rd-party procurement

services

NGOtransparency

watchdog

Journalists

Linked Open

Data Cloud

10

2

What is an ontology

A formal explicit description of concepts with their attributes and relationships including restrictions on values

In practical terms an ontology

bull defines classes ndash the things of interest

bull arranges classes in a hierarchy ndash subclasssuperclass

bull defines properties and allowed values ndash eg data types

bull defines relationships between classes

bull fills in values for the properties ndash eg controlled vocabularies

The definition of these semantics enable interoperability among different systems and applications

11

2

How is an ontology different

Other initiatives eg UBL1 CEN WSBII2

bull Focus on messaging to support the procurement process

bull Express information in XML structures (tree-container approach)

bull Operate in closed-world environments full specification for application integration ndash what is not specified is false

The e-procurement ontology

bull Formalises the semantics of all entities properties and relationships

bull Expresses information in RDF (Subject-Predicate-Object triples)

bull Operates in open-world of Linked Data specification of common elements for data integration ndash what is not specified is unknown

1 Universal Business Language See httpswwwoasis-openorgcommitteesubl2 CEN Business Interoperability Interfaces httpwwwcenbiieu

12

2

ltxml version=10 encoding=utf-8 gt

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns

xmlnsns0=httpdataeuropaeuontologygt

ltrdfDescription rdfabout=httpdataeuropaeuInvoice123gt

ltns0hasADeterminedgt

ltrdfDescription rdfabout=httpdataeuropaeuValue234gt

ltns0hasCurrency rdfresource=httppublicationseuropaeuresourceauthoritycurrencyEURgt

ltns0hasAmount rdfdatatype=httpwwww3org2001XMLSchemadecimalgt498730ltns0hasAmountgt

ltrdfDescriptiongt

ltns0hasADeterminedgt

ltrdfDescriptiongt

httpdataeuropaeuontologyhasADetermined

httpdataeuropaeuontologyhasCurrency httpdataeuropaeuontologyhasAmount

httpdataeuropaeuInvoice123

httpdataeuropaeuValue234

httppublicationseuropaeuresourceauthoritycurrencyEUR 498730

13

2

A Linked Data example in RDFCALL FOR TENDER

Direct linking to

references on the web

(RDF)

hellipMDR

(RDF)

(RDF)

(RDF)

NUTS

CPV

MDR

hellip NUTS

hellip CPV

RDF for Call For

Tender

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns gtltrdfDescription rdfabout=CfT-Xgtltrdftype rdfresource=eprocCallForTender gtlteprochasCPV rdfresource=httpcpv30197220-4 link to CPV RDFlteprochasNUTS rdfresource=httpnutsLU000 link to NUTS RDFltdctpublisher rdfresource=httpcorporate-bodyPUBL Link to MDR RDF

ltrdfDescriptiongtltrdfRDFgt

14

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 6: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Background to the project

Legal background Directives

Landscaping exercise 2016

Conclusions of earlier work

Two phases

bull Inception phase to prepare the ground

bull Development phase to build consensus on ontology in Working Group of stakeholders

Final result e-procurement ontology allowing wide range of applications to access and reuse procurement data

6

2

Two phases and final result

Two phases

bull Inception phase to prepare the ground

bull Development phase to build consensus on ontology in Working Group of stakeholders

Final result e-procurement ontology allowing wide range of applications to access and reuse procurement data

7

2

The problem and its impact

The problem

bull Concepts and relationships not fully documented

bull Data inherited from legacy paper-based origins

bull Different incompatible formats

The impact

bull Low transparency and monitoring

bull Difficulty to provide value-added services

bull Low interconnection between public procurement systems

bull Low reuse and access to data

8

2

Why an ontology

In general1

bull To share common understanding of the structure of information

bull To enable reuse of domain knowledge

bull To make domain assumptions explicit

In our case

bull Provide a conceptual model across existing procurement standards

bull model in standard Ontology Web Language (OWL)2

bull Enable procurement data to play in Linked Data3 environment for access by third-party applications

1See httpprotegestanfordedupublicationsontology_developmentontology101-noy-mcguinnesshtml2See httpswwww3orgOWL3See httpswwww3orgstandardssemanticwebdata

9

2

ltXMLgt

Closed world

e-procurement

silo

Message and process

based specifying all

information for

application integration

Linked Data

e-procurement

ontology

Open world

Application

independent

RDF

Exportand convert

CPV

NUTS

Eurostat

MDR

PPROC

Dublin Core

Match with budget amp spending

data

3rd-party procurement

services

NGOtransparency

watchdog

Journalists

Linked Open

Data Cloud

10

2

What is an ontology

A formal explicit description of concepts with their attributes and relationships including restrictions on values

In practical terms an ontology

bull defines classes ndash the things of interest

bull arranges classes in a hierarchy ndash subclasssuperclass

bull defines properties and allowed values ndash eg data types

bull defines relationships between classes

bull fills in values for the properties ndash eg controlled vocabularies

The definition of these semantics enable interoperability among different systems and applications

11

2

How is an ontology different

Other initiatives eg UBL1 CEN WSBII2

bull Focus on messaging to support the procurement process

bull Express information in XML structures (tree-container approach)

bull Operate in closed-world environments full specification for application integration ndash what is not specified is false

The e-procurement ontology

bull Formalises the semantics of all entities properties and relationships

bull Expresses information in RDF (Subject-Predicate-Object triples)

bull Operates in open-world of Linked Data specification of common elements for data integration ndash what is not specified is unknown

1 Universal Business Language See httpswwwoasis-openorgcommitteesubl2 CEN Business Interoperability Interfaces httpwwwcenbiieu

12

2

ltxml version=10 encoding=utf-8 gt

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns

xmlnsns0=httpdataeuropaeuontologygt

ltrdfDescription rdfabout=httpdataeuropaeuInvoice123gt

ltns0hasADeterminedgt

ltrdfDescription rdfabout=httpdataeuropaeuValue234gt

ltns0hasCurrency rdfresource=httppublicationseuropaeuresourceauthoritycurrencyEURgt

ltns0hasAmount rdfdatatype=httpwwww3org2001XMLSchemadecimalgt498730ltns0hasAmountgt

ltrdfDescriptiongt

ltns0hasADeterminedgt

ltrdfDescriptiongt

httpdataeuropaeuontologyhasADetermined

httpdataeuropaeuontologyhasCurrency httpdataeuropaeuontologyhasAmount

httpdataeuropaeuInvoice123

httpdataeuropaeuValue234

httppublicationseuropaeuresourceauthoritycurrencyEUR 498730

13

2

A Linked Data example in RDFCALL FOR TENDER

Direct linking to

references on the web

(RDF)

hellipMDR

(RDF)

(RDF)

(RDF)

NUTS

CPV

MDR

hellip NUTS

hellip CPV

RDF for Call For

Tender

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns gtltrdfDescription rdfabout=CfT-Xgtltrdftype rdfresource=eprocCallForTender gtlteprochasCPV rdfresource=httpcpv30197220-4 link to CPV RDFlteprochasNUTS rdfresource=httpnutsLU000 link to NUTS RDFltdctpublisher rdfresource=httpcorporate-bodyPUBL Link to MDR RDF

ltrdfDescriptiongtltrdfRDFgt

14

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 7: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Two phases and final result

Two phases

bull Inception phase to prepare the ground

bull Development phase to build consensus on ontology in Working Group of stakeholders

Final result e-procurement ontology allowing wide range of applications to access and reuse procurement data

7

2

The problem and its impact

The problem

bull Concepts and relationships not fully documented

bull Data inherited from legacy paper-based origins

bull Different incompatible formats

The impact

bull Low transparency and monitoring

bull Difficulty to provide value-added services

bull Low interconnection between public procurement systems

bull Low reuse and access to data

8

2

Why an ontology

In general1

bull To share common understanding of the structure of information

bull To enable reuse of domain knowledge

bull To make domain assumptions explicit

In our case

bull Provide a conceptual model across existing procurement standards

bull model in standard Ontology Web Language (OWL)2

bull Enable procurement data to play in Linked Data3 environment for access by third-party applications

1See httpprotegestanfordedupublicationsontology_developmentontology101-noy-mcguinnesshtml2See httpswwww3orgOWL3See httpswwww3orgstandardssemanticwebdata

9

2

ltXMLgt

Closed world

e-procurement

silo

Message and process

based specifying all

information for

application integration

Linked Data

e-procurement

ontology

Open world

Application

independent

RDF

Exportand convert

CPV

NUTS

Eurostat

MDR

PPROC

Dublin Core

Match with budget amp spending

data

3rd-party procurement

services

NGOtransparency

watchdog

Journalists

Linked Open

Data Cloud

10

2

What is an ontology

A formal explicit description of concepts with their attributes and relationships including restrictions on values

In practical terms an ontology

bull defines classes ndash the things of interest

bull arranges classes in a hierarchy ndash subclasssuperclass

bull defines properties and allowed values ndash eg data types

bull defines relationships between classes

bull fills in values for the properties ndash eg controlled vocabularies

The definition of these semantics enable interoperability among different systems and applications

11

2

How is an ontology different

Other initiatives eg UBL1 CEN WSBII2

bull Focus on messaging to support the procurement process

bull Express information in XML structures (tree-container approach)

bull Operate in closed-world environments full specification for application integration ndash what is not specified is false

The e-procurement ontology

bull Formalises the semantics of all entities properties and relationships

bull Expresses information in RDF (Subject-Predicate-Object triples)

bull Operates in open-world of Linked Data specification of common elements for data integration ndash what is not specified is unknown

1 Universal Business Language See httpswwwoasis-openorgcommitteesubl2 CEN Business Interoperability Interfaces httpwwwcenbiieu

12

2

ltxml version=10 encoding=utf-8 gt

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns

xmlnsns0=httpdataeuropaeuontologygt

ltrdfDescription rdfabout=httpdataeuropaeuInvoice123gt

ltns0hasADeterminedgt

ltrdfDescription rdfabout=httpdataeuropaeuValue234gt

ltns0hasCurrency rdfresource=httppublicationseuropaeuresourceauthoritycurrencyEURgt

ltns0hasAmount rdfdatatype=httpwwww3org2001XMLSchemadecimalgt498730ltns0hasAmountgt

ltrdfDescriptiongt

ltns0hasADeterminedgt

ltrdfDescriptiongt

httpdataeuropaeuontologyhasADetermined

httpdataeuropaeuontologyhasCurrency httpdataeuropaeuontologyhasAmount

httpdataeuropaeuInvoice123

httpdataeuropaeuValue234

httppublicationseuropaeuresourceauthoritycurrencyEUR 498730

13

2

A Linked Data example in RDFCALL FOR TENDER

Direct linking to

references on the web

(RDF)

hellipMDR

(RDF)

(RDF)

(RDF)

NUTS

CPV

MDR

hellip NUTS

hellip CPV

RDF for Call For

Tender

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns gtltrdfDescription rdfabout=CfT-Xgtltrdftype rdfresource=eprocCallForTender gtlteprochasCPV rdfresource=httpcpv30197220-4 link to CPV RDFlteprochasNUTS rdfresource=httpnutsLU000 link to NUTS RDFltdctpublisher rdfresource=httpcorporate-bodyPUBL Link to MDR RDF

ltrdfDescriptiongtltrdfRDFgt

14

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 8: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

The problem and its impact

The problem

bull Concepts and relationships not fully documented

bull Data inherited from legacy paper-based origins

bull Different incompatible formats

The impact

bull Low transparency and monitoring

bull Difficulty to provide value-added services

bull Low interconnection between public procurement systems

bull Low reuse and access to data

8

2

Why an ontology

In general1

bull To share common understanding of the structure of information

bull To enable reuse of domain knowledge

bull To make domain assumptions explicit

In our case

bull Provide a conceptual model across existing procurement standards

bull model in standard Ontology Web Language (OWL)2

bull Enable procurement data to play in Linked Data3 environment for access by third-party applications

1See httpprotegestanfordedupublicationsontology_developmentontology101-noy-mcguinnesshtml2See httpswwww3orgOWL3See httpswwww3orgstandardssemanticwebdata

9

2

ltXMLgt

Closed world

e-procurement

silo

Message and process

based specifying all

information for

application integration

Linked Data

e-procurement

ontology

Open world

Application

independent

RDF

Exportand convert

CPV

NUTS

Eurostat

MDR

PPROC

Dublin Core

Match with budget amp spending

data

3rd-party procurement

services

NGOtransparency

watchdog

Journalists

Linked Open

Data Cloud

10

2

What is an ontology

A formal explicit description of concepts with their attributes and relationships including restrictions on values

In practical terms an ontology

bull defines classes ndash the things of interest

bull arranges classes in a hierarchy ndash subclasssuperclass

bull defines properties and allowed values ndash eg data types

bull defines relationships between classes

bull fills in values for the properties ndash eg controlled vocabularies

The definition of these semantics enable interoperability among different systems and applications

11

2

How is an ontology different

Other initiatives eg UBL1 CEN WSBII2

bull Focus on messaging to support the procurement process

bull Express information in XML structures (tree-container approach)

bull Operate in closed-world environments full specification for application integration ndash what is not specified is false

The e-procurement ontology

bull Formalises the semantics of all entities properties and relationships

bull Expresses information in RDF (Subject-Predicate-Object triples)

bull Operates in open-world of Linked Data specification of common elements for data integration ndash what is not specified is unknown

1 Universal Business Language See httpswwwoasis-openorgcommitteesubl2 CEN Business Interoperability Interfaces httpwwwcenbiieu

12

2

ltxml version=10 encoding=utf-8 gt

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns

xmlnsns0=httpdataeuropaeuontologygt

ltrdfDescription rdfabout=httpdataeuropaeuInvoice123gt

ltns0hasADeterminedgt

ltrdfDescription rdfabout=httpdataeuropaeuValue234gt

ltns0hasCurrency rdfresource=httppublicationseuropaeuresourceauthoritycurrencyEURgt

ltns0hasAmount rdfdatatype=httpwwww3org2001XMLSchemadecimalgt498730ltns0hasAmountgt

ltrdfDescriptiongt

ltns0hasADeterminedgt

ltrdfDescriptiongt

httpdataeuropaeuontologyhasADetermined

httpdataeuropaeuontologyhasCurrency httpdataeuropaeuontologyhasAmount

httpdataeuropaeuInvoice123

httpdataeuropaeuValue234

httppublicationseuropaeuresourceauthoritycurrencyEUR 498730

13

2

A Linked Data example in RDFCALL FOR TENDER

Direct linking to

references on the web

(RDF)

hellipMDR

(RDF)

(RDF)

(RDF)

NUTS

CPV

MDR

hellip NUTS

hellip CPV

RDF for Call For

Tender

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns gtltrdfDescription rdfabout=CfT-Xgtltrdftype rdfresource=eprocCallForTender gtlteprochasCPV rdfresource=httpcpv30197220-4 link to CPV RDFlteprochasNUTS rdfresource=httpnutsLU000 link to NUTS RDFltdctpublisher rdfresource=httpcorporate-bodyPUBL Link to MDR RDF

ltrdfDescriptiongtltrdfRDFgt

14

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 9: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Why an ontology

In general1

bull To share common understanding of the structure of information

bull To enable reuse of domain knowledge

bull To make domain assumptions explicit

In our case

bull Provide a conceptual model across existing procurement standards

bull model in standard Ontology Web Language (OWL)2

bull Enable procurement data to play in Linked Data3 environment for access by third-party applications

1See httpprotegestanfordedupublicationsontology_developmentontology101-noy-mcguinnesshtml2See httpswwww3orgOWL3See httpswwww3orgstandardssemanticwebdata

9

2

ltXMLgt

Closed world

e-procurement

silo

Message and process

based specifying all

information for

application integration

Linked Data

e-procurement

ontology

Open world

Application

independent

RDF

Exportand convert

CPV

NUTS

Eurostat

MDR

PPROC

Dublin Core

Match with budget amp spending

data

3rd-party procurement

services

NGOtransparency

watchdog

Journalists

Linked Open

Data Cloud

10

2

What is an ontology

A formal explicit description of concepts with their attributes and relationships including restrictions on values

In practical terms an ontology

bull defines classes ndash the things of interest

bull arranges classes in a hierarchy ndash subclasssuperclass

bull defines properties and allowed values ndash eg data types

bull defines relationships between classes

bull fills in values for the properties ndash eg controlled vocabularies

The definition of these semantics enable interoperability among different systems and applications

11

2

How is an ontology different

Other initiatives eg UBL1 CEN WSBII2

bull Focus on messaging to support the procurement process

bull Express information in XML structures (tree-container approach)

bull Operate in closed-world environments full specification for application integration ndash what is not specified is false

The e-procurement ontology

bull Formalises the semantics of all entities properties and relationships

bull Expresses information in RDF (Subject-Predicate-Object triples)

bull Operates in open-world of Linked Data specification of common elements for data integration ndash what is not specified is unknown

1 Universal Business Language See httpswwwoasis-openorgcommitteesubl2 CEN Business Interoperability Interfaces httpwwwcenbiieu

12

2

ltxml version=10 encoding=utf-8 gt

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns

xmlnsns0=httpdataeuropaeuontologygt

ltrdfDescription rdfabout=httpdataeuropaeuInvoice123gt

ltns0hasADeterminedgt

ltrdfDescription rdfabout=httpdataeuropaeuValue234gt

ltns0hasCurrency rdfresource=httppublicationseuropaeuresourceauthoritycurrencyEURgt

ltns0hasAmount rdfdatatype=httpwwww3org2001XMLSchemadecimalgt498730ltns0hasAmountgt

ltrdfDescriptiongt

ltns0hasADeterminedgt

ltrdfDescriptiongt

httpdataeuropaeuontologyhasADetermined

httpdataeuropaeuontologyhasCurrency httpdataeuropaeuontologyhasAmount

httpdataeuropaeuInvoice123

httpdataeuropaeuValue234

httppublicationseuropaeuresourceauthoritycurrencyEUR 498730

13

2

A Linked Data example in RDFCALL FOR TENDER

Direct linking to

references on the web

(RDF)

hellipMDR

(RDF)

(RDF)

(RDF)

NUTS

CPV

MDR

hellip NUTS

hellip CPV

RDF for Call For

Tender

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns gtltrdfDescription rdfabout=CfT-Xgtltrdftype rdfresource=eprocCallForTender gtlteprochasCPV rdfresource=httpcpv30197220-4 link to CPV RDFlteprochasNUTS rdfresource=httpnutsLU000 link to NUTS RDFltdctpublisher rdfresource=httpcorporate-bodyPUBL Link to MDR RDF

ltrdfDescriptiongtltrdfRDFgt

14

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 10: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

ltXMLgt

Closed world

e-procurement

silo

Message and process

based specifying all

information for

application integration

Linked Data

e-procurement

ontology

Open world

Application

independent

RDF

Exportand convert

CPV

NUTS

Eurostat

MDR

PPROC

Dublin Core

Match with budget amp spending

data

3rd-party procurement

services

NGOtransparency

watchdog

Journalists

Linked Open

Data Cloud

10

2

What is an ontology

A formal explicit description of concepts with their attributes and relationships including restrictions on values

In practical terms an ontology

bull defines classes ndash the things of interest

bull arranges classes in a hierarchy ndash subclasssuperclass

bull defines properties and allowed values ndash eg data types

bull defines relationships between classes

bull fills in values for the properties ndash eg controlled vocabularies

The definition of these semantics enable interoperability among different systems and applications

11

2

How is an ontology different

Other initiatives eg UBL1 CEN WSBII2

bull Focus on messaging to support the procurement process

bull Express information in XML structures (tree-container approach)

bull Operate in closed-world environments full specification for application integration ndash what is not specified is false

The e-procurement ontology

bull Formalises the semantics of all entities properties and relationships

bull Expresses information in RDF (Subject-Predicate-Object triples)

bull Operates in open-world of Linked Data specification of common elements for data integration ndash what is not specified is unknown

1 Universal Business Language See httpswwwoasis-openorgcommitteesubl2 CEN Business Interoperability Interfaces httpwwwcenbiieu

12

2

ltxml version=10 encoding=utf-8 gt

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns

xmlnsns0=httpdataeuropaeuontologygt

ltrdfDescription rdfabout=httpdataeuropaeuInvoice123gt

ltns0hasADeterminedgt

ltrdfDescription rdfabout=httpdataeuropaeuValue234gt

ltns0hasCurrency rdfresource=httppublicationseuropaeuresourceauthoritycurrencyEURgt

ltns0hasAmount rdfdatatype=httpwwww3org2001XMLSchemadecimalgt498730ltns0hasAmountgt

ltrdfDescriptiongt

ltns0hasADeterminedgt

ltrdfDescriptiongt

httpdataeuropaeuontologyhasADetermined

httpdataeuropaeuontologyhasCurrency httpdataeuropaeuontologyhasAmount

httpdataeuropaeuInvoice123

httpdataeuropaeuValue234

httppublicationseuropaeuresourceauthoritycurrencyEUR 498730

13

2

A Linked Data example in RDFCALL FOR TENDER

Direct linking to

references on the web

(RDF)

hellipMDR

(RDF)

(RDF)

(RDF)

NUTS

CPV

MDR

hellip NUTS

hellip CPV

RDF for Call For

Tender

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns gtltrdfDescription rdfabout=CfT-Xgtltrdftype rdfresource=eprocCallForTender gtlteprochasCPV rdfresource=httpcpv30197220-4 link to CPV RDFlteprochasNUTS rdfresource=httpnutsLU000 link to NUTS RDFltdctpublisher rdfresource=httpcorporate-bodyPUBL Link to MDR RDF

ltrdfDescriptiongtltrdfRDFgt

14

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 11: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

What is an ontology

A formal explicit description of concepts with their attributes and relationships including restrictions on values

In practical terms an ontology

bull defines classes ndash the things of interest

bull arranges classes in a hierarchy ndash subclasssuperclass

bull defines properties and allowed values ndash eg data types

bull defines relationships between classes

bull fills in values for the properties ndash eg controlled vocabularies

The definition of these semantics enable interoperability among different systems and applications

11

2

How is an ontology different

Other initiatives eg UBL1 CEN WSBII2

bull Focus on messaging to support the procurement process

bull Express information in XML structures (tree-container approach)

bull Operate in closed-world environments full specification for application integration ndash what is not specified is false

The e-procurement ontology

bull Formalises the semantics of all entities properties and relationships

bull Expresses information in RDF (Subject-Predicate-Object triples)

bull Operates in open-world of Linked Data specification of common elements for data integration ndash what is not specified is unknown

1 Universal Business Language See httpswwwoasis-openorgcommitteesubl2 CEN Business Interoperability Interfaces httpwwwcenbiieu

12

2

ltxml version=10 encoding=utf-8 gt

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns

xmlnsns0=httpdataeuropaeuontologygt

ltrdfDescription rdfabout=httpdataeuropaeuInvoice123gt

ltns0hasADeterminedgt

ltrdfDescription rdfabout=httpdataeuropaeuValue234gt

ltns0hasCurrency rdfresource=httppublicationseuropaeuresourceauthoritycurrencyEURgt

ltns0hasAmount rdfdatatype=httpwwww3org2001XMLSchemadecimalgt498730ltns0hasAmountgt

ltrdfDescriptiongt

ltns0hasADeterminedgt

ltrdfDescriptiongt

httpdataeuropaeuontologyhasADetermined

httpdataeuropaeuontologyhasCurrency httpdataeuropaeuontologyhasAmount

httpdataeuropaeuInvoice123

httpdataeuropaeuValue234

httppublicationseuropaeuresourceauthoritycurrencyEUR 498730

13

2

A Linked Data example in RDFCALL FOR TENDER

Direct linking to

references on the web

(RDF)

hellipMDR

(RDF)

(RDF)

(RDF)

NUTS

CPV

MDR

hellip NUTS

hellip CPV

RDF for Call For

Tender

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns gtltrdfDescription rdfabout=CfT-Xgtltrdftype rdfresource=eprocCallForTender gtlteprochasCPV rdfresource=httpcpv30197220-4 link to CPV RDFlteprochasNUTS rdfresource=httpnutsLU000 link to NUTS RDFltdctpublisher rdfresource=httpcorporate-bodyPUBL Link to MDR RDF

ltrdfDescriptiongtltrdfRDFgt

14

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 12: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

How is an ontology different

Other initiatives eg UBL1 CEN WSBII2

bull Focus on messaging to support the procurement process

bull Express information in XML structures (tree-container approach)

bull Operate in closed-world environments full specification for application integration ndash what is not specified is false

The e-procurement ontology

bull Formalises the semantics of all entities properties and relationships

bull Expresses information in RDF (Subject-Predicate-Object triples)

bull Operates in open-world of Linked Data specification of common elements for data integration ndash what is not specified is unknown

1 Universal Business Language See httpswwwoasis-openorgcommitteesubl2 CEN Business Interoperability Interfaces httpwwwcenbiieu

12

2

ltxml version=10 encoding=utf-8 gt

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns

xmlnsns0=httpdataeuropaeuontologygt

ltrdfDescription rdfabout=httpdataeuropaeuInvoice123gt

ltns0hasADeterminedgt

ltrdfDescription rdfabout=httpdataeuropaeuValue234gt

ltns0hasCurrency rdfresource=httppublicationseuropaeuresourceauthoritycurrencyEURgt

ltns0hasAmount rdfdatatype=httpwwww3org2001XMLSchemadecimalgt498730ltns0hasAmountgt

ltrdfDescriptiongt

ltns0hasADeterminedgt

ltrdfDescriptiongt

httpdataeuropaeuontologyhasADetermined

httpdataeuropaeuontologyhasCurrency httpdataeuropaeuontologyhasAmount

httpdataeuropaeuInvoice123

httpdataeuropaeuValue234

httppublicationseuropaeuresourceauthoritycurrencyEUR 498730

13

2

A Linked Data example in RDFCALL FOR TENDER

Direct linking to

references on the web

(RDF)

hellipMDR

(RDF)

(RDF)

(RDF)

NUTS

CPV

MDR

hellip NUTS

hellip CPV

RDF for Call For

Tender

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns gtltrdfDescription rdfabout=CfT-Xgtltrdftype rdfresource=eprocCallForTender gtlteprochasCPV rdfresource=httpcpv30197220-4 link to CPV RDFlteprochasNUTS rdfresource=httpnutsLU000 link to NUTS RDFltdctpublisher rdfresource=httpcorporate-bodyPUBL Link to MDR RDF

ltrdfDescriptiongtltrdfRDFgt

14

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 13: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

ltxml version=10 encoding=utf-8 gt

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns

xmlnsns0=httpdataeuropaeuontologygt

ltrdfDescription rdfabout=httpdataeuropaeuInvoice123gt

ltns0hasADeterminedgt

ltrdfDescription rdfabout=httpdataeuropaeuValue234gt

ltns0hasCurrency rdfresource=httppublicationseuropaeuresourceauthoritycurrencyEURgt

ltns0hasAmount rdfdatatype=httpwwww3org2001XMLSchemadecimalgt498730ltns0hasAmountgt

ltrdfDescriptiongt

ltns0hasADeterminedgt

ltrdfDescriptiongt

httpdataeuropaeuontologyhasADetermined

httpdataeuropaeuontologyhasCurrency httpdataeuropaeuontologyhasAmount

httpdataeuropaeuInvoice123

httpdataeuropaeuValue234

httppublicationseuropaeuresourceauthoritycurrencyEUR 498730

13

2

A Linked Data example in RDFCALL FOR TENDER

Direct linking to

references on the web

(RDF)

hellipMDR

(RDF)

(RDF)

(RDF)

NUTS

CPV

MDR

hellip NUTS

hellip CPV

RDF for Call For

Tender

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns gtltrdfDescription rdfabout=CfT-Xgtltrdftype rdfresource=eprocCallForTender gtlteprochasCPV rdfresource=httpcpv30197220-4 link to CPV RDFlteprochasNUTS rdfresource=httpnutsLU000 link to NUTS RDFltdctpublisher rdfresource=httpcorporate-bodyPUBL Link to MDR RDF

ltrdfDescriptiongtltrdfRDFgt

14

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 14: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

A Linked Data example in RDFCALL FOR TENDER

Direct linking to

references on the web

(RDF)

hellipMDR

(RDF)

(RDF)

(RDF)

NUTS

CPV

MDR

hellip NUTS

hellip CPV

RDF for Call For

Tender

ltrdfRDF xmlnsrdf=httpwwww3org19990222-rdf-syntax-ns gtltrdfDescription rdfabout=CfT-Xgtltrdftype rdfresource=eprocCallForTender gtlteprochasCPV rdfresource=httpcpv30197220-4 link to CPV RDFlteprochasNUTS rdfresource=httpnutsLU000 link to NUTS RDFltdctpublisher rdfresource=httpcorporate-bodyPUBL Link to MDR RDF

ltrdfDescriptiongtltrdfRDFgt

14

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 15: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

The identifier challenge

Linked Data requires all entities to be uniquely identified

These identifiers are available for some entities eg

bull Contracting Authorities MDR Corporate Body Name Authority List for European and (some) international organisations

bull Economic Operators OpenCorporatesorg

Further activities

bull Linked Open Data for NUTS at Eurostat

bull National company register and other base registries

15

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 16: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

16

Questions

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 17: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

17

Draft Project Charter and time plan

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 18: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Project phases Phase 1 Inception

November 2016mdashJune 2017

bull Development and documentation of methodology with application of methodology to three use cases

bull Delivery of initial conceptual model and ontology

bull Set-up of Working Group and working environment

bull Input from Working Group to test the methodology

bull Definition of additional use cases

bull Establishment of Project Charter

18

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 19: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Project phases Phase 2 Development

September 2017mdashJune 2018

bull Development of complete specification and ontology by Working Group applying methodology to additional use cases

bull Iterative publication of working drafts

bull Public review of final draft specification and ontology

bull Resolution of public comments

bull Formal publication

19

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 20: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Project Charter scope

Includes (IN scope)

bull Development of e-procurement ontology supporting the whole of the procurement process in a collaborative effort by a Working Group with representation of main stakeholders

bull Delivery of specification with conceptual model and OWL ontology

bull Deployment on the Metadata Registry at Publications Office

Excludes (OUT scope)

bull Implementation of systems that use the ontology

bull Change management and maintenance

bull Creation of implementation guidelines

20

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 21: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Project Charter constraints amp assumptions

Assumptions

bull Ontology will respect the data standards and structures in the environment of the Publications Office

bull Ontology will be expressed in OWL2 conformant to W3C conditions

bull Ontology will be made available under open licence

bull Working group to include experts in e-procurement data modelling ontology design and Linked Open Data technologies

bull Members share objective of reaching consensus by finding common ground across different perspectives

21

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 22: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

22

Time plan November 2016mdashMarch 2017

bull Proposed methodology

bull Initial ontology for three use cases

bull Proposed Project Charter

bull Working Group and work environment

23 March 2017 todays meeting

bull Presentation of results so far

AprilmdashJune 2017

bull Input from the Working Group

Review of methodology and charter

Review of initial ontology

bull Meetings with Working Group

bull Refinement of additional use cases

Inception phase

22

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 23: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

23

Time plan

Execution phase

(may be revised as deemed necessary by the Working Group)

Event Date

First WG meeting September 2017 (Milestone 1)

First draft of specification October 2017

Second WG meeting December 017

Second draft of specification January 2018

Third WG meeting February 2018

Third draft of specification March 2018

Fourth WG meeting April 2018

Publication of fourth draft for public review April 2018 (Milestone 2)

Fifth draft of specification resolving public comments June 2018

Fifth WG meeting June 2018

Publication of final specification June 2018 (Milestone 3)

23

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 24: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

24

Questions

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 25: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

25

Working environment

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 26: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Working environment

Mailing list

Input of general interest for the working group members

GitHub

Any issuesolutioncomment concerning documents uploaded on the publication channel (Joinup) The editor and chair will assure the periodicity of the maintenance (eg issues linked to documentation issues and solutions categorised)

Resource Producttool

Ontology development tool Proteacutegeacute httpprotegestanfordedu

Model visualisation tool TBD

Conference call facility Adobe Connect httpsec-wacsadobeconnectcom

Mailing list Joinup eprocurementontologyjoinupeceuropaeu

Issue tracker GitHub httpsgithubcomeprocurementontologyeprocurementontology

Publication channel Joinup httpsjoinupeceuropaeuasseteprocurementontology

26

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 27: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

27

Questions

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 28: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

28

Lunch break

1200-1300

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 29: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

1 Round table

2 Introduction to the project

3 Draft Project charter and time plan

4 Working environment

5 Methodology

6 Initial results ndash conceptual model based on three use cases

7 Additional use cases for consideration

8 Next steps planning work until June 2017

Lunch

Agenda

29

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 30: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

30

Methodology

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 31: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Overview of the Methodology

Adaptation of ISA Process and methodology for developing semantic agreements1

Ontology development approach based on Ontology Development 101 A Guide to Creating Your First Ontology2 by Natalya F Noy and Deborah L McGuinness

Reuse approach based on A Contextual Approach to Ontology Reuse Methodology Methods and Tools for the Semantic Web3 by Elena Pacircslaru-Bontaş

Tested and refined based on application to the three use cases

1 See httpsjoinupeceuropaeunode670062 See httpprotegestanfordedupublicationsontology_developmentontology101pdf3 See httpwwwdissfu-berlindedissreceiveFUDISS_thesis_000000002738

31

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 32: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Five main steps

32

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 33: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

33

Questions

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 34: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

34

Initial resultsDraft conceptual model based on three use

cases

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 35: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Initial results

Methodology

Three use cases

bull Data journalism

bull Automated match-making

bull Verifying VAT payments on intracommunity service provision

Information requirements

Naming and identifier conventions

Initial conceptual model and ontology

Challenges and how to overcome them

35

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 36: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Use case 1 Data journalism

Citizens want to know how public money is spent

What was sold by whom at what price

Need for journalists to access process interpret and combine public data from different sources

Different data sources should be accessed in a harmonised way using common semantics

36

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 37: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Use case 2 Automated matchmaking

During the e-notification phase a system checks the procurement criteria against the capabilities of economic operators

If an economic operator meets the procurement criteria the system automatically informs the economic operator

If procurement criteria are partly met the system proposes economic operators that can work together

For economic operators time gain easier identification of partners optimised partnerships

For contracting authorities increased competition and improved quality of tenderers

37

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 38: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Use case 3 Verifying VAT payments

During post-award phase Member States can access each othersrsquo systems in order to get information about profile invoicing and payment details of economic operators

A Member State can check whether the declared VAT amount corresponds to the taxed value of the awarded contract

38

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 39: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

39

Step 1 Define use cases The following template should be used

1 Select and update use cases from the landscaping study

The working group should review the use cases proposed in the landscaping report and select the ones that should be in scope and proposes updates to the use cases if they deem it necessary

2 Define additional use cases that the e-procurement ontology should cover

The working group members should propose and agree on new use cases where they feel a need is not covered by the selected use cases or from the sum of more than one use case

Element Description

Title A short phrase that can be used to refer to the use case

Category The type of use case one of

Transparency and monitoring

Innovation amp value added services

Interconnection of public procurement systems

Description Concise text that provides basic information about the actors

the goal and the intended results of the use case

Actors Further details on the agents (persons organisations or

software programs) involved in the use case

Final recipients The actors that receive the results or benefits from the use

case

Preconditions Anything that can be said about the situation before the use

case begins

Flow A step-by-step description of the actions taken and responses

received by the user

Comments Any other observation related to the use case

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 40: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Step 2 derive requirements from the use casesGoal Define the scope amp domain of the ontology

1 Highlight the entities that are mentioned in the use caseMark important nouns documents agents criteria item descriptions places time periods etc

2 Generalise the entities from individuals to conceptsEg ldquothe European Commissionrdquo =gt ldquoa contracting authorityrdquo

3 Enter the entities in the requirements template

Information

requirement

Description Related

Use

Case

IR01 The concept of economic operator MUST be definedUC1 UC2

UC3

IR02 The concept of contract award notice MUST be defined UC2

40

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 41: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Step 3 Develop a conceptual data modelGoal Identify and describe entities with their attributes and relationships

1 Enumerate important concepts based on information requirementsList concepts from the information requirements in a list or UML diagram

2 Identify missing concepts and the class hierarchyClose the gaps

3 Define the classesPropose amp agree on definitions for the classes following the template

4 Define the properties of classes

5 Define the facets of the propertiesCardinalities and value spaces controlled vocabularies amp code lists

41

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 42: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Step 3 Develop a conceptual data model

Classes

Properties

Label Definition

Contracting Authority State regional or local authorities bodies governed by public law or associations formed by one or more

such authorities or one or more such bodies governed by public law

Economic Operator Any persons andor entities which offer the execution of works the supply of products or the provision of

services on the market irrespective of the legal form under which they have chosen to operate

hellip hellip

Label Definition Class Data type Card

hasName This property specifies a name for an economic operator Economic Operator String 1n

hellip hellip hellip hellip hellip

42

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 43: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

43

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 44: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Step 3 Develop a conceptual data model

Subset

44

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 45: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Step 4 Consider reusing existing ontologies

Goal identify and reuse existing concepts in order to maximise interoperability with existing systems and applications

1 Analyse related ontologies and vocabularies for similar entities and relationships

2 Choose relevant entities from other ontologies

Label URI

Contracting Authority

httpdataeuropaeueprocontologyContractingAuthority

Considering to reuse

bull httpdataeuropaeum8gPublicOrganisation

Economic Operator

httpdataeuropaeueprocontologyEconomicOperatorConsidering to reuse

Considering to reuse

bull httpwwww3orgnsorgOrganization (for organisations)

bull httpwwww3orgnsregorgRegisteredOrganization (for businesses)

45

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 46: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Potential sources for reuse

ISA Core Vocabularies httpsjoinupeceuropaeunode145983

PPROC httpcontsemunizaresdefsector-publicopprochtml

Paraguayan ontology httpswwwcontratacionesgovpy

FOAF httpxmlnscomfoafspec

Dublin Core httpdublincoreorgdocumentsdcmi-terms

SKOS httpswwww3org200908skos-referenceskoshtml

A more exhaustive list is represented in the Landscaping report on

policy support for eProcurement

httpsjoinupeceuropaeunode159724

46

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 47: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Reuse levelsFor each concept coming from other ontologies a reusability level should be fixed It is based on this level that the working group will decide whether to reuse the concept or not

47

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 48: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Step 5 define and implement an OWL ontologyAs a last step the agreed ontology should be described in the OWL DL1 format and published on the Metadata Registry (MDR) of the Publications Office of the EU

1 OWL DL httpswwww3orgTRowl-guide

ltrdfRDF xmlns=httpdataeuropaeueprocontologyxmlbase=httpdataeuropaeueprocontologyxmlnsrdf=httpwwww3org19990222-rdf-syntax-nsxmlnsdct=httppurlorgdctermsxmlnsowl=httpwwww3org200207owlxmlnsrdfs=httpwwww3org200001rdf-schemagt

ltowlOntology rdfabout=httpdataeuropaeueprocontologygtltdctcreator rdfresource=httppublicationseuropaeuresourceauthoritycorporate-bodyPUBLgtltrdfslabel xmllang=engteProcurement OntologyltrdfslabelgtltrdfsseeAlso rdfresource=httpsjoinupeceuropaeuasseteprocurementontologygtltrdfscomment xmllang=engtAn ontology to describe the information model of the eProcurement processltrdfscommentgt

ltowlOntologygt

lt-- Class --gt

ltowlClass rdfabout=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfslabel xmllang=engtContracting Authorityltrdfslabelgt

ltrdfscomment xmllang=engtState regional or local authorities bodies governed by public law or associations formed by one or more such authorities or one or more such bodies governed by public law other than those authorities bodies or associations which pursue one of the activities referred to in Annex II of the Directive 201423EU of the European Parliament and of the Council ltrdfslabelgt

ltrdfssubClassOf rdfresource=httpxmlnscomfoaf01Agent gtltowlClassgt

lt-- Object property = relationship between classes --gt

ltowlObjectProperty rdfabout=httpdataeuropaeueprocontologypublishesgtltrdfsdomain rdfresource=httpdataeuropaeueprocontologyContractingAuthoritygtltrdfsrange rdfresource=httpdataeuropaeueprocontologyCallForTendergtltrdfscomment xmllang=engtThis property links a contracting authority to a call for tender that it makes availableltrdfscommentgtltrdfslabel xmllang=engtpublishesltrdfslabelgt

ltowlObjectPropertygt

ltrdfRDFgt

48

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 49: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

49

Questions

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 50: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

50

Additional use cases

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 51: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Additional use cases

Transparency and monitoring

Data journalism

Increase transparency and public understandability

Monitor the money flow

Detect fraud and compliance with procurement criteria

Audit procurement process

Cross-validate data from different parts of the procurement process

51

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 52: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Additional use cases

Innovation and value added services

Automated matchmaking of procured services and products with businesses

Automated validation of procurement criteria

Alerting services

Data analytics on public procurement

Interconnection of public procurement systems

Verifying VAT payments on intracommunity service provision

Introduce automated classification systems in public procurement systems

52

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 53: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

53

Next steps

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 54: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Tasks for the Working Group AprilmdashJune 2017

bull Before Easter- Contribute propose amp review of methodology charter and initial ontology on GitHub

bull Before Easter- Refinement of additional use cases

Propose changes in existing use cases from the landscaping report

Propose new use cases by filling the template provided in the specification

bull 26 April 2017 ndash 2nd Meeting with Working Group ndash Agreement on use cases

Read the proposed changes in the documents before the meeting

bull 8 May 2017 ndash Refinement of methodology charter and initial ontology on GitHub

bull TDB 23 May 2017 ndash 3rd Meeting with Working Group

Read the final propositions for acceptance

54

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 55: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

Next steps

Date Task Task owner

Today First working group meeting presentation of the project

WG members chair editor

Before Easter Deadline for submitting comments on the documentation and use cases through GitHub

WG members

19 April 2017 New version of the documents Editor

26 April 2017 2nd working group meeting (virtual) consensus on the use cases

WG members chair editor

8 May 2017 Deadline for submitting comments on GitHub WG members

16 May 2017 Final version of the documents Editor

TBD 23 May 2017 3rd working group meeting (virtual) final agreementon the documents

WG members chair editor

55

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 56: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

56

Questions

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology

Page 57: e-procurement ontology workshop - Joinup · 2017-10-03 · • Ontology will respect the data standards and structures in the environment of the Publications Office • Ontology will

2

57

e-Procurement Ontology

Contact us

NatalieMuricpublicationseuropaeu

eprocurementontologyjoinupeceuropaeu

Join the e-Procurement Community

httpsjoinupeceuropaeuasseteprocurementontology