Implementation

In this section, the discussion on the domain modelings follows with the implementation of the developed models for the three artifacts, OCW, Publications, Events (as discussed before). Due to the technical needs and priorities of this research with regard to its objectives, the implementation of the data models for these

three domains have not been developed in the same level nor in the same platform. The conceptualized domain of the scholarly communication is aimed to be shown as RDF triples by utilizing RDF9, RDF Schema10and OWL11.

Implementation of the OpenCourseWare Model: The model that was conceptualized for OCW was extended as a quality framework for online courses (will be discussed in section 4.3). The implementation of the defined concepts was left on the shoulders of the SlideWiki.org developers. To the best of our knowledge, most of the defined terms have been turned to a feature inside the platform. The semantic representation of the concepts such as content Creator, language information and material of the OCW are developed [77] in the recent version of SlideWiki.org platform which was based on the work done by the conceptualization of this research.

Implementation of the OpenAIRE LOD Model: The database management system used for OpenAIRE LOD is Virtuoso12. It provides an environment to crate the graph of data and based on the injected ontology. The ontology developed for OpenAIRE LOD based on the initial data model has been created as a graph also. At the time of loading data into Virtuoso, the ontology is also imported using the Conductor user interface13_{. All the selected or defined ontologies are imported using the}

following command: SPARQL LOAD URL of the Ontology1; Ontology 2,.... Then the data is connected to the imported ontologies. In this way the OpenAIRE LOD graph has been created. In addition to the concepts defined inside the ontology, one needs to introduce the ontology, its license, online link, the graph namespace prefix, and date or creation at the time of importing the ontology. Parts of the technical challenges that was faced in this step is skipped to be discussed here. A detailed description of the required steps can be found in the main help page by Virtuoso14.

Implementation of the OpenResearch.org Model: In modeling our ontology of scientific events and their stakeholders (participants, organizers, publishers, sponsors, etc.), we followed the best practices of reusingterms from existing ontologies (cf. [208]) and applying ontology design patterns [91]. Domain- specific candidates for reuse include generic ontologies about publishing as well as ontologies about scientific conferences. The GND ontology [94] defines authorities established in publishing, including events and persons and their roles. The Semantic Web Conference ontology (SWC) considers academic conferences [188]; it has originally been designed to support the European and International Semantic Web Conferences. The Ontology Alignment Evaluation Initiative (OAEI) provides further conference ontologies that vary in size, language, domain, and modeling style (cf. [301] for the 2015 conference ontologies and [262] for the full series of OAEI evaluation events). For any further terminology not sufficiently covered by existing ontologies, we defined our own ontology called OpenResearch (OR) (abbreviated “or”). The OpenResearch ontology employs the Content Ontology Design Pattern15to model participation16. The developed ontology which was introduced in the previous sections is implemented in the OpenResearch.org platform that will be introduced in details in the next chapters.

In this section, we introduce the implementation of OR ontology with the focus on scholarly events. Figure 4.5 is a representation of the OR data model suing Protegé [192]. The vocabulary used in OpenResearch reuses existing vocabularies from related domains, since reuse increases the value of

