Manuel:Gestion des données dans MediaWiki

Jump to navigation Jump to search
This page is a translated version of the page Manual:Managing data in MediaWiki and the translation is 8% complete.
Outdated translations are marked like this.
Other languages:
English • ‎français • ‎português • ‎中文 • ‎日本語

MediaWiki a été conçu pour gérer la plupart des informations textuelles et il le fait très bien.

Néanmoins, la seule manière de structurer le contenu est par Aide:Espaces de noms (cet article est dans l'espace de noms Manuel), Sous-pages ou Aide:Catégories (cet article a été mis dans le $4).

Si vous voulez géré les données structurées dans MediaWiki, par exemple une date ou un nombre, il existe plusieurs approches différentes pour cela, gérées par des extensions dédiées. Les différences et les similarités les plus communes sont indiquées dans la table suivante :

Fonction SemanticMediaWiki Logo.png
Semantic MediaWiki
Wikibase logo.svg
Cargo logo.png
Main usecase Managing data within a MediaWiki installation, based on Semantic Web standards. Powering Wikidata Managing data within a MediaWiki installation.
Approach Data (properties) are annotated within regular wikitext or by templates. With the datatype "reference", properties can be used to describe items using statements.[1] Properties are defined and used to describe Items using statements. Data is stored in database tables, with each table corresponding to a template.
Available since 2005 2012 2015
Active installations 1000s[2] 10s[3][4] 100s[5]
Community 134+ developers[6] 146 developers[7] 51 developers[8]
Storage MediaWiki database, Elasticsearch, 5 different SPARQL stores[9] MediaWiki database, Elasticsearch, SPARQL store (Blazegraph for MediaWiki database (or a separate database[10])
Property definition By typing wikitext. Properties can be invented freely. They will be of datatype page by default and can be defined later. Properties have to be defined before usage. Instead of using properties, data tables are defined with a predetermined (but reconfigurable) set of fields per table.
Value declaration Inline ([[MyProperty::MyValue]]) or with templates. Form-based data entry with Page Forms. Using forms. With parser functions in templates. Form-based data entry with Page Forms.
Predefined data types 18[11] 17[12] 18
Property management type definitions, constraint schemas, ontology import custom, or import of Wikidata ontology Instead of using properties, data tables are defined with a predetermined (but reconfigurable) set of fields per table.
Inline queries yes, with parser functions no (external SPARQL queries) yes, with parser functions
External querying yes, with either an API or SPARQL querying (available through special extensions such as RDFIO and LinkedWiki) yes, with SPARQL Query service yes, with an API
Result formats[13] ~ 63[14] 0, but visualisations via Query Service or other external tools, and on wiki data access via LUA ~ 25[15]
Development Github Gerrit Gerrit
Complementary extensions 28[16] to 51[17], e.g. Semantic Result Formats , Semantic Bundle , Semantic Scribunto ~7[18], e.g. Wikibase Client , WikibaseLexeme , Query Service 2 (Page Forms, Page Schemas). Cargo provides some or all of the functionality of Semantic MediaWiki, Semantic Result Formats, Maps, Semantic Drilldown, Semantic Compound Queries, Semantic Internal Objects and Semantic Scribunto.[19]
Complementary tools & services ? ? ?
Implementable on WMF wikis ? ? ?

Alternative comparisons


See also

  • Multi-Content Revisions - Ability to manage different independent content objects on the same wiki page by a technology change to the back-end of MediaWik.
  • DynamicPageList – Allows to extract data from pages.
  • WikiDB – Provides database features, somewhat similar to semantic properties.