Headless Server Manual

Total Page:16

File Type:pdf, Size:1020Kb

Headless Server Manual COREMEDIA CONTENT CLOUD Headless Server Manual Headless Server Developer Manual Headless Server Manual | Copyright CoreMedia GmbH © 2021 CoreMedia GmbH Ludwig-Erhard-Straße 18 20459 Hamburg International All rights reserved. No part of this manual or the corresponding program may be reproduced or copied in any form (print, photocopy or other process) without the written permission of CoreMedia GmbH. Germany Alle Rechte vorbehalten. CoreMedia und weitere im Text erwähnte CoreMedia Produkte sowie die entsprechenden Logos sind Marken oder eingetragene Marken der CoreMedia GmbH in Deutschland. Alle anderen Namen von Produkten sind Marken der jeweiligen Firmen. Das Handbuch bzw. Teile hiervon sowie die dazugehörigen Programme dürfen in keiner Weise (Druck, Fotokopie oder sonstige Verfahren) ohne schriftliche Genehmigung der CoreMedia GmbH reproduziert oder vervielfältigt werden. Unberührt hiervon bleiben die gesetzlich erlaubten Nutzungsarten nach dem UrhG. Licenses and Trademarks All trademarks acknowledged. September 08, 2021 (Release 2107 ) COREMEDIA CONTENT CLOUD ii Headless Server Manual | 1. Preface ................................................................................ 1 1.1. Audience .................................................................... 2 1.2. CoreMedia Services ........................................................ 3 1.2.1. Registration ....................................................... 3 1.2.2. CoreMedia Releases ............................................. 4 1.2.3. Documentation .................................................. 4 1.2.4. CoreMedia Training .............................................. 8 1.2.5. CoreMedia Support .............................................. 8 1.3. Typographic Conventions ................................................ 10 1.4. Changelog ................................................................. 12 2. Overview ............................................................................. 13 3. Configuration and Operation ....................................................... 15 3.1. Configuration of the Headless Server ................................... 16 3.2. Endpoints of the Headless Server ....................................... 17 3.3. Preview .................................................................... 19 3.3.1. JSON Preview Client ............................................. 19 3.3.2. Custom Preview Client ......................................... 20 3.4. Security ................................................................... 21 3.4.1. Whitelisting of GraphQL Queries ............................... 22 3.4.2. Limiting the Size of a Search Result .......................... 22 3.4.3. Limiting the Depth of a GraphQL Query ....................... 22 3.4.4. Limiting the Complexity of a GraphQL Query ................. 23 3.4.5. Enforcing an Execution Timeout for GraphQL Queries ....... 23 4. Development ....................................................................... 25 4.1. Defining the GraphQL Schema ........................................... 26 4.2. Headless Server Implementation with GraphQL-Java ................. 28 4.2.1. Bootstrapping an Executable Schema ........................ 28 4.2.2. TypeDefinitionRegistry ......................................... 28 4.2.3. RuntimeWiring ................................................. 28 4.2.4. Invoking Queries ............................................... 30 4.3. The @fetch Directive ..................................................... 32 4.4. The @inherit Directive ................................................... 34 4.5. Model Mapper ............................................................ 35 4.6. Filter Predicates ......................................................... 36 4.7. Adapter ................................................................... 37 4.8. Building Links ............................................................ 39 4.8.1. Link Composer for ID links ..................................... 39 4.8.2. Link Composer for hyperlinks ................................. 39 4.8.3. Implementing Custom Link Composer ....................... 40 4.9. Content Schema ......................................................... 41 4.9.1. Simple Article Query ............................................ 41 4.9.2. Article Query with Fragments and Parameters ............... 42 4.9.3. Querying all available Sites .................................... 43 4.9.4. Site Query ....................................................... 43 4.9.5. Querying derived Sites ......................................... 45 4.9.6. Page Query ..................................................... 45 4.9.7. Download Query ................................................ 49 4.9.8. External Link Query ............................................ 49 4.9.9. Querying localized variants ................................... 50 COREMEDIA CONTENT CLOUD iii Headless Server Manual | 4.10. Using Time Dependent Visibility ........................................ 51 4.11. Remote Links ............................................................ 52 5. Rich Text ............................................................................ 55 5.1. Rich Text Output .......................................................... 56 5.1.1. The Include Directive ........................................... 58 5.1.2. YAML Anchors and Aliases ..................................... 58 5.1.3. Code Comments ............................................... 59 5.1.4. Name Property ................................................. 59 5.1.5. Elements Property ............................................. 59 5.1.6. Classes Property ............................................... 60 5.1.7. Contexts and InitialContext Property .......................... 60 5.1.8. HandlerSets Property .......................................... 68 5.1.9. Internal Links ................................................... 68 5.1.10. External Links ................................................. 69 5.2. Using RichTextAdapters for Different Rich Text Grammars ............ 71 5.2.1. Rich Text Adapters .............................................. 71 5.2.2. Developing Custom RichTextAdapters ........................ 72 5.2.3. CoreMedia Grammar RichTextAdapter ........................ 74 6. Search Extension .................................................................. 75 6.1. Generic Search ........................................................... 76 6.2. Dynamic Query Lists ..................................................... 79 6.3. Custom Filter Queries .................................................... 81 7. eCommerce Extension ............................................................. 83 7.1. Headless Commerce Integration Architecture ......................... 84 7.2. Augmentation ............................................................ 86 7.2.1. Categories and Products Mapped to Media Content ......... 86 7.2.2. Augmented Categories and Products ......................... 87 7.2.3. Augmented Pages ............................................. 89 7.3. Product Lists .............................................................. 91 7.4. References to Products and Categories ................................ 92 7.5. eCommerce Setup and Configuration .................................. 94 8. Personalization Extension ......................................................... 95 8.1. Retrieve CMSelectionRules Documents ................................. 96 8.2. Rules ...................................................................... 97 9. Persisted Queries ................................................................. 100 9.1. Loading Persisted Queries at Server Startup ........................... 101 9.1.1. Defining Persisted Queries in Plain GraphQL .................. 101 9.1.2. Defining Persisted Query Maps in Apollo Format ............ 102 9.1.3. Defining Persisted Query Maps in Relay Format ............. 103 9.2. Plugin support for persisted queries ................................... 104 9.3. Query Whitelisting ....................................................... 105 9.4. Apollo Automatic Persisted Queries ................................... 106 10. REST Access to GraphQL ......................................................... 107 10.1. Mapping REST Access to Persisted Queries ........................... 109 10.2. JSLT Transformation ................................................... 110 11. Site Filter ........................................................................... 111 12. Media Endpoint ................................................................... 112 12.1. Media Endpoint URLs ................................................... 114 12.2. Configuration of Media Endpoints ..................................... 116 COREMEDIA CONTENT CLOUD iv Headless Server Manual | 13. Metadata Root .................................................................... 117 13.1. PDE Mapping as Metadata .............................................. 118 14. Frontend Client Development ................................................... 120 14.1. Getting Started .......................................................... 121 14.1.1. Prerequisites ................................................... 121 14.1.2. Setting up a React App ....................................... 121 14.1.3. Setup Apollo for GraphQL ..................................... 122 14.1.4. Developer Tools ............................................... 122 14.2.
Recommended publications
  • C and C++ Preprocessor Directives #Include #Define Macros Inline
    MODULE 10 PREPROCESSOR DIRECTIVES My Training Period: hours Abilities ▪ Able to understand and use #include. ▪ Able to understand and use #define. ▪ Able to understand and use macros and inline functions. ▪ Able to understand and use the conditional compilation – #if, #endif, #ifdef, #else, #ifndef and #undef. ▪ Able to understand and use #error, #pragma, # and ## operators and #line. ▪ Able to display error messages during conditional compilation. ▪ Able to understand and use assertions. 10.1 Introduction - For C/C++ preprocessor, preprocessing occurs before a program is compiled. A complete process involved during the preprocessing, compiling and linking can be read in Module W. - Some possible actions are: ▪ Inclusion of other files in the file being compiled. ▪ Definition of symbolic constants and macros. ▪ Conditional compilation of program code or code segment. ▪ Conditional execution of preprocessor directives. - All preprocessor directives begin with #, and only white space characters may appear before a preprocessor directive on a line. 10.2 The #include Preprocessor Directive - The #include directive causes copy of a specified file to be included in place of the directive. The two forms of the #include directive are: //searches for header files and replaces this directive //with the entire contents of the header file here #include <header_file> - Or #include "header_file" e.g. #include <stdio.h> #include "myheader.h" - If the file name is enclosed in double quotes, the preprocessor searches in the same directory (local) as the source file being compiled for the file to be included, if not found then looks in the subdirectory associated with standard header files as specified using angle bracket. - This method is normally used to include user or programmer-defined header files.
    [Show full text]
  • What Is Link Building and How It Is Useful?
    What is Link Building and How it is Useful? digitalmarketingtrends.in/what-is-link-building-and-how-it-is-useful/ Devoo Banna March 23, 2019 What is Link Building and How it is Useful? (90%) Votes Whether you are new or old brand, the main thing you need to know about the link building concept is how it is useful and what is its goal. Basically is helps in boosting your site’s visibility in online world. The way of SEO and link building services is always updated or followed accordingly with the latest trends and techniques in the market according to the Google algorithm. Link building is important, if you want to compete and thrive in the online world. SEO has becoming the vital part of digital marketing. It would be better explained, if it is given the title of need for the hour. Marketing involves different strategies which have been applied for a long duration. Rankraft, the best digital marketing agency of India acts as a supporter to your business which eventually helps your business grow each day. With the help of digital service, the world is now getting an idea of the different strategies in online marketing. SEO is a major tool to promote and initiate online branding, generating organic traffic, online publicity and many things. Thus, it is the time when the search engine optimization expertise is going to get the most of the importance. Rankraft is one of the best online marketing agency where they shape your business as per the latest digital trends to help you for your site’s link building which ensures your business growth.
    [Show full text]
  • Guide to C Files and H Files by Jacob “Bob” Egner Introduction This
    Guide To C Files And H Files by Jacob “Bob” Egner Introduction This document explains the philosophy of C and H files, and what to put in each file type. At times, I'll stray from the main topic to talk about C compilation in general. The more you understand about C compilation, the less trouble you'll have getting your programs to compile and work. Along with this document, you should also have the files heap.h, heap.c, and heap_test.c. This project can be found in the starter files section of the web site. heap.c and heap.h make up a “module” that implements a memory heap. heap_test.c uses the heap module. I wrote these files to be examples for this document, bring dynamic memory management to the 9S12, and mostly for fun. Please glance over these files before proceeding. The project can be found in the “Starter files” section of the course web site. Why Do We Have H Files? One key thing in understanding C and H files is that declaration and definition are two different things. A declaration tells the compiler that something exists and what kind of beast it is. A definition tells the compiler what it is. A function declaration tells the name of a function, what arguments it takes and what it returns. A function definition also has all that and the code that implements the function. A variable declaration tells the type of a variable. A variable definition tells the type and actually allocates space for the variable.
    [Show full text]
  • Absoft Pro Fortran User Guide
    Pro Fortran Windows™ User Guide For 32-bit and 64-bit Windows Pro Fortran Windows™ User Guide For 32-bit and 64-bit Windows 2111 Cass Lake Road, Suite 102 Troy, MI 48084 U.S.A. Tel (248) 220-1190 Fax (248) 220-1194 [email protected] All rights reserved. No part of this publication may be reproduced or used in any form by any means, without the prior written permission of Absoft Corporation. THE INFORMATION CONTAINED IN THIS PUBLICATION IS BELIEVED TO BE ACCURATE AND RELIABLE. HOWEVER, ABSOFT CORPORATION MAKES NO REPRESENTATION OF WARRANTIES WITH RESPECT TO THE PROGRAM MATERIAL DESCRIBED HEREIN AND SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE. FURTHER, ABSOFT RESERVES THE RIGHT TO REVISE THE PROGRAM MATERIAL AND MAKE CHANGES THEREIN FROM TIME TO TIME WITHOUT OBLIGATION TO NOTIFY THE PURCHASER OF THE REVISION OR CHANGES. IN NO EVENT SHALL ABSOFT BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE PURCHASER'S USE OF THE PROGRAM MATERIAL. U.S. GOVERNMENT RESTRICTED RIGHTS — The software and documentation are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at 252.227-7013. The contractor is Absoft Corporation, 2111 Cass Lake Rd, Suite 102, Keego Harbr, Michigan 48320. ABSOFT CORPORATION AND ITS LICENSOR(S) MAKE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE SOFTWARE.
    [Show full text]
  • Ways Marketing Automation Can Hurt SEO...That No One's Talking About
    6 ways Marketing Automation Can Hurt SEO... ...That No One’s Talking About 6 Ways Marketing Automation Can Hurt SEO (That No One’s Talking About) WHAT IS MARKETING AUTOMATION? Marketing automation is a software designed to help businesses know their customer, then personalize, contextualize, communicate and optimize their content for that customer. Marketing automation tools allow businesses to create an entire website or microsite specifically geared toward capturing leads, organizing their contact data, and then regularly nurturing them with personalized emails and dynamic landing pages that speak directly to each contact’s unique details. WHO USES MARKETING AUTOMATION? More and more businesses, whether they have 5 employees or 5,000, turn to marketing to marketing automation (MA) as a way to grow their businesses. It can help them organize their sales contacts, deliver targeted content and service to those contacts and measure the results - all from one simple user interface. In fact, the adoption rate for marketing automation has grown rapidly over the past couple years, with 2015 statistics showing 59% of B2B Fortune 500 companies, and 68% of top-performing small businesses use marketing automation. verticalmeasures.com 6 Ways Marketing Automation Can Hurt SEO (That No One’s Talking About) SEO potential. And that’s not what you want to SO, WHAT’S THE PROBLEM? hear when making a big investment into a new platform. Marketers, salespeople and SEOs love the optimization, relationship building and On the other hand, when you implement a ROI attribution that marketing automation marketing automation tool properly, there delivers. It can also pose inherent challenges to are lots of SEO benefits largely having to traditional website optimization in ways many do with the kind of unparalleled data that companies may not have considered - because marketing automation can provide, namely: frankly, no one’s talking about them… until now.
    [Show full text]
  • Javaserver Pages™ (JSP™) V1.2 Syntax Reference
    JavaServer Pages™ (JSP™) v1.2 Syntax Reference <jsp:root> Defines standard elements and namespace attributes of tag libraries. Hidden Comment Documents the JSP page but is not inserted into the response. Declaration Declares a variable or method valid in the scripting language used in the page. Expression Contains an expression valid in the scripting language used in the page. Scriptlet Contains a code fragment valid in the scripting language used in the page. <jsp:text> Encloses template data. Include Directive Includes a resource of text or code when the JSP page is translated. Page Directive Defines attributes that apply to an entire JSP page. Taglib Directive Defines a tag library and prefix for the custom tags used in the JSP page. <jsp:forward> Forwards a request to an HTML file, JSP page, or servlet. <jsp:getProperty> Inserts the value of a bean property into the response. <jsp:include> Includes a static resource or the result from another web component <jsp:plugin> Causes the execution of an applet or bean. The applet or bean executes in the specified plugin. If the plugin is not available, the client displays a dialog to initiate the download of the plugin software. <jsp:setProperty> Sets a bean property value or values. <jsp:useBean> Instantiates or references a bean with a specific name and scope. 1 Preface All tags are case sensitive. A pair of single quotes is equivalent to a pair of double quotes. Spaces are not allowed between an equals sign and an attribute value. The elements in a JSP page can be expressed in JSP syntax or XML syntax.
    [Show full text]
  • A Web Based System Design for Creating Content in Adaptive
    Malaysian Online Journal of Educational Technology 2020 (Volume 8 - Issue 3 ) A Web Based System Design for Creating [1] [email protected], Gazi University, Faculty of Gazi Content in Adaptive Educational Education, Ankara Hypermedia and Its Usability [2] [email protected], Gazi University, Faculty of Gazi Education, Ankara Yıldız Özaydın Aydoğdu [1], Nursel Yalçın [2] http://dx.doi.org/10.17220/mojet.2020.03.001 ABSTRACT Adaptive educational hypermedia is an environment that offers an individualized learning environment according to the characteristics, knowledge and purpose of the students. In general, adaptive educational hypermedia, a user model is created based on user characteristics and adaptations are made in terms of text, content or presentation according to the created user model. Different contents according to the user model are shown as much as user model creation in adaptive educational hypermedia. The development of applications that allow the creation of adaptive content according to the features specified in the user model has great importance in ensuring the use of adaptive educational hypermedia in different contexts. The purpose of this research is to develop a web- based application for creating content in adaptive educational hypermedia and to examine the usability of the developed application. In order to examine the usability of the application developed in the scope of the study, a field expert opinion form was developed and opinions were asked about the usability of the application from 7 different field experts. As the result of the opinions, it has been seen that the application developed has a high usability level. In addition, based on domain expert recommendations, system revisions were made and the system was published at www.adaptivecontentdevelopment.com.
    [Show full text]
  • Section “Common Predefined Macros” in the C Preprocessor
    The C Preprocessor For gcc version 12.0.0 (pre-release) (GCC) Richard M. Stallman, Zachary Weinberg Copyright c 1987-2021 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation. A copy of the license is included in the section entitled \GNU Free Documentation License". This manual contains no Invariant Sections. The Front-Cover Texts are (a) (see below), and the Back-Cover Texts are (b) (see below). (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Table of Contents 1 Overview :::::::::::::::::::::::::::::::::::::::: 1 1.1 Character sets:::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.2 Initial processing ::::::::::::::::::::::::::::::::::::::::::::::: 2 1.3 Tokenization ::::::::::::::::::::::::::::::::::::::::::::::::::: 4 1.4 The preprocessing language :::::::::::::::::::::::::::::::::::: 6 2 Header Files::::::::::::::::::::::::::::::::::::: 7 2.1 Include Syntax ::::::::::::::::::::::::::::::::::::::::::::::::: 7 2.2 Include Operation :::::::::::::::::::::::::::::::::::::::::::::: 8 2.3 Search Path :::::::::::::::::::::::::::::::::::::::::::::::::::: 9 2.4 Once-Only Headers::::::::::::::::::::::::::::::::::::::::::::: 9 2.5 Alternatives to Wrapper #ifndef ::::::::::::::::::::::::::::::
    [Show full text]
  • The Portland Group
    ® PGI Compiler User's Guide Parallel Fortran, C and C++ for Scientists and Engineers Release 2011 The Portland Group While every precaution has been taken in the preparation of this document, The Portland Group® (PGI®), a wholly-owned subsidiary of STMicroelectronics, Inc., makes no warranty for the use of its products and assumes no responsibility for any errors that may appear, or for damages resulting from the use of the information contained herein. The Portland Group retains the right to make changes to this information at any time, without notice. The software described in this document is distributed under license from STMicroelectronics and/or The Portland Group and may be used or copied only in accordance with the terms of the end-user license agreement ("EULA"). PGI Workstation, PGI Server, PGI Accelerator, PGF95, PGF90, PGFORTRAN, and PGI Unified Binary are trademarks; and PGI, PGHPF, PGF77, PGCC, PGC++, PGI Visual Fortran, PVF, PGI CDK, Cluster Development Kit, PGPROF, PGDBG, and The Portland Group are registered trademarks of The Portland Group Incorporated. Other brands and names are property of their respective owners. No part of this document may be reproduced or transmitted in any form or by any means, for any purpose other than the purchaser's or the end user's personal use without the express written permission of STMicroelectronics and/or The Portland Group. PGI® Compiler User’s Guide Copyright © 2010-2011 STMicroelectronics, Inc. All rights reserved. Printed in the United States of America First Printing: Release 2011, 11.0, December, 2010 Second Printing: Release 2011, 11.1, January, 2011 Third Printing: Release 2011, 11.2, February, 2011 Fourth Printing: Release 2011, 11.3, March, 2011 Fourth Printing: Release 2011, 11.4, April, 2011 Technical support: [email protected] Sales: [email protected] Web: www.pgroup.com ID: 1196151 Contents Preface .....................................................................................................................................
    [Show full text]
  • R Markdown Cheat Sheet I
    1. Workflow R Markdown is a format for writing reproducible, dynamic reports with R. Use it to embed R code and results into slideshows, pdfs, html documents, Word files and more. To make a report: R Markdown Cheat Sheet i. Open - Open a file that ii. Write - Write content with the iii. Embed - Embed R code that iv. Render - Replace R code with its output and transform learn more at rmarkdown.rstudio.com uses the .Rmd extension. easy to use R Markdown syntax creates output to include in the report the report into a slideshow, pdf, html or ms Word file. rmarkdown 0.2.50 Updated: 8/14 A report. A report. A report. A report. A plot: A plot: A plot: A plot: Microsoft .Rmd Word ```{r} ```{r} ```{r} = = hist(co2) hist(co2) hist(co2) ``` ``` Reveal.js ``` ioslides, Beamer 2. Open File Start by saving a text file with the extension .Rmd, or open 3. Markdown Next, write your report in plain text. Use markdown syntax to an RStudio Rmd template describe how to format text in the final report. syntax becomes • In the menu bar, click Plain text File ▶ New File ▶ R Markdown… End a line with two spaces to start a new paragraph. *italics* and _italics_ • A window will open. Select the class of output **bold** and __bold__ you would like to make with your .Rmd file superscript^2^ ~~strikethrough~~ • Select the specific type of output to make [link](www.rstudio.com) with the radio buttons (you can change this later) # Header 1 • Click OK ## Header 2 ### Header 3 #### Header 4 ##### Header 5 ###### Header 6 4.
    [Show full text]
  • The Algorithmization of the Hyperlink.” Computational Culture 3 (2013)
    Citation: Helmond, A. “The Algorithmization of the Hyperlink.” Computational Culture 3 (2013). http://computationalculture.net/article/the-algorithmization-of-the-hyperlink The Algorithmization of the Hyperlink Anne Helmond, University of Amsterdam Abstract This study looks at the history of the hyperlink from a medium-specific perspective by analyzing the technical reconfiguration of the hyperlink by engines and platforms over time. Hyperlinks may be seen as having different roles belonging to specific periods, including the role of the hyperlink as a unit of navigation, a relationship marker, a reputation indicator and a currency of the web. The question here is how web devices have contributed to constituting these roles and how social media platforms have advanced the hyperlink from a navigational device into a data- rich analytical device. By following how hyperlinks have been handled by search engines and social media platforms, and in their turn have adapted to this treatment, this study traces the emergence of new link types and related linking practices. The focus is on the relations between hyperlinks, users, engines and platforms as mediated through software and in particular the process of the algorithmization of the hyperlink through short URLs by social media platforms. The important role these platforms play in the automation of hyperlinks through platform features and in the reconfiguration of the link as database call is illustrated in a case study on link sharing on Twitter. 1 Introduction The hyperlink as a key natively digital object (Rogers 2013, 13) is considered to be the fabric of the web and in this role has the capacity to create relations, constitute networks and organize and rank content.
    [Show full text]
  • Literature Survey and Open Challenges
    Link maintenance for integrity in linked open data evolution: literature survey and open challenges Andre Gomes Regino a, Julio Cesar dos Reis a,d, Rodrigo Bonacin b, Ahsan Morshed c and Timos Sellis e a Institute of Computing, University of Campinas, SP, Brazil E-mails: [email protected], [email protected] b , UNIFACCAMP and Center for Information Technology Renato Archer, SP, Brazil E-mail: [email protected] c , Central Queensland University of Technology,Melbourne, Australia E-mail: [email protected] d Nucleus of Informatics Applied to Education, University of Campinas, SP, Brazil E-mail: [email protected] e , Swinburne University of Technology,Melbourne, Australia E-mail: [email protected] Editor: Oscar Corcho, Universidad Politécnica de Madrid, Spain Solicited reviews: Mikel Emaldi Manrique, Universidad de Deusto, Spain; Two anonymous reviewers Open review: Mohamed Ahmed Sherif, University of Leipzig, Germany Abstract. RDF data has been extensively deployed describing various types of resources in a structured way. Links between data elements described by RDF models stand for the core of Semantic Web. The rising amount of structured data published in public RDF repositories, also known as Linked Open Data, elucidates the success of the global and unified dataset proposed by the vision of the Semantic Web. Nowadays, semi-automatic algorithms build connections among these datasets by exploring a variety of methods. Interconnected open data demands automatic methods and tools to maintain their consistency over time. The update of linked data is considered as key process due to the evolutionary characteristic of such structured datasets. However, data changing operations might influence well-formed links, which turns difficult to maintain the consistencies of connections over time.
    [Show full text]