9_{https://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/} 10_{https://www.w3.org/TR/rdf-schema/} 11_{https://www.w3.org/TR/owl-semantics/} 12_{https://virtuoso.openlinksw.com/} 13_{http://data.persee.fr/conductor/} 14_{http://vos.openlinksw.com/owiki/wiki/VOS/VirtTipsAndTricksGuideImportOntology} 15_{http://ontologydesignpatterns.org/wiki/Submissions:Participation}

4.1 Metadata Domains of Scholarly Communication

Figure 4.5: The core concepts of the OpenResearch ontology. Part of the main concepts related to scholarly events is shown. wiki:EKAW_2016 swc:ConferenceEvent rdf:type or:StandAloneEvent _rdf:type export:EKAW_2016 _{rdfs:isDefinedBy} EKAW 2016

Datatype: xsd:string rdfs:label or:acronym 20th International Conference on Knowledge …

Datatype: xsd:string dc:title wiki:EKAW or:eventInSeries 2016-11-19Z Datatype: xsd:date icaltzd:dtstart 2016-11-23Z Datatype: xsd:date icaltzd:dtend http://ekaw2016.cs.unibo.it foaf:homepage http://openresearch.org/EKAW_2016 swivt:page wiki:Bologna or:locationCity wiki:Italy or:locationCountry 2016-07-08Z Datatype: xsd:date or:abstractDeadline 2016-07-15Z Datatype: xsd:date or:submissionDeadline http://www.easychair.org/conferences/?conf=ekaw2016 or:submissionLink wiki:Paolo_Ciancarini or:generalChair wiki:Eva_Blomqvist or:programChair wiki:Fabio_Vitali or:programChair

Figure 4.6: Event example. An exemplary usage of the conceptualization which is showing the conference of EKAW 2016 resource.

semantic data. Existing related vocabularies are the Semantic Web Conference Ontology (SWC)17_{, the}

Semantic Web Portal Ontology(SWPO)18, and the Funding, Research Administration and Projects Ontology(FRAPO)19, as well as schema.org. The SWC, SWPO and schema.org vocabularies provide means for modeling general events and SWC and SWPO also conferences. FRAPO provides terms to express scientific projects and their relations. The property alignment is implemented using the SMW mechanism for importing vocabularies20. This includes definitions of the reused vocabularies in special vocabulary pages e.g. for SWC21, which lists all imported properties and annotates them with SMW data types for the values. Wiki categories and properties are then aligned with the vocabulary terms using

17_{http://data.semanticweb.org/ns/swc/swc_2009-05-09.html}

18_{http://sw-portal.deri.org/ontologies/swportal}

19_{http://www.sparontologies.net/ontologies/frapo/source.html}

20_{https://www.semantic-mediawiki.org/wiki/Help:Import_vocabulary}

special imported from links. For instance Category:Conference is aligned to swc:ConferenceEvent with [[imported from::swc:ConferenceEvent]]. For modeling the calls and roles for a conference we defined new properties in our own vocabulary22. Fig. 4.623provides an example for using the data model. In contrast to the existing data model for calls and roles in the SWC ontology we are following a flat structure, which allows users, e.g., to directly attach a deadline to an event rather than creating a new instance for a call in addition to the actual event.

{{ E v e n t

| Acronym = EKAW 2016

| T i t l e = 20 t h I n t e r n a t i o n a l C o n f e r e n c e on Knowledge E n g i n e e r i n g and Knowledge Management | S e r i e s = EKAW | Type = C o n f e r e n c e | F i e l d = Knowledge E n g i n e e r i n g | S t a r t d a t e = 2 0 1 6 / 1 1 / 1 9 | End d a t e = 2 0 1 6 / 1 1 / 2 3 | Homepage = ekaw2016 . c s . u n i b o . i t | T w i t t e r a c c o u n t = @ekaw2016 | C i t y = B o l o g n a | C o u n t r y = I t a l y | S u b m i s s i o n d e a d l i n e = 2 0 1 6 / 0 7 / 1 5 | A b s t r a c t d e a d l i n e = 2 0 1 6 / 0 7 / 0 8 | h a s g e n e r a l c h a i r = P a o l o C i a n c a r i n i , | h a s p r o g r a m c h a i r = Eva B l o m q v i s t , F a b i o V i t a l i , | h a s w o r k s h o p c h a i r = Matthew H o r r i d g e , J u n Zhao , | h a s demo c h a i r = T u d o r Groza , M a r i Carmen , | S u b m i t t e d p a p e r s = 171

| A c c e p t e d p a p e r s = 51

| h a s P r o c e e d i n g s L i n k = h t t p s : / / l i n k . s p r i n g e r . com / book /10.1007/978 −3 −319 −49004 −5 }}

Listing 4.2: Example of Event. An event description on OpenResearch.org.