RDF Schema. Un article de Wikipédia, l'encyclopédie libre. La première version de RDFS a été proposée en mars 1999, et la recommandation finale publiée par le W3C en février 2004. Les composants principaux de RDFS sont intégrés dans un langage d'ontologie plus expressif, OWL. Principales caractéristiques de RDFS[modifier | modifier le code] Classes et sous-classes[modifier | modifier le code] Un exemple simple de rdfs:Class est foaf:Person dans le vocabulaire FOAF. Une instance de la classe foaf:Person est une ressource liée à la classe en utilisant un prédicat rdf:type. L'expression formelle suivante en RDFS traduit la phrase en langage naturel : 'Jean est une personne'. ex:Jean rdf:type foaf:Person La définition de rdfs:Class est récursive. rdfs:Class est la classe de toutes les classes. rdfs:subClassOf permet de définir des hiérarchies de classes.
Par exemple, 'Toute personne est un Agent': foaf:Person rdfs:subClassOf foaf:Agent Propriétés[modifier | modifier le code] ex:Jean ex:travailledans ex:Societe_X. Linked Data | Linked Data - Connect Distributed Data across the Web. FOAF-a-matic -- Décrivez-vous en RDF. Written by Leigh Dodds. Introduction FOAF-a-matic is a simple Javascript application that allows you to create a FOAF ("Friend-of-A-Friend") description of yourself. You can read more about FOAF in Edd Dumbill's "XML Watch: Finding friends with XML and RDF" article, at the FOAF homepage on RDFWeb, and also the FOAF vocabulary description.
In short though, FOAF is a way to describe yourself -- your name, email address, and the people you're friends with -- using XML and RDF. This allows software to process these descriptions, perhaps as part of an automated search engine, to discover information about your and the communities of which you're a member. FOAF has the potential to drive many new interesting developments in online communities. The FOAF-a-Matic is being provided as a quick and easy way for you to create your own FOAF description. Note: none of the information you enter in this page is used or stored in any way. People You Know Tell FOAF-a-matic about some people you know.
License. Public-lod Mail Archives. Linked Data Platform Use Cases and Requirements. 3. User Stories Maintaining Social Contact Information Many of us have multiple email accounts that include information about the people and organizations we interact with – names, email addresses, telephone numbers, instant messenger identities and so on. When someone’s email address or telephone number changes (or they acquire a new one), our lives would be much simpler if we could update that information in one spot and all copies of it would automatically be updated.
Agreeing on a format for “the contact” is not enough, however. What would work in either case is a common understanding of the resource, a few formats needed, and access guidance for these resources. Keeping Track of Personal and Business Relationships In our daily lives, we deal with many different organizations in many different relationships, and they each have data about us. System and Software Development Tool Integration Library Linked Data The 'Digital Objects Cluster' contains a number of relevant use cases: 4. Interlinking. Linked Data is a method to publish data on the Web and to interlink data between different data sources. Linked Data can be accessed using Semantic Web browsers, just as traditional Web documents are accessed using HTML browsers. However, instead of following document links between HTML pages, Semantic Web browsers enable surfers to navigate between different data sources by following RDF links. RDF links can also be followed by robots or Semantic Web search engines in order to crawl the Semantic Web.
See Linked Data – The Story so far and How to publish Linked Data on the Web for more information about Linked Data. The DBpedia data set is interlinked with various other data sources (see voiD description). ) gives an overview of some of these data sources: The W3C Linking Open Data Community Project DBpedia is part of the W3C Linking Open Data community project, an effort to publish and interlink various open data sources. Linking to DBpedia from Your Dataset The Disco, Development. Tabulator: Async Javascript And Semantic Web. RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax. [Docs] [txt|pdf] [draft-fielding-...] [Tracker] [Diff1] [Diff2] [Errata] Updated by: 6874, 7320 INTERNET STANDARD Errata Exist Network Working Group T.
Berners-Lee Request for Comments: 3986 W3C/MIT STD: 66 R. Fielding Updates: 1738 Day Software Obsoletes: 2732, 2396, 1808 L. Masinter Category: Standards Track Adobe Systems January 2005 Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol.
RFC 3986 URI Generic Syntax January 2005 Table of Contents 1. RFC 3986 URI Generic Syntax January 2005 6. RFC 3986 URI Generic Syntax January 2005 1. A Uniform Resource Identifier (URI) provides a simple and extensible means for identifying a resource. 1.1. URIs are characterized as follows: Uniform Uniformity provides several benefits. 1.1.1. Tabulator: Async Javascript And Semantic Web. Linked Data - Design Issues. Up to Design Issues The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data. With linked data, when you have some of it, you can find other, related, data.
Like the web of hypertext, the web of data is constructed with documents on the web. However, unlike the web of hypertext, where links are relationships anchors in hypertext documents written in HTML, for data they links between arbitrary things described by RDF,. The URIs identify any kind of object or concept. But for HTML or RDF, the same expectations apply to make the web grow: Use URIs as names for things Use HTTP URIs so that people can look up those names. Simple.
The four rules I'll refer to the steps above as rules, but they are expectations of behavior. The first rule, to identify things with URIs, is pretty much understood by most people doing semantic web technology. The second rule, to use HTTP URIs, is also widely understood. Followup. Linked Data Platform Use Cases and Requirements. How to publish Linked Data on the Web.
This document provides a tutorial on how to publish Linked Data on the Web. After a general overview of the concept of Linked Data, we describe several practical recipes for publishing information as Linked Data on the Web. This tutorial has been superseeded by the book Linked Data: Evolving the Web into a Global Data Space written by Tom Heath and Christian Bizer. This tutorial was published in 2007 and is still online for historical reasons. The Linked Data book was published in 2011 and provides a more detailed and up-to-date introduction into Linked Data. The goal of Linked Data is to enable people to share structured data on the Web as easily as they can share documents today.
The term Linked Data was coined by Tim Berners-Lee in his Linked Data Web architecture note. Applying both principles leads to the creation of a data commons on the Web, a space where people and organizations can post and consume data about anything. This chapter describes the basic principles of Linked Data.