Semantic MediaWiki/data

Tables

All of this information has been reverse-engineered, mostly from examination of data in a single SMW instance. I was not able to find any data-structure documentation in the official code docs.

Note that the schema version numbers are generally higher than the corresponding SMW version.

schema version 3 These are present in SMW version 1.9 alpha: /smw_di_*: /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

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.