Semantic MediaWiki/data: Difference between revisions

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
remaining gaps filled in; key tables boldfaced; one more explanation
new tables for schema v3
Line 1: Line 1:
==Tables==
==Tables==
As of SMW version 1.7:
{|
|-
| valign=top |
===schema version 3===
These are present in SMW version 1.9 alpha:
* [[/smw_di_blob]]
* [[/smw_di_bool]]
* [[/smw_di_coords]]
* [[/smw_di_number]]
* [[/smw_di_time]]
* [[/smw_di_url]]
* [[/smw_di_wikipage]]
* [[/smw_fpt_ask]]
* [[/smw_fpt_askde]]
* [[/smw_fpt_askfo]]
* [[/smw_fpt_asksi]]
* [[/smw_fpt_askst]]
* [[/smw_fpt_cdat]]
* [[/smw_fpt_conc]]
* [[/smw_fpt_conv]]
* [[/smw_fpt_impo]]
* [[/smw_fpt_inst]]
* [[/smw_fpt_ledt]]
* [[/smw_fpt_list]]
* [[/smw_fpt_mdat]]
* [[/smw_fpt_newp]]
* [[/smw_fpt_pval]]
* [[/smw_fpt_redi]]
* [[/smw_fpt_serv]]
* [[/smw_fpt_sf_af]]
* [[/smw_fpt_sf_df]]
* [[/smw_fpt_sobj]]
* [[/smw_fpt_subc]]
* [[/smw_fpt_subp]]
* [[/smw_fpt_type]]
* [[/smw_fpt_unit]]
* [[/smw_fpt_uri]]
* '''[[/smw_object_ids]]'''
* [[/smw_prop_stats]]
| valign=top |
===schema version 2===
These were present in SMW version 1.7, and may also be valid for 1.8 (but not 1.9):
* '''[[/smw_atts2]]''': relationships where the value is numerically/logically significant, or a "string" (non-page type)
* '''[[/smw_atts2]]''': relationships where the value is numerically/logically significant, or a "string" (non-page type)
* [[/smw_conc2]]: not sure; probably [[smw:Help:Concepts|concepts]]
* [[/smw_conc2]]: not sure; probably [[smw:Help:Concepts|concepts]]
Line 14: Line 55:


Core tables are boldfaced; the others seem to be primarily for optimization or auxiliary purposes.
Core tables are boldfaced; the others seem to be primarily for optimization or auxiliary purposes.
==Explanations==
====Explanations====
* Semantic relationships are defined in [[/smw rels2]], [[/smw_text2]], and [[/smw_atts2]].
* Semantic relationships are defined in [[/smw rels2]], [[/smw_text2]], and [[/smw_atts2]].
* Correspondence between SMW entities (property names and some property values) and MediaWiki pages is defined in [[/smw_ids]]
* Correspondence between SMW entities (property names and some property values) and MediaWiki pages is defined in [[/smw_ids]]
* Presumably the type of storage can be determined by looking up the SMW ID in [[/smw_spec2]], making it unnecessary to check multiple tables (rels2, text2, atts2) for each property. but it does not seem to have been designed for this purpose.
* Presumably the type of storage can be determined by looking up the SMW ID in [[/smw_spec2]], making it unnecessary to check multiple tables (rels2, text2, atts2) for each property. but it does not seem to have been designed for this purpose.
|}

Revision as of 15:12, 14 February 2013

Tables

schema version 3

These are present in SMW version 1.9 alpha:

schema version 2

These were present in SMW version 1.7, and may also be valid for 1.8 (but not 1.9):

  • /smw_atts2: relationships where the value is numerically/logically significant, or a "string" (non-page type)
  • /smw_conc2: not sure; probably concepts
  • /smw_conccache: not sure; presumably a cache for concepts
  • /smw_ids: assigns IDs to all properties, and values that map to a (potential) wiki page
  • /smw_inst2: not sure
  • /smw_redi2: not sure; redirects?
  • /smw_rels2: relationships where the value refers to a (potential) wiki page
  • /smw_spec2: URLs to SWiVT specs
  • /smw_subp2: not sure; sub-property map?
  • /smw_subs2: not sure; looks like a mapping of categories to sub-categories
  • /smw_text2: relationships where the value is a long text/data blob

Core tables are boldfaced; the others seem to be primarily for optimization or auxiliary purposes.

Explanations

  • Semantic relationships are defined in /smw rels2, /smw_text2, and /smw_atts2.
  • Correspondence between SMW entities (property names and some property values) and MediaWiki pages is defined in /smw_ids
  • Presumably the type of storage can be determined by looking up the SMW ID in /smw_spec2, making it unnecessary to check multiple tables (rels2, text2, atts2) for each property. but it does not seem to have been designed for this purpose.