DOCSLIB.ORG

N3 Rules Processing and HTML Translation for the Semantic Web

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
N3 Rules Processing and HTML Translation for the Semantic Web View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by CiteSeerX N3 Rules Processing and HTML Translation for the Semantic web Chun Yip Leung Digital Media Systems Laboratory HP Laboratories Bristol HPL-2003-199 October 2nd , 2003* E-mail: chun.leung@doc.ic.ac.uk N3, The semantic web is an emerging technology that could totally change forward chained how web works. It is based on the Resource Description Framework rules, RDF (RDF) which defines graphs to represent links between data. RDF/XML translation, is the common format to store RDF graphs while N3 is another instant to semantic web represent RDF and provides powerful function like rules representation. * Internal Accession Date Only Approved for External Publication ã Copyright Hewlett-Packard Company 2003 N3 Rules Processing and HTML Translation for the Semantic web Author: Chun Yip Leung (chun.leung@doc.ic.ac.uk) Keyword: N3; Forward Chained Rules; RDF Translation; Semantic Web Abstract The semantic web is an emerging technology that could totally change how web works. It is based on the Resource Description Framework (RDF) [0] which defines graphs to represent link s between data. RDF/XML is the common format to store RDF graphs while N3 is another instant to represent RDF and provides powerful function like rules representation. In this report we will discuss how to connect N3 rules to the Jena2’s rule processing system and also use the new system to solve the visual representation problem on browsing RDF. Acknowledgements This report and the project I have been working on within my six-month placement in Hewlett-Packard Labs Bristol gave my invaluable experience and I would like to say thank you to the Jena development team, especially Andy Seaborne, Chris Dollin and Dave Reynolds who gave me many advice throughout. 1 Introduction In the current web, machines cannot understand the meaning of the links. [1] Figure 1 - The current web Web browsers use HTTP protocol to access data served by different servers. Documents and resources are linked by hyperlinks and Hypertext is transmitted to present data over 1 web browsers. When the World Wide Web was designed, the assumption was a person will read the page, not machines. This makes it very hard for information management and processing, especially across different documents. The Semantic Web makes a simple extension to the current web by using binary relationships to capture the meaning between link s and data. [2] That makes it possible to represent machine processable information and lead to automation, integration and reuse of data across various applications. [3] The computer industry has agreed and uses XML standards to give a syntactic structure for describing data. However, XML can be used in many different ways to describe the same data, this makes it too open and arbitrary to support the type of widespread and ad hoc data integration envisaged for the Semantic Web. [4] Therefore a standard syntax - Resource Description Framework (RDF) was introduced. RDF defines a graph model to provide a consistent, standardised way of describing and querying internet resources, from text pages and graphics to audio files and video clips. It gives semantic interoperability, and provides the base layer for building a Semantic Web. [4] 2 Problem “The Semantic Web is a vision: the idea of having data on the Web defined and linked in such a way that it can be used by machines not just for display purposes."[6] 2.1 Display information represented by RDF in web browsers In the semantic web, RDF is the base for defining meaning, or relationships, between data. The most common way to store RDF data is to use RDF/ XML; however XML syntax is not very good at the visual presentation of information to human beings; when we see XML files written according to the RDF specifications, we know how to interpret them. But that does not mean we could see the meaning straight away. <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf -syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:foaf="http://xmlns.com/foaf/0.1/"> <foaf:Person rdf:about="http://www.chunleung.org/"> <foaf:name>Johnny Leung</foaf:name> <foaf:workplaceHomepage rdf:resource="http://www.hp.com/"/> <foaf:schoolHomepage rdf:resource="http://www.doc.ic.ac.uk/"/> </rdf:RDF> RDF/XML may be much harder to read than this: Johnny Leung workplaceHomepage : http://www.hp.com/ schoolHomepage: http://www.doc.ic.ac.uk/ Therefore, a better means of visual presentation would be necessary towards the success of semantic web. The most common way to make visual presentation over the Internet is 2 the hypertext. It would be a good idea if it is able to use HTML on displaying the information modelled by RDF, in particul ar RDF/XML, on web browsers. One of the examples is us ing web server to serve FOAF (Friend of a Friend) data stored in RDF over the internet. And throughout this report, I will illustrate how this actually could be done. Moreover, we normally do not want to display all the information stored within the RDF but only part of the information. For example, we have a collection of FOAF RDF about placement students working in Hewlett-Packard Labs but we only want to display FOAF data on a particular person, say about “Johnny”. And within Johnny’s data, we might only want a certain bit being displayed. The principle is same as report generation in general I.T. industry but our data source is any data modelled in RDF. This could be done in XSLT up to a point if data is stored in XML format, but the XML’s tree structure and centric design make it not so effective. This happened because for the same graph, we could have different RDF/XML representation, as RDF focused on representing semantic, that means there are inf inity ways to store the same semantic within the RDF/XML documents, that means we have to obtain the data within the semantic level. The good thing about RDF is that there is a graph represented by it. The logical meaning, or semantic will not be affected on the representation method and therefore the translation should not be effected if the RDF data is provided in RDF/XML, N3, N- triples or in different type of Jena model. 2.2 Customizable system When the data was presented over web browsers, it would also be great if the layout is not limited but any customizable layout. The primary aim is different types of template could be easily created and the system could generate the HTML output according to the template so we could have whatever needed. The further aim would be minimize the learning curve on how the configuration could be done. The system developer might need to understand the semantic web technology deeply and programming on declarative rules are required on serving different RDF data based on different schema, but the learning curve of the system administrator should be much shorter in order to configure the system. The HTML template is based in normal HTML but with embedded tags, known as taglibs, and normal web developer or website administrator sho uld be able pick up the technique on template writing in a very short time and create web pages to present RDF data. 3 3 Background 3.1 Semantic Web Technologies Semantic Web technologies are based on a global naming scheme (URIs), a standard syntax for describing data (RDF), standard means of describing the properties of that data (rdf-schema) and standard means of describing relationships between data items (ontologies). [5] Figure 2 - The Layer Cake The principles are: · Everything Identifiable is on SW by URI (Universal Resource Identifiers). · Some properties allow unambiguous identification · Allow effective combination of the independent work of diverse communities. · Support the ability to add new information without insisting that the old be modified. · Provide communities the ability to resolve ambiguities and clarify inconsistencies. · Use descriptive conventions that can expand as human understanding expands. 3.1.1 RDF/XML RDF provides a consistent, standardized way of describing and querying internet resources and it provides the base layer for building a Semantic Web. For instance, telnet(janet_bruten, 3128700) represents the fact that the person object Janet Bruten has the telnet number 312-8700. For example, if we have the following graphs representing relationships: [4] Figure 3 - A simple directed graph This means: 4 http://www.hp.com/JanetBruten has telnet whose value is 31287002 and http://www.hp.com/JanetBruten has employee_number whose value is 405549 The standard way to record these relationships is via RDF/XML: <?xml version=’1.0’?> <rdf:RDF xmlns:rdf = ‘http://www.w3.org/1999/02/22 -rdf-syntax-ns#’ xmlns:person = ” http://www.hpl.hp.com/semweb/person” > <rdf:Description rdf:about=‘http://www.hp.com/JanetBruten’> <person:telnet>31287002</person:telnet> <person:employee_number>405549</person:employee_number> </rdf:Description> </rdf:RDF> 3.1.2 Notation 3 - N3 [7] N3 is based on RDF standards and equivalent to RDF/XML syntax , but have extra features like rules and formula. N3 is not designed as an alternative to RDF's XML syntax but a language designed for a human-readable and scribblable language. [10] It is easier and simpler than the RDF/XML approach. In N3, information is also a collection of statements; each with a subject, verb and object - and nothing else. <subject> <verb> <object> . In a statement, everything is identified by URI. And every statement is ended with a period. For example: <#johnny> <#knows> <#mei>.
Load more

Recommended publications
  • Semantics Developer's Guide
    MarkLogic Server Semantic Graph Developer’s Guide 2 MarkLogic 10 May, 2019 Last Revised: 10.0-8, October, 2021 Copyright © 2021 MarkLogic Corporation. All rights reserved. MarkLogic Server MarkLogic 10—May, 2019 Semantic Graph Developer’s Guide—Page 2 MarkLogic Server Table of Contents Table of Contents Semantic Graph Developer’s Guide 1.0 Introduction to Semantic Graphs in MarkLogic ..........................................11 1.1 Terminology ..........................................................................................................12 1.2 Linked Open Data .................................................................................................13 1.3 RDF Implementation in MarkLogic .....................................................................14 1.3.1 Using RDF in MarkLogic .........................................................................15 1.3.1.1 Storing RDF Triples in MarkLogic ...........................................17 1.3.1.2 Querying Triples .......................................................................18 1.3.2 RDF Data Model .......................................................................................20 1.3.3 Blank Node Identifiers ..............................................................................21 1.3.4 RDF Datatypes ..........................................................................................21 1.3.5 IRIs and Prefixes .......................................................................................22 1.3.5.1 IRIs ............................................................................................22
    [Show full text]
  • Binary RDF for Scalable Publishing, Exchanging and Consumption in the Web of Data
    WWW 2012 – PhD Symposium April 16–20, 2012, Lyon, France Binary RDF for Scalable Publishing, Exchanging and Consumption in the Web of Data Javier D. Fernández 1;2 Supervised by: Miguel A. Martínez Prieto 1 and Claudio Gutierrez 2 1 Department of Computer Science, University of Valladolid (Spain) 2 Department of Computer Science, University of Chile (Chile) jfergar@infor.uva.es ABSTRACT era and hence they share a document-centric view, providing The Web of Data is increasingly producing large RDF data- human-focused syntaxes, disregarding large data. sets from diverse fields of knowledge, pushing the Web to In a typical scenario within the current state-of-the-art, a data-to-data cloud. However, traditional RDF represen- efficient interchange of RDF data is limited, at most, to com- tations were inspired by a document-centric view, which pressing the verbose plain data with universal compression results in verbose/redundant data, costly to exchange and algorithms. The resultant file has no logical structure and post-process. This article discusses an ongoing doctoral the- there is no agreed way to efficiently publish such data, i.e., sis addressing efficient formats for publication, exchange and to make them (publicly) available for diverse purposes and consumption of RDF on a large scale. First, a binary serial- users. In addition, the data are hardly usable at the time of ization format for RDF, called HDT, is proposed. Then, we consumption; the consumer has to decompress the file and, focus on compressed rich-functional structures which take then, to use an appropriate external tool (e.g.
    [Show full text]
  • RDF Query Languages Need Support for Graph Properties
    RDF Query Languages Need Support for Graph Properties Renzo Angles1, Claudio Gutierrez1, and Jonathan Hayes1,2 1 Dept. of Computer Science, Universidad de Chile 2 Dept. of Computer Science, Technische Universit¨at Darmstadt, Germany {rangles,cgutierr,jhayes}@dcc.uchile.cl Abstract. This short paper discusses the need to include into RDF query languages the ability to directly query graph properties from RDF data. We study the support that current RDF query languages give to these features, to conclude that they are currently not supported. We propose a set of basic graph properties that should be added to RDF query languages and provide evidence for this view. 1 Introduction One of the main features of the Resource Description Framework (RDF) is its ability to interconnect information resources, resulting in a graph-like structure for which connectivity is a central notion [GLMB98]. As we will argue, basic concepts of graph theory such as degree, path, and diameter play an important role for applications that involve RDF querying. Considering the fact that the data model influences the set of operations that should be provided by a query language [HBEV04], it follows the need for graph operations support in RDF query languages. For example, the query “all relatives of degree 1 of Alice”, submitted to a genealogy database, amounts to retrieving the nodes adjacent to a resource. The query “are suspects A and B related?”, submitted to a police database, asks for any path connecting these resources in the (RDF) graph that is stored in this database. The query “what is the Erd˝osnumber of Alberto Mendelzon”, submitted to (a RDF version of) DBLP, asks simply for the length of the shortest path between the nodes representing Erd˝osand Mendelzon.
    [Show full text]
  • Exercise Sheet 1
    Semantic Web, SS 2017 1 Exercise Sheet 1 RDF, RDFS and Linked Data Submit your solutions until Friday, 12.5.2017, 23h00 by uploading them to ILIAS. Later submissions won't be considered. Every solution should contain the name(s), email adress(es) and registration number(s) of its (co-)editor(s). Read the slides for more submission guidelines. 1 Knowledge Representation (4pts) 1.1 Knowledge Representation Humans usually express their knowledge in natural language. Why aren't we using, e.g., English for knowledge representation and the semantic web? 1.2 Terminological vs Concrete Knowledge What is the role of terminological knowledge (e.g. Every company is an organization.), and what is the role of facts (e.g. Microsoft is an organization. Microsoft is headquartered in Redmond.) in a semantic web system? Hint: Imagine an RDF ontology that contains either only facts (describing factual knowledge: states of aairs) or constraints (describing terminological knowledge: relations between con- cepts). What could a semantic web system do with it? Semantic Web, SS 2017 2 2 RDF (10pts) RDF graphs consist of triples having a subject, a predicate and an object. Dierent syntactic notations can be used in order to serialize RDF graphs. By now you have seen the XML and the Turtle syntax of RDF. In this task we will use the Notation3 (N3) format described at http://www.w3.org/2000/10/swap/Primer. Look at the following N3 le: @prefix model: <http://example.com/model1/> . @prefix cdk: <http://example.com/chemistrydevelopmentkit/> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
    [Show full text]
  • Common Sense Reasoning with the Semantic Web
    Common Sense Reasoning with the Semantic Web Christopher C. Johnson and Push Singh MIT Summer Research Program Massachusetts Institute of Technology, Cambridge, MA 02139 CJohnson26@mail.utexas.edu, push@media.MIT.edu http://groups.csail.mit.edu/dig/2005/08/Johnson-CommonSense.pdf Abstract Current HTML content on the World Wide Web has no real meaning to the computers that display the content. Rather, the content is just fodder for the human eye. This is unfortunate as in fact Web documents describe real objects and concepts, and give particular relationships between them. The goal of the World Wide Web Consortium’s (W3C) Semantic Web initiative is to formalize web content into Resource Description Framework (RDF) ontologies so that computers may reason and make decisions about content across the Web. Current W3C work has so far been concerned with creating languages in which to express formal Web ontologies and tools, but has overlooked the value and importance of implementing common sense reasoning within the Semantic Web. As Web blogging and news postings become more prominent across the Web, there will be a vast source of natural language text not represented as RDF metadata. Common sense reasoning will be needed to take full advantage of this content. In this paper we will first describe our work in converting the common sense knowledge base, ConceptNet, to RDF format and running N3 rules through the forward chaining reasoner, CWM, to further produce new concepts in ConceptNet. We will then describe an example in using ConceptNet to recommend gift ideas by analyzing the contents of a weblog.
    [Show full text]
  • Use Style: Paper Title
    IJRECE VOL. 6 ISSUE 2 APR.-JUNE 2018 ISSN: 2393-9028 (PRINT) | ISSN: 2348-2281 (ONLINE) A Review on Reasoning System, Types and Tools and Need for Hybrid Reasoning Goutami M.K1, Mrs. Rashmi S R2, Bharath V3 1M.Tech, Computer Network Engineering, Dept. of Computer Science and Engineering, Dayananda Sagar college of Engineering, Bangalore. (Email: goutamimk@gmail.com) 2Asst. Professor, Dept. of Computer Science and Engineering, Dayananda Sagar college of Engineering , Bangalore. (Email: rashmimugdha@gmail.com) 3Dept. of Computer Science and Engineering, Dayananda Sagar college of Engineering, Bangalore Abstract— Expert system is a programming system which knowledge base then we require a programming system that utilizes the information of expert knowledge of the specific will facilitate us to access the knowledge for reasoning purpose domain to make decisions. These frameworks are intended to and helps in decision making and problem solving. Inference tackle complex issues by thinking through the learning process engine is an element of the system that applies logical rules to called as reasoning. The knowledge used for reasoning is the knowledge base to deduce new information. User interface represented mainly as if-then rules. Expert system forms a is one through which the user can communicate with the expert significant part in day-to-day life nowadays as it emulates the system. expert’s behavior in analyzing the information and concludes “A reasoning system is a software system that uses available knowledge, applies logical techniques to generate decision. This paper primarily centers on the reasoning system conclusions”. It uses logical techniques such as deduction which plays the fundamental part in field of artificial approach and induction approach.
    [Show full text]
  • Resource Description Framework Technologies in Chemistry Egon L Willighagen1* and Martin P Brändle2
    Willighagen and Brändle Journal of Cheminformatics 2011, 3:15 http://www.jcheminf.com/content/3/1/15 EDITORIAL Open Access Resource description framework technologies in chemistry Egon L Willighagen1* and Martin P Brändle2 Editorial would like to thank Pfizer, Inc., who had partially The Resource Description Framework (RDF) is provid- funded the article processing charges for this Thematic ing the life sciences with new standards around data Series. Pfizer, Inc. has had no input into the content of and knowledge management. The uptake in the life the publication or the articles themselves. All articles in sciences is significantly higher than the uptake of the the series were independently prepared by the authors eXtensible Markup Language (XML) and even relational and were subjected to the journal’s standard peer review databases, as was recently shown by Splendiani et al. [1] process. Chemistry is adopting these methods too. For example, In the remainder of this editorial, we will briefly out- Murray-Rust and co-workers used RDF already in 2004 line the various RDF technologies and how they have to distribute news items where chemical structures were been used in chemistry so far. embedded using RDF Site Summary 1.0 [2]. Frey imple- mented a system which would now be referred to as an 1 Concepts electronic lab notebook (ELN) [3]. The use of the The core RDF specification was introduced by the SPARQL query language goes back to 2007 where it World Wide Web Consortium (W3C) in 1999 [6] and was used in a system to annotate crystal structures [4]. defines the foundation of the RDF technologies.
    [Show full text]
  • Connecting RDA and RDF Linked Data for a Wide World of Connected Possibilities
    Practice Connecting RDA and RDF Linked Data for a Wide World of Connected Possibilities Ashleigh Faith & Michelle Chrzanowski Ashleigh N. Faith, MLIS is an Adjunct Instructor at the University of Pittsburgh Information School, anp114@pitt.edu Michelle Chrzanowski, MLS is a Reference Librarian at the Tidewater Community College Norfolk Campus Library, mchrzanowski@tcc.edu Libraries have struggled with connecting a plethora of content and the metadata stored in catalogs to patrons. Adding more value to catalogs, more tools for reference librarians, and enriched patron search, linked data is a means to connect more people with more relevant information. With the recent transition to the Resource Description and Access (RDA) cataloging standard within libraries, linking data in library databases has become a much easier project to tackle, largely because of another standard called Resource Description Framework (RDF). Both focus on resource description and both are components of linked data within the library. Tying them together is the Functional Requirements for Bibliographic Records (FRBR) conceptual framework. Acknowledging that linked data components are most likely new to many librarians, this article seeks to explain what linked data is, how RDA and RDF are connected by FRBR, and how knowledge maps may improve information access. Introduction Interest in linked data has been growing. Recently, a search of the abstract databases Scopus, Web of Science, and Google Scholar show “linked data” as a search term an average of 45,633 times from 2010 to July 2015. From January to July 2015 alone, "linked data" was searched an average of 3,573 times. It is therefore no wonder that more people are paying attention to data and how it can be linked to other data.
    [Show full text]
  • The Resource Description Framework and Its Schema Fabien Gandon, Reto Krummenacher, Sung-Kook Han, Ioan Toma
    The Resource Description Framework and its Schema Fabien Gandon, Reto Krummenacher, Sung-Kook Han, Ioan Toma To cite this version: Fabien Gandon, Reto Krummenacher, Sung-Kook Han, Ioan Toma. The Resource Description Frame- work and its Schema. Handbook of Semantic Web Technologies, 2011, 978-3-540-92912-3. hal- 01171045 HAL Id: hal-01171045 https://hal.inria.fr/hal-01171045 Submitted on 2 Jul 2015 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. The Resource Description Framework and its Schema Fabien L. Gandon, INRIA Sophia Antipolis Reto Krummenacher, STI Innsbruck Sung-Kook Han, STI Innsbruck Ioan Toma, STI Innsbruck 1. Abstract RDF is a framework to publish statements on the web about anything. It allows anyone to describe resources, in particular Web resources, such as the author, creation date, subject, and copyright of an image. Any information portal or data-based web site can be interested in using the graph model of RDF to open its silos of data about persons, documents, events, products, services, places etc. RDF reuses the web approach to identify resources (URI) and to allow one to explicitly represent any relationship between two resources.
    [Show full text]
  • RDF Translator: a Restful Multi-Format Data Converter for the Semantic Web
    RDF Translator: A RESTful Multi-Format Data Converter for the Semantic Web Technical Report TR-2013-1 Version: July 25, 2013 Alex Stolz, alex.stolz@unibw.de Bene Rodriguez-Castro, bene.rodriguez@unibw.de MartinarXiv:1312.4704v1 [cs.DL] 17 Dec 2013 Hepp, martin.hepp@unibw.de E-Business and Web Science Research Group, Universit¨atder Bundeswehr M¨unchen Werner-Heisenberg-Weg 39, D-85579 Neubiberg, Germany RDF Translator: A RESTful Multi-Format Data Converter for the Semantic Web Alex Stolz, Bene Rodriguez-Castro, and Martin Hepp E-Business and Web Science Research Group, Universit¨atder Bundeswehr M¨unchen Werner-Heisenberg-Weg 39, D-85579 Neubiberg, Germany falex.stolz,bene.rodriguez,martin.heppg@unibw.de Abstract. The interdisciplinary nature of the Semantic Web and the many projects put forward by the community led to a large number of widely accepted serialization formats for RDF. Most of these RDF syn- taxes have been developed out of a necessity to serve specific purposes better than existing ones, e.g. RDFa was proposed as an extension to HTML for embedding non-intrusive RDF statements in human-readable documents. Nonetheless, the RDF serialization formats are generally transducible among themselves given that they are commonly based on the RDF model. In this paper, we present (1) a RESTful Web service based on the HTTP protocol that translates between different serializa- tions. In addition to its core functionality, our proposed solution provides (2) features to accommodate frequent needs of Semantic Web developers, namely a straightforward user interface with copy-to-clipboard function- ality, syntax highlighting, persistent URI links for easy sharing, cool URI patterns, and content negotiation using respective HTTP headers.
    [Show full text]
  • The Crosscloud Project and Decentralized Web Applications
    The Crosscloud Project and Decentralized Web Applications by Martin Martinez Rivera Submitted to the Department of Electrical Engineering and Computer Science in partial fulfillment of the requirements for the degree of Master of Engineering in Electrical Engineering and Computer Science at the MASSACHUSETTS INSTITUTE OF TECHNOLOGY September 2015 ○c 2015 Martin Martinez Rivera. The author hereby grants to MIT permission to reproduce and to distribute publicly paper and electronic copies of this thesis document in whole and in part in any medium now known or hereafter created. Author................................................................ Department of Electrical Engineering and Computer Science August 18, 2015 Certified by. Tim Berners-Lee Professor Thesis Supervisor Accepted by . Christopher J. Terman Chairman, Masters of Engineering Thesis Committee 2 The Crosscloud Project and Decentralized Web Applications by Martin Martinez Rivera Submitted to the Department of Electrical Engineering and Computer Science on August 18, 2015, in partial fulfillment of the requirements for the degree of Master of Engineering in Electrical Engineering and Computer Science Abstract Crosscloud is a project spearheaded by the Decentralized Information Group, aiming to create a platform that enables developers to build decentralized Web applications in which users have total control over their data. This thesis presents the results of my work: gojsonld, a library for the JSON-LD linked data format written in the Go programming language, and ldnode, a server developed on the Node.js framework which acts as a back-end for Web applications. gojsonld allows Crosscloud applications written in Go to use the JSON-LD format, which is based on the popular JSON format and is widely used in the design of Web application APIs.
    [Show full text]
  • Rdflib Documentation
    rdflib Documentation Release 5.0.0-dev RDFLib Team Nov 01, 2018 Contents 1 Getting started 3 2 In depth 19 3 Reference 33 4 For developers 157 5 Indices and tables 171 Python Module Index 173 i ii rdflib Documentation, Release 5.0.0-dev RDFLib is a pure Python package work working with RDF. RDFLib contains most things you need to work with RDF, including: • parsers and serializers for RDF/XML, N3, NTriples, N-Quads, Turtle, TriX, RDFa and Microdata. • a Graph interface which can be backed by any one of a number of Store implementations. • store implementations for in memory storage and persistent storage on top of the Berkeley DB. • a SPARQL 1.1 implementation - supporting SPARQL 1.1 Queries and Update statements. Contents 1 rdflib Documentation, Release 5.0.0-dev 2 Contents CHAPTER 1 Getting started If you never used RDFLib, click through these 1.1 Getting started with RDFLib 1.1.1 Installation RDFLib is open source and is maintained in a GitHub repository. RDFLib releases, current and previous are listed on PyPi The best way to install RDFLib is to use pip (sudo as required): $ pip install rdflib Support is available through the rdflib-dev group: http://groups.google.com/group/rdflib-dev and on the IRC channel #rdflib on the freenode.net server The primary interface that RDFLib exposes for working with RDF is a Graph. The package uses various Python idioms that offer an appropriate way to introduce RDF to a Python programmer who hasn’t worked with RDF before. RDFLib graphs are not sorted containers; they have ordinary set operations (e.g.
    [Show full text]