background preloader

Doc

Facebook Twitter

Namespaces in XML 1.0 (Third Edition) 1 Motivation and Summary We envision applications of Extensible Markup Language (XML) where a single XML document may contain elements and attributes (here referred to as a "markup vocabulary") that are defined for and used by multiple software modules.

Namespaces in XML 1.0 (Third Edition)

One motivation for this is modularity: if such a markup vocabulary exists which is well-understood and for which there is useful software available, it is better to re-use this markup rather than re-invent it. Such documents, containing multiple markup vocabularies, pose problems of recognition and collision. Software modules need to be able to recognize the elements and attributes which they are designed to process, even in the face of "collisions" occurring when markup intended for some other software package uses the same element name or attribute name. These considerations require that document constructs should have names constructed so as to avoid clashes between names from different markup vocabularies. 2 XML Namespaces Examples: <? <? Introduction_a_owl.pdf (Objet application/pdf) Cours5. Triplestore. Much like a relational database, one stores information in a triplestore and retrieves it via a query language.

Triplestore

Unlike a relational database, a triplestore is optimized for the storage and retrieval of triples. In addition to queries, triples can usually be imported/exported using Resource Description Framework (RDF) and other formats. Some triplestores can store billions of triples.[2] Implementation[edit] Some triplestores have been built as database engines from scratch, while others have been built on top of existing commercial relational database engines (i.e. List of implementations[edit] Technical overview[edit] The following table is an overview of available triplestores, their technical implementation, support for the SPARQL World Wide Web Consortium (W3C) recommendations, and available application programming interfaces (API).

See also[edit] Freebase uses a triplestore called graphd[citation needed]Named graph a.k.a. References[edit] French Translations of W3C Documents. RDF en quelques slides. Web Ontology Language. Un article de Wikipédia, l'encyclopédie libre.

Web Ontology Language

Pour les articles homonymes, voir OWL. Le langage OWL est basé sur les recherches effectuées dans le domaine de la logique de description. Il peut être vu en quelque sorte comme un standard informatique qui met en oeuvre certaines logiques de description, et permet à des outils qui comprennent OWL de travailler avec ces données, de vérifier que les données sont cohérentes, de déduire des connaissances nouvelles ou d'extraires certaines informations de cette base de données.

Il permet notamment de décrire des ontologies, c'est-à-dire qu'il permet de définir des terminologies pour décrire des domaines concrets. Une terminologie se constitue de concepts et de propriétés (aussi appelés « rôles » en logiques de description). Web Sémantique:OWL. Le guide du langage d'ontologie Web OWL. Recommandation du W3C du 10 février 2004 Cette version : Dernière version : Version précédente :

Le guide du langage d'ontologie Web OWL

RDF, description, comment l'utiliser notamment avec XUL. Cadre de Description de Ressources Selon les spécifications de W3C et la documentation de Mozilla Qu'est-ce que RDF?

RDF, description, comment l'utiliser notamment avec XUL

Le format RDF permet de combiner deux documents XML en un seul, en décrivant les relations entre les données, et est utilisé par XUL pour indiquer dans le fichier lui-même comment le programme affichera les données. Quand utiliser RDF? Ce format convient lorsque l'information doit avoir une structure correspondant à celle de l'outil qui l'utilise, une interface graphique le plus souvent. Lorsque également l'on veut agréger des sources de données séparées. Web S?mantique:RDF. RDF - Semantic Web Standards. Overview RDF is a standard model for data interchange on the Web.

RDF - Semantic Web Standards

RDF has features that facilitate data merging even if the underlying schemas differ, and it specifically supports the evolution of schemas over time without requiring all the data consumers to be changed. RDF extends the linking structure of the Web to use URIs to name the relationship between things as well as the two ends of the link (this is usually referred to as a “triple”). Using this simple model, it allows structured and semi-structured data to be mixed, exposed, and shared across different applications.

This linking structure forms a directed, labeled graph, where the edges represent the named link between two resources, represented by the graph nodes. Recommended Reading. HTML5+RDFa. A mechanism for embedding RDF in HTML Editor's Draft 13 July 2009 Latest Published Version: Not published Latest Editor's Draft: Previous Versions: None Contributors (alphabetical order): Ben Adida (Chair, Creative Commons) Mark Birbeck (Editor, RDFa Core and inventor of RDFa concept, Web Backplane Ltd.)

HTML5+RDFa

Shane McCarron (Editor, RDFa Core, Applied Testing and Technology, Inc.) Steven Pemberton (Chair, XHTML2, CWI) Manu Sporny, (Editor, HTML5+RDFa, Digital Bazaar, Inc.) Ralph R. Copyright © 2009 W3C® (MIT, ERCIM, Keio), All Rights Reserved. Abstract. Mon blog - Les ontologies graphiques. Php_rdf_tutorial.pdf (Objet application/pdf) Pearltrees, RDF & Perl.