• Aucun résultat trouvé

Towards a Linked Open Code

N/A
N/A
Protected

Academic year: 2021

Partager "Towards a Linked Open Code"

Copied!
9
0
0

Texte intégral

Loading

Figure

Fig. 1. Challenges to achieve a first working prototype of Linked Open Code
Fig. 2. Comparison of metadata provided function signature in Python and C++
Fig. 3. Overview of the process for semantic annotation of functions

Références

Documents relatifs

A data integration subsystem will provide other subsystems or external agents with uniform access interface to all of the system’s data sources. Requested information

The prototype currently offers two entry points: Users can either initiate a keyword search over a given SPARQL endpoint, or they can select any of the al- ready available

Native support to data analysis. Better data accessibility inherent to LOD presents itself as both an opportunity and a challenge. With better access, an LOD data consumer is exposed

for single FOAF documents at websites, or blogging software that publishes RDF(a), but does not provide a SPARQL endpoint), it is beyond the scope of this paper (if not

However, the majority of SPARQL implemen- tations require the data to be available in advance, i.e., to exist in main memory or in a RDF repository (accessible through a SPARQL

In this paper, we present a system which makes scientific data available following the linked open data principle using standards like RDF und URI as well as the popular

This analysis shown in Figure 6 shows that participants found data source and triple pattern(s) related information helpful for understanding the query result derivation, but have

This paper has shown how LODeX is able to provide a visual and navigable summary of a LOD dataset including its inferred schema starting from the URL of a SPARQL Endpoint3. The