r66478 MediaWiki - Code Review archive

Repository:MediaWiki
Revision:r66477‎ | r66478 | r66479 >
Date:17:03, 15 May 2010
Author:jeroendedauw
Status:deferred
Tags:
Comment:
Changes for 1.5.1 - Moved entry point and settings file to conform with MW convention.
Modified paths:
  • /trunk/extensions/SemanticMediaWiki/INSTALL (modified) (history)
  • /trunk/extensions/SemanticMediaWiki/SMW_Settings.php (added) (history)
  • /trunk/extensions/SemanticMediaWiki/SemanticMediaWiki.php (added) (history)
  • /trunk/extensions/SemanticMediaWiki/includes/SMW_Settings.php (modified) (history)
  • /trunk/extensions/SemanticMediaWiki/includes/SMW_Setup.php (modified) (history)
  • /trunk/extensions/SemanticMediaWiki/includes/SMW_SetupLight.php (modified) (history)

Diff [purge]

Index: trunk/extensions/SemanticMediaWiki/INSTALL
@@ -75,7 +75,7 @@
7676 We abbreviate "[wikipath]/extensions/SemanticMediaWiki" as "[SMW_path]".
7777 (2) Insert the following two lines into "[wikipath]/LocalSettings.php":
7878
79 - include_once("$IP/extensions/SemanticMediaWiki/includes/SMW_Settings.php");
 79+ include_once("$IP/extensions/SemanticMediaWiki/SemanticMediaWiki.php");
8080 enableSemantics('example.org');
8181
8282 where example.org should be replaced by your server's name (or IP address).
@@ -100,7 +100,7 @@
101101 100 to 109. 100 and 101 are not used (they were used in early beta versions).
102102 106 and 107 are reserved for the SemanticForms extension. If you have your own
103103 custom namespaces, you have to set the parameter $smwgNamespaceIndex before
104 -including SMW_Settings.php. See the documentation $within SMW_Settings.php for
 104+including SemanticMediaWiki.php. See the documentation $within SMW_Settings.php for
105105 details. If you add more namespaces later on, then you have to assign them to
106106 higher numbers than those used by Semantic MediaWiki.
107107
Index: trunk/extensions/SemanticMediaWiki/includes/SMW_SetupLight.php
@@ -14,16 +14,6 @@
1515 * @ingroup SMW
1616 */
1717
18 -/**
19 - * This documentation group collects source code files belonging to Semantic
20 - * MediaWiki.
21 - *
22 - * For documenting extensions of SMW, please do not use groups starting with
23 - * "SMW" but make your own groups instead. Browsing at
24 - * http://semantic-mediawiki.org/doc/ is assumed to be easier this way.
25 - * @defgroup SMW Semantic MediaWiki
26 - */
27 -
2818 define( 'SMW_VERSION', '1.5.0.b-light-SVN' );
2919
3020 require_once( 'SMW_GlobalFunctions.php' );
Index: trunk/extensions/SemanticMediaWiki/includes/SMW_Setup.php
@@ -5,16 +5,6 @@
66 * @ingroup SMW
77 */
88
9 -/**
10 - * This documentation group collects source code files belonging to Semantic
11 - * MediaWiki.
12 - *
13 - * For documenting extensions of SMW, please do not use groups starting with
14 - * "SMW" but make your own groups instead. Browsing at
15 - * http://semantic-mediawiki.org/doc/ is assumed to be easier this way.
16 - * @defgroup SMW Semantic MediaWiki
17 - */
18 -
199 require_once( 'SMW_GlobalFunctions.php' );
2010
2111 define( 'SMW_VERSION', '1.5.0.b-SVN' );
Index: trunk/extensions/SemanticMediaWiki/includes/SMW_Settings.php
@@ -1,429 +1,13 @@
22 <?php
 3+
34 /**
4 - * @file
 5+ * File for backward compatibility with pre SMW 1.5.1.
 6+ * This used to be the main entrypoint for SMW, now moved to SemanticMediaWiki.php
 7+ *
 8+ * @file SMW_Settings.php
59 * @ingroup SMW
 10+ *
 11+ * @author Jeroen De Dauw
612 */
713
8 -#################################################################
9 -# CHANGING THE CONFIGURATION FOR SEMANTIC MEDIAWIKI #
10 -#################################################################
11 -# Do not change this file directly, but copy custom settings #
12 -# into your LocalSettings.php. Most settings should be make #
13 -# between including this file and the call to enableSemantics().#
14 -# Exceptions that need to be set before are documented below. #
15 -#################################################################
16 -
17 -if ( !defined( 'MEDIAWIKI' ) ) {
18 - die( "This file is part of the Semantic MediaWiki extension. It is not a valid entry point.\n" );
19 -}
20 -
21 -###
22 -# This is the path to your installation of Semantic MediaWiki as seen from the
23 -# web. Change it if required ($wgScriptPath is the path to the base directory
24 -# of your wiki). No final slash.
25 -##
26 -$smwgScriptPath = $wgScriptPath . '/extensions/SemanticMediaWiki';
27 -##
28 -
29 -###
30 -# This is the path to your installation of Semantic MediaWiki as seen on your
31 -# local filesystem. Used against some PHP file path issues.
32 -# If needed, you can also change this path in LocalSettings.php after including
33 -# this file.
34 -##
35 -$smwgIP = dirname( __FILE__ ) . '/../';
36 -##
37 -
38 -###
39 -# Use another storage backend for Semantic MediaWiki. The default is suitable
40 -# for most uses of SMW.
41 -##
42 -$smwgDefaultStore = "SMWSQLStore2";
43 -##
44 -
45 -// load global constants and setup functions
46 -require_once( 'SMW_Setup.php' );
47 -
48 -###
49 -# If you already have custom namespaces on your site, insert
50 -# $smwgNamespaceIndex = ???;
51 -# into your LocalSettings.php *before* including this file. The number ??? must
52 -# be the smallest even namespace number that is not in use yet. However, it
53 -# must not be smaller than 100.
54 -##
55 -smwfInitNamespaces();
56 -
57 -###
58 -# This setting allows you to select in which cases you want to have a factbox
59 -# appear below an article. Note that the Magic Words __SHOWFACTBOX__ and
60 -# __HIDEFACTBOX__ can be used to control Factbox display for individual pages.
61 -# Other options for this setting include:
62 -##
63 -// $smwgShowFactbox = SMW_FACTBOX_NONEMPTY; # show only those factboxes that have some content
64 -// $smwgShowFactbox = SMW_FACTBOX_SPECIAL # show only if special properties were set
65 -$smwgShowFactbox = SMW_FACTBOX_HIDDEN; # hide always
66 -// $smwgShowFactbox = SMW_FACTBOX_SHOWN; # show always, buggy and not recommended
67 -##
68 -
69 -###
70 -# Same as $smwgShowFactbox but for edit mode and same possible values.
71 -##
72 -$smwgShowFactboxEdit = SMW_FACTBOX_NONEMPTY;
73 -##
74 -
75 -###
76 -# Should the toolbox of each content page show a link to browse the properties
77 -# of that page using Special:Browse? This is a useful way to access properties
78 -# and it is somewhat more subtle than showing a Factbox on every page.
79 -##
80 -$smwgToolboxBrowseLink = true;
81 -##
82 -
83 -###
84 -# Should warnings be displayed in wikitexts right after the problematic input?
85 -# This affects only semantic annotations, not warnings that are displayed by
86 -# inline queries or other features.
87 -##
88 -$smwgInlineErrors = true;
89 -##
90 -
91 -###
92 -# Should SMW consider MediaWiki's subcategory hierarchy in querying? If set to
93 -# true, subcategories will always be interpreted like subclasses. For example,
94 -# if A is a subcategory of B then a query for all elements of B will also yield
95 -# all elements of A. If this setting is disabled, then subclass relationships
96 -# can still be given explicitly by using the property "subcategory of" on some
97 -# category page. Only if the setting is false will such annotations be shown in
98 -# the factbox (if enabled).
99 -##
100 -$smwgUseCategoryHierarchy = true;
101 -##
102 -
103 -###
104 -# Should category pages that use some [[Category:Foo]] statement be treated as
105 -# elements of the category Foo? If disabled, then it is not possible to make
106 -# category pages elements of other categories. See also the above setting
107 -# $smwgUseCategoryHierarchy.
108 -##
109 -$smwgCategoriesAsInstances = true;
110 -##
111 -
112 -###
113 -# Should SMW accept inputs like [[property::Some [[link]] in value]]? If
114 -# enabled, this may lead to PHP crashes (!) when very long texts are used as
115 -# values. This is due to limitations in the library PCRE that PHP uses for
116 -# pattern matching. The provoked PHP crashes will prevent requests from being
117 -# completed -- usually clients will receive server errors ("invalid response")
118 -# or be offered to download "index.php". It might be okay to enable this if
119 -# such problems are not observed in your wiki.
120 -##
121 -$smwgLinksInValues = false;
122 -##
123 -
124 -###
125 -# Settings for recurring events, created with the #set_recurring_event parser
126 -# function: the default number of instances defined, if no end date is set;
127 -# and the maximum number that can be defined, regardless of end date.
128 -##
129 -$smwgDefaultNumRecurringEvents = 100;
130 -$smwgMaxNumRecurringEvents = 500;
131 -##
132 -
133 -###
134 -# Should the browse view for incoming links show the incoming links via its
135 -# inverses, or shall they be displayed on the other side?
136 -##
137 -$smwgBrowseShowInverse = false;
138 -##
139 -
140 -###
141 -# Should the browse view always show the incoming links as well, and more of
142 -# the incoming values?
143 -##
144 -$smwgBrowseShowAll = true;
145 -##
146 -
147 -###
148 -# Should the search by property special page display nearby results when there
149 -# are only a few results with the exact value? Switch this off if this page has
150 -# performance problems.
151 -##
152 -$smwgSearchByPropertyFuzzy = true;
153 -
154 -###
155 -# Number results shown in the listings on pages in the namespaces Property,
156 -# Type, and Concept. If a value of 0 is given, the respective listings are
157 -# hidden completely.
158 -##
159 -$smwgTypePagingLimit = 200; // same number as for categories
160 -$smwgConceptPagingLimit = 200; // same number as for categories
161 -$smwgPropertyPagingLimit = 25; // use smaller value since property lists need more space
162 -##
163 -
164 -###
165 -# How many values should at most be displayed for a page on the Property page?
166 -##
167 -$smwgMaxPropertyValues = 3; // if large values are desired, consider reducing $smwgPropertyPagingLimit for better performance
168 -##
169 -
170 -###
171 -# Settings for inline queries ({{#ask:...}}) and for semantic queries in
172 -# general. This can especially be used to prevent overly high server-load due
173 -# to complex queries. The following settings affect all queries, wherever they
174 -# occur.
175 -##
176 -$smwgQEnabled = true; // (De)activates all query related features and interfaces
177 -$smwgQMaxLimit = 10000; // Max number of results *ever* retrieved, even when using special query pages.
178 -$smwgIgnoreQueryErrors = true; // Should queries be executed even if some errors were detected?
179 - // A hint that points out errors is shown in any case.
180 -
181 -$smwgQSubcategoryDepth = 10; // Restrict level of sub-category inclusion (steps within category hierarchy)
182 -$smwgQSubpropertyDepth = 10; // Restrict level of sub-property inclusion (steps within property hierarchy)
183 - // (Use 0 to disable hierarchy-inferencing in queries)
184 -$smwgQEqualitySupport = SMW_EQ_SOME; // Evaluate #redirects as equality between page names, with possible
185 - // performance-relevant restrictions depending on the storage engine
186 - // $smwgQEqualitySupport = SMW_EQ_FULL; // Evaluate #redirects as equality between page names in all cases
187 - // $smwgQEqualitySupport = SMW_EQ_NONE; // Never evaluate #redirects as equality between page names
188 -$smwgQSortingSupport = true; // (De)activate sorting of results.
189 -$smwgQRandSortingSupport = true; // (De)activate random sorting of results.
190 -$smwgQDefaultNamespaces = null; // Which namespaces should be searched by default?
191 - // (value NULL switches off default restrictions on searching -- this is faster)
192 - // Example with namespaces: $smwgQDefaultNamespaces = array(NS_MAIN, NS_IMAGE);
193 -$smwgQComparators = '<|>|!|~'; // List of comparator characters supported by queries, separated by '|'
194 - // Available entries: < (smaller than), < (greater than), ! (unequal to),
195 - // ~ (pattern with '*' as wildcard, only for Type:String)
196 - // If unsupported comparators are used, they are treated as part of the queried value
197 -
198 -###
199 -# Further settings for queries. The following settings affect inline queries
200 -# and querying special pages. Essentially they should mirror the kind of
201 -# queries that should immediately be answered by the wiki, using whatever
202 -# computations are needed.
203 -##
204 -$smwgQMaxSize = 12; // Maximal number of conditions in queries, use format=debug for example sizes
205 -$smwgQMaxDepth = 4; // Maximal property depth of queries, e.g. [[rel::<q>[[rel2::Test]]</q>]] has depth 2
206 -
207 -// The below setting defines which query features should be available by default.
208 -// Examples:
209 -// only cateory intersections: $smwgQFeatures = SMW_CATEGORY_QUERY | SMW_CONJUNCTION_QUERY;
210 -// only single concepts: $smwgQFeatures = SMW_CONCEPT_QUERY;
211 -// anything but disjunctions: $smwgQFeatures = SMW_ANY_QUERY & ~SMW_DISJUNCTION_QUERY;
212 -// The default is to support all basic features.
213 -$smwgQFeatures = SMW_PROPERTY_QUERY | SMW_CATEGORY_QUERY | SMW_CONCEPT_QUERY |
214 - SMW_NAMESPACE_QUERY | SMW_CONJUNCTION_QUERY | SMW_DISJUNCTION_QUERY;
215 -
216 -### Settings about printout of (especially inline) queries:
217 -$smwgQDefaultLimit = 50; // Default number of rows returned in a query. Can be increased with limit=num in #ask
218 -$smwgQMaxInlineLimit = 500; // Max number of rows ever printed in a single inline query on a single page.
219 -$smwgQPrintoutLimit = 100; // Max number of supported printouts (added columns in result table, ?-statements)
220 -$smwgQDefaultLinking = 'all'; // Default linking behaviour. Can be one of "none", "subject" (first column), "all".
221 -
222 -
223 -###
224 -# Further settings for queries. The following settings affect queries that are
225 -# part of concept pages. These are usually chosen to be les restricted than
226 -# inline queries, since there are two other means for controling their use:
227 -# (1) Concept queries that would not be allowed as normal queries will not be
228 -# executed directly, but can use pre-computed results instead. This is the
229 -# default.
230 -# (2) The whole Concept: namespace can be restricted (using some suitable
231 -# MediaWiki extension) to an experienced user group that may create more
232 -# complex queries responably. Other users can employ thus defined concepts in
233 -# their queries.
234 -##
235 -$smwgQConceptCaching = CONCEPT_CACHE_HARD; // Which concepts should be displayed only if available from cache?
236 - // CONCEPT_CACHE_ALL -- show concept elements anywhere only if they are cached
237 - // CONCEPT_CACHE_HARD -- show without cache if concept is not harder than permitted inline queries
238 - // CONCEPT_CACHE_NONE -- show all concepts even without any cache
239 - // In any cases, caches will always be used if available.
240 -$smwgQConceptMaxSize = 20; // Same as $smwgQMaxSize, but for concepts
241 -$smwgQConceptMaxDepth = 8; // Same as $smwgQMaxDepth, but for concepts
242 -
243 -// Same as $smwgQFeatures but for concepts (note: using concepts in concepts is currently not supported!)
244 -$smwgQConceptFeatures = SMW_PROPERTY_QUERY | SMW_CATEGORY_QUERY | SMW_NAMESPACE_QUERY |
245 - SMW_CONJUNCTION_QUERY | SMW_DISJUNCTION_QUERY;
246 -
247 -// Cache life time in minutes. If a concept cache exists but is older than
248 -// this, SMW tries to recompute it, and will only use the cache if this is not
249 -// allowed due to settings above:
250 -$smwgQConceptCacheLifetime = 24 * 60;
251 -
252 -
253 -### Predefined result formats for queries
254 -# Array of available formats for formatting queries. Can be redefined in
255 -# the settings to disallow certain formats or to register extension formats.
256 -# To disable a format, do "unset($smwgResultFormats['template']);" Disabled
257 -# formats will be treated like if the format parameter had been omitted. The
258 -# formats 'table' and 'list' are defaults that cannot be disabled. The format
259 -# 'broadtable' should not be disabled either in order not to break Special:ask.
260 -##
261 -$smwgResultFormats = array(
262 - 'table' => 'SMWTableResultPrinter',
263 - 'list' => 'SMWListResultPrinter',
264 - 'ol' => 'SMWListResultPrinter',
265 - 'ul' => 'SMWListResultPrinter',
266 - 'broadtable' => 'SMWTableResultPrinter',
267 - 'category' => 'SMWCategoryResultPrinter',
268 - 'embedded' => 'SMWEmbeddedResultPrinter',
269 - 'template' => 'SMWListResultPrinter',
270 - 'count' => 'SMWListResultPrinter',
271 - 'debug' => 'SMWListResultPrinter',
272 - 'rss' => 'SMWRSSResultPrinter',
273 - 'csv' => 'SMWCsvResultPrinter',
274 - 'json' => 'SMWJSONResultPrinter'
275 -);
276 -##
277 -
278 -### Predefined aliases for result formats
279 -# Array of available aliases for result formats. Can be redefined in
280 -# the settings to disallow certain aliases or to register extension aliases.
281 -# To disable an alias, do "unset($smwgResultAliases['alias']);" Disabled
282 -# aliases will be treated like if the alias parameter had been omitted.
283 -##
284 -$smwgResultAliases = array();
285 -##
286 -
287 -### Predefined sources for queries
288 -# Array of available sources for answering queries. Can be redefined in
289 -# the settings to register new sources (usually an extension will do so
290 -# on installation). Unknown source will be rerouted to the local wiki.
291 -# Note that the basic installation comes with no additional source besides
292 -# the local source (which in turn cannot be disabled or set explicitly).
293 -# Set a new store like this: $smwgQuerySources['freebase'] = "SMWFreebaseStore";
294 -##
295 -$smwgQuerySources = array(
296 -// 'local' => '',
297 -);
298 -##
299 -
300 -### Default property type
301 -# Undefined properties (those without pages or whose pages have no "has type"
302 -# statement) will be assumed to be of this type. This is an internal type id.
303 -# See the file languages/SMW_LanguageXX.php to find what IDs to use for
304 -# datatpyes in your language. The default corresponds to "Type:Page".
305 -##
306 -$smwgPDefaultType = '_wpg';
307 -##
308 -
309 -###
310 -# Settings for RSS export
311 -##
312 -$smwgRSSEnabled = true; // use to switch off RSS (it's not worse than querying Special:Ask, but attracts more users)
313 -$smwgRSSWithPages = true; // Should RSS feeds deliver whole pages or just link to them?
314 -##
315 -
316 -###
317 -# Settings for OWL/RDF export
318 -##
319 -$smwgAllowRecursiveExport = false; // can normal users request recursive export?
320 -$smwgExportBacklinks = true; // should backlinks be included by default?
321 -$smwgOWLFullExport = false; // decides, if the RDF export will export, by default,
322 - // OWL Full or rather nice OWL DL.
323 - // Can be overriden in the RDF export class.
324 -// global $smwgNamespace; // The Namespace of exported URIs.
325 -// $smwgNamespace = "http://example.org/id/"; // Will be set automatically if
326 -// nothing is given, but in order to make pretty URIs you will need to set this
327 -// to something nice and adapt your Apache configuration appropriately. This is
328 -// done, e.g., on semanticweb.org, where URIs are of the form
329 -// http://semanticweb.org/id/FOAF
330 -##
331 -
332 -###
333 -# The maximal number that SMW will normally display without using scientific exp
334 -# notation. The deafult is rather large since some users have problems understanding
335 -# exponents. Scineitfic applications may prefer a smaller value for concise display.
336 -##
337 -$smwgMaxNonExpNumber = 1000000000000000;
338 -##
339 -
340 -###
341 -# SMW defers some tasks until after a page was edited by using the MediaWiki
342 -# job queueing system (see http://www.mediawiki.org/wiki/Manual:Job_queue).
343 -# For example, when the type of a property is changed, all affected pages will
344 -# be scheduled for (later) update. If a wiki generates too many jobs in this
345 -# way (Special:Statistics and "showJobs.php" can be used to check that), the
346 -# following setting can be used to disable jobs. Note that this will cause some
347 -# parts of the semantic data to get out of date, so that manual modifications
348 -# or the use of SMW_refreshData.php might be needed.
349 -##
350 -$smwgEnableUpdateJobs = true;
351 -##
352 -
353 -###
354 -# Overwriting the following array, you can define for which namespaces
355 -# the semantic links and annotations are to be evaluated. On other
356 -# pages, annotations can be given but are silently ignored. This is
357 -# useful since, e.g., talk pages usually do not have attributes and
358 -# the like. In fact, is is not obvious what a meaningful attribute of
359 -# a talk page could be. Pages without annotations will also be ignored
360 -# during full RDF export, unless they are referred to from another
361 -# article.
362 -##
363 -$smwgNamespacesWithSemanticLinks = array(
364 - NS_MAIN => true,
365 - NS_TALK => false,
366 - NS_USER => true,
367 - NS_USER_TALK => false,
368 - NS_PROJECT => true,
369 - NS_PROJECT_TALK => false,
370 - NS_IMAGE => true,
371 - NS_IMAGE_TALK => false,
372 - NS_MEDIAWIKI => false,
373 - NS_MEDIAWIKI_TALK => false,
374 - NS_TEMPLATE => false,
375 - NS_TEMPLATE_TALK => false,
376 - NS_HELP => true,
377 - NS_HELP_TALK => false,
378 - NS_CATEGORY => true,
379 - NS_CATEGORY_TALK => false,
380 - SMW_NS_PROPERTY => true,
381 - SMW_NS_PROPERTY_TALK => false,
382 - SMW_NS_TYPE => true,
383 - SMW_NS_TYPE_TALK => false,
384 - SMW_NS_CONCEPT => true,
385 - SMW_NS_CONCEPT_TALK => false,
386 -);
387 -##
388 -
389 -###
390 -# Properties (usually given as internal ids or DB key versions of property
391 -# titles) that are relevant for declaring the behaviour of a property P on a
392 -# property page in the sense that changing their values requires that all
393 -# pages that use P must be processed again. For example, if _PVAL (allowed
394 -# values) for a property change, then pages must be processed again. This
395 -# setting is not normally changed by users but by extensions that add new
396 -# types that have their own additional declaration properties.
397 -##
398 -$smwgDeclarationProperties = array( '_PVAL', '_LIST' );
399 -##
400 -
401 -// some default settings which usually need no modification
402 -
403 -###
404 -# -- FEATURE IS DISABLED --
405 -# Setting this to true allows to translate all the labels within
406 -# the browser GIVEN that they have interwiki links.
407 -##
408 -$smwgTranslate = false;
409 -
410 -###
411 -# -- FEATURE IS DISABLED --
412 -# If you want to import ontologies, you need to install RAP,
413 -# a free RDF API for PHP, see
414 -# http://www.wiwiss.fu-berlin.de/suhl/bizer/rdfapi/
415 -# The following is the path to your installation of RAP
416 -# (the directory where you extracted the files to) as seen
417 -# from your local filesystem. Note that ontology import is
418 -# highly experimental at the moment, and may not do what you
419 -# extect.
420 -##
421 -// $smwgRAPPath = $smwgIP . 'libs/rdfapi-php';
422 -// $smwgRAPPath = '/another/example/path/rdfapi-php';
423 -##
424 -
425 -###
426 -# If the following is set to true, it is possible to initiate the repairing
427 -# or updating of all wiki data using the interface on Special:SMWAdmin.
428 -##
429 -$smwgAdminRefreshStore = true;
430 -##
 14+require_once dirname( __FILE__ ) . '/../SMW_settings.php';
\ No newline at end of file
Index: trunk/extensions/SemanticMediaWiki/SMW_Settings.php
@@ -0,0 +1,430 @@
 2+<?php
 3+
 4+/**
 5+ * @file
 6+ * @ingroup SMW
 7+ */
 8+
 9+#################################################################
 10+# CHANGING THE CONFIGURATION FOR SEMANTIC MEDIAWIKI #
 11+#################################################################
 12+# Do not change this file directly, but copy custom settings #
 13+# into your LocalSettings.php. Most settings should be make #
 14+# between including this file and the call to enableSemantics().#
 15+# Exceptions that need to be set before are documented below. #
 16+#################################################################
 17+
 18+if ( !defined( 'MEDIAWIKI' ) ) {
 19+ die( "This file is part of the Semantic MediaWiki extension. It is not a valid entry point.\n" );
 20+}
 21+
 22+###
 23+# This is the path to your installation of Semantic MediaWiki as seen from the
 24+# web. Change it if required ($wgScriptPath is the path to the base directory
 25+# of your wiki). No final slash.
 26+##
 27+$smwgScriptPath = $wgScriptPath . '/extensions/SemanticMediaWiki';
 28+##
 29+
 30+###
 31+# This is the path to your installation of Semantic MediaWiki as seen on your
 32+# local filesystem. Used against some PHP file path issues.
 33+# If needed, you can also change this path in LocalSettings.php after including
 34+# this file.
 35+##
 36+$smwgIP = dirname( __FILE__ ) . '/';
 37+##
 38+
 39+###
 40+# Use another storage backend for Semantic MediaWiki. The default is suitable
 41+# for most uses of SMW.
 42+##
 43+$smwgDefaultStore = "SMWSQLStore2";
 44+##
 45+
 46+// load global constants and setup functions
 47+require_once( 'includes/SMW_Setup.php' );
 48+
 49+###
 50+# If you already have custom namespaces on your site, insert
 51+# $smwgNamespaceIndex = ???;
 52+# into your LocalSettings.php *before* including this file. The number ??? must
 53+# be the smallest even namespace number that is not in use yet. However, it
 54+# must not be smaller than 100.
 55+##
 56+smwfInitNamespaces();
 57+
 58+###
 59+# This setting allows you to select in which cases you want to have a factbox
 60+# appear below an article. Note that the Magic Words __SHOWFACTBOX__ and
 61+# __HIDEFACTBOX__ can be used to control Factbox display for individual pages.
 62+# Other options for this setting include:
 63+##
 64+// $smwgShowFactbox = SMW_FACTBOX_NONEMPTY; # show only those factboxes that have some content
 65+// $smwgShowFactbox = SMW_FACTBOX_SPECIAL # show only if special properties were set
 66+$smwgShowFactbox = SMW_FACTBOX_HIDDEN; # hide always
 67+// $smwgShowFactbox = SMW_FACTBOX_SHOWN; # show always, buggy and not recommended
 68+##
 69+
 70+###
 71+# Same as $smwgShowFactbox but for edit mode and same possible values.
 72+##
 73+$smwgShowFactboxEdit = SMW_FACTBOX_NONEMPTY;
 74+##
 75+
 76+###
 77+# Should the toolbox of each content page show a link to browse the properties
 78+# of that page using Special:Browse? This is a useful way to access properties
 79+# and it is somewhat more subtle than showing a Factbox on every page.
 80+##
 81+$smwgToolboxBrowseLink = true;
 82+##
 83+
 84+###
 85+# Should warnings be displayed in wikitexts right after the problematic input?
 86+# This affects only semantic annotations, not warnings that are displayed by
 87+# inline queries or other features.
 88+##
 89+$smwgInlineErrors = true;
 90+##
 91+
 92+###
 93+# Should SMW consider MediaWiki's subcategory hierarchy in querying? If set to
 94+# true, subcategories will always be interpreted like subclasses. For example,
 95+# if A is a subcategory of B then a query for all elements of B will also yield
 96+# all elements of A. If this setting is disabled, then subclass relationships
 97+# can still be given explicitly by using the property "subcategory of" on some
 98+# category page. Only if the setting is false will such annotations be shown in
 99+# the factbox (if enabled).
 100+##
 101+$smwgUseCategoryHierarchy = true;
 102+##
 103+
 104+###
 105+# Should category pages that use some [[Category:Foo]] statement be treated as
 106+# elements of the category Foo? If disabled, then it is not possible to make
 107+# category pages elements of other categories. See also the above setting
 108+# $smwgUseCategoryHierarchy.
 109+##
 110+$smwgCategoriesAsInstances = true;
 111+##
 112+
 113+###
 114+# Should SMW accept inputs like [[property::Some [[link]] in value]]? If
 115+# enabled, this may lead to PHP crashes (!) when very long texts are used as
 116+# values. This is due to limitations in the library PCRE that PHP uses for
 117+# pattern matching. The provoked PHP crashes will prevent requests from being
 118+# completed -- usually clients will receive server errors ("invalid response")
 119+# or be offered to download "index.php". It might be okay to enable this if
 120+# such problems are not observed in your wiki.
 121+##
 122+$smwgLinksInValues = false;
 123+##
 124+
 125+###
 126+# Settings for recurring events, created with the #set_recurring_event parser
 127+# function: the default number of instances defined, if no end date is set;
 128+# and the maximum number that can be defined, regardless of end date.
 129+##
 130+$smwgDefaultNumRecurringEvents = 100;
 131+$smwgMaxNumRecurringEvents = 500;
 132+##
 133+
 134+###
 135+# Should the browse view for incoming links show the incoming links via its
 136+# inverses, or shall they be displayed on the other side?
 137+##
 138+$smwgBrowseShowInverse = false;
 139+##
 140+
 141+###
 142+# Should the browse view always show the incoming links as well, and more of
 143+# the incoming values?
 144+##
 145+$smwgBrowseShowAll = true;
 146+##
 147+
 148+###
 149+# Should the search by property special page display nearby results when there
 150+# are only a few results with the exact value? Switch this off if this page has
 151+# performance problems.
 152+##
 153+$smwgSearchByPropertyFuzzy = true;
 154+
 155+###
 156+# Number results shown in the listings on pages in the namespaces Property,
 157+# Type, and Concept. If a value of 0 is given, the respective listings are
 158+# hidden completely.
 159+##
 160+$smwgTypePagingLimit = 200; // same number as for categories
 161+$smwgConceptPagingLimit = 200; // same number as for categories
 162+$smwgPropertyPagingLimit = 25; // use smaller value since property lists need more space
 163+##
 164+
 165+###
 166+# How many values should at most be displayed for a page on the Property page?
 167+##
 168+$smwgMaxPropertyValues = 3; // if large values are desired, consider reducing $smwgPropertyPagingLimit for better performance
 169+##
 170+
 171+###
 172+# Settings for inline queries ({{#ask:...}}) and for semantic queries in
 173+# general. This can especially be used to prevent overly high server-load due
 174+# to complex queries. The following settings affect all queries, wherever they
 175+# occur.
 176+##
 177+$smwgQEnabled = true; // (De)activates all query related features and interfaces
 178+$smwgQMaxLimit = 10000; // Max number of results *ever* retrieved, even when using special query pages.
 179+$smwgIgnoreQueryErrors = true; // Should queries be executed even if some errors were detected?
 180+ // A hint that points out errors is shown in any case.
 181+
 182+$smwgQSubcategoryDepth = 10; // Restrict level of sub-category inclusion (steps within category hierarchy)
 183+$smwgQSubpropertyDepth = 10; // Restrict level of sub-property inclusion (steps within property hierarchy)
 184+ // (Use 0 to disable hierarchy-inferencing in queries)
 185+$smwgQEqualitySupport = SMW_EQ_SOME; // Evaluate #redirects as equality between page names, with possible
 186+ // performance-relevant restrictions depending on the storage engine
 187+ // $smwgQEqualitySupport = SMW_EQ_FULL; // Evaluate #redirects as equality between page names in all cases
 188+ // $smwgQEqualitySupport = SMW_EQ_NONE; // Never evaluate #redirects as equality between page names
 189+$smwgQSortingSupport = true; // (De)activate sorting of results.
 190+$smwgQRandSortingSupport = true; // (De)activate random sorting of results.
 191+$smwgQDefaultNamespaces = null; // Which namespaces should be searched by default?
 192+ // (value NULL switches off default restrictions on searching -- this is faster)
 193+ // Example with namespaces: $smwgQDefaultNamespaces = array(NS_MAIN, NS_IMAGE);
 194+$smwgQComparators = '<|>|!|~'; // List of comparator characters supported by queries, separated by '|'
 195+ // Available entries: < (smaller than), < (greater than), ! (unequal to),
 196+ // ~ (pattern with '*' as wildcard, only for Type:String)
 197+ // If unsupported comparators are used, they are treated as part of the queried value
 198+
 199+###
 200+# Further settings for queries. The following settings affect inline queries
 201+# and querying special pages. Essentially they should mirror the kind of
 202+# queries that should immediately be answered by the wiki, using whatever
 203+# computations are needed.
 204+##
 205+$smwgQMaxSize = 12; // Maximal number of conditions in queries, use format=debug for example sizes
 206+$smwgQMaxDepth = 4; // Maximal property depth of queries, e.g. [[rel::<q>[[rel2::Test]]</q>]] has depth 2
 207+
 208+// The below setting defines which query features should be available by default.
 209+// Examples:
 210+// only cateory intersections: $smwgQFeatures = SMW_CATEGORY_QUERY | SMW_CONJUNCTION_QUERY;
 211+// only single concepts: $smwgQFeatures = SMW_CONCEPT_QUERY;
 212+// anything but disjunctions: $smwgQFeatures = SMW_ANY_QUERY & ~SMW_DISJUNCTION_QUERY;
 213+// The default is to support all basic features.
 214+$smwgQFeatures = SMW_PROPERTY_QUERY | SMW_CATEGORY_QUERY | SMW_CONCEPT_QUERY |
 215+ SMW_NAMESPACE_QUERY | SMW_CONJUNCTION_QUERY | SMW_DISJUNCTION_QUERY;
 216+
 217+### Settings about printout of (especially inline) queries:
 218+$smwgQDefaultLimit = 50; // Default number of rows returned in a query. Can be increased with limit=num in #ask
 219+$smwgQMaxInlineLimit = 500; // Max number of rows ever printed in a single inline query on a single page.
 220+$smwgQPrintoutLimit = 100; // Max number of supported printouts (added columns in result table, ?-statements)
 221+$smwgQDefaultLinking = 'all'; // Default linking behaviour. Can be one of "none", "subject" (first column), "all".
 222+
 223+
 224+###
 225+# Further settings for queries. The following settings affect queries that are
 226+# part of concept pages. These are usually chosen to be les restricted than
 227+# inline queries, since there are two other means for controling their use:
 228+# (1) Concept queries that would not be allowed as normal queries will not be
 229+# executed directly, but can use pre-computed results instead. This is the
 230+# default.
 231+# (2) The whole Concept: namespace can be restricted (using some suitable
 232+# MediaWiki extension) to an experienced user group that may create more
 233+# complex queries responably. Other users can employ thus defined concepts in
 234+# their queries.
 235+##
 236+$smwgQConceptCaching = CONCEPT_CACHE_HARD; // Which concepts should be displayed only if available from cache?
 237+ // CONCEPT_CACHE_ALL -- show concept elements anywhere only if they are cached
 238+ // CONCEPT_CACHE_HARD -- show without cache if concept is not harder than permitted inline queries
 239+ // CONCEPT_CACHE_NONE -- show all concepts even without any cache
 240+ // In any cases, caches will always be used if available.
 241+$smwgQConceptMaxSize = 20; // Same as $smwgQMaxSize, but for concepts
 242+$smwgQConceptMaxDepth = 8; // Same as $smwgQMaxDepth, but for concepts
 243+
 244+// Same as $smwgQFeatures but for concepts (note: using concepts in concepts is currently not supported!)
 245+$smwgQConceptFeatures = SMW_PROPERTY_QUERY | SMW_CATEGORY_QUERY | SMW_NAMESPACE_QUERY |
 246+ SMW_CONJUNCTION_QUERY | SMW_DISJUNCTION_QUERY;
 247+
 248+// Cache life time in minutes. If a concept cache exists but is older than
 249+// this, SMW tries to recompute it, and will only use the cache if this is not
 250+// allowed due to settings above:
 251+$smwgQConceptCacheLifetime = 24 * 60;
 252+
 253+
 254+### Predefined result formats for queries
 255+# Array of available formats for formatting queries. Can be redefined in
 256+# the settings to disallow certain formats or to register extension formats.
 257+# To disable a format, do "unset($smwgResultFormats['template']);" Disabled
 258+# formats will be treated like if the format parameter had been omitted. The
 259+# formats 'table' and 'list' are defaults that cannot be disabled. The format
 260+# 'broadtable' should not be disabled either in order not to break Special:ask.
 261+##
 262+$smwgResultFormats = array(
 263+ 'table' => 'SMWTableResultPrinter',
 264+ 'list' => 'SMWListResultPrinter',
 265+ 'ol' => 'SMWListResultPrinter',
 266+ 'ul' => 'SMWListResultPrinter',
 267+ 'broadtable' => 'SMWTableResultPrinter',
 268+ 'category' => 'SMWCategoryResultPrinter',
 269+ 'embedded' => 'SMWEmbeddedResultPrinter',
 270+ 'template' => 'SMWListResultPrinter',
 271+ 'count' => 'SMWListResultPrinter',
 272+ 'debug' => 'SMWListResultPrinter',
 273+ 'rss' => 'SMWRSSResultPrinter',
 274+ 'csv' => 'SMWCsvResultPrinter',
 275+ 'json' => 'SMWJSONResultPrinter'
 276+);
 277+##
 278+
 279+### Predefined aliases for result formats
 280+# Array of available aliases for result formats. Can be redefined in
 281+# the settings to disallow certain aliases or to register extension aliases.
 282+# To disable an alias, do "unset($smwgResultAliases['alias']);" Disabled
 283+# aliases will be treated like if the alias parameter had been omitted.
 284+##
 285+$smwgResultAliases = array();
 286+##
 287+
 288+### Predefined sources for queries
 289+# Array of available sources for answering queries. Can be redefined in
 290+# the settings to register new sources (usually an extension will do so
 291+# on installation). Unknown source will be rerouted to the local wiki.
 292+# Note that the basic installation comes with no additional source besides
 293+# the local source (which in turn cannot be disabled or set explicitly).
 294+# Set a new store like this: $smwgQuerySources['freebase'] = "SMWFreebaseStore";
 295+##
 296+$smwgQuerySources = array(
 297+// 'local' => '',
 298+);
 299+##
 300+
 301+### Default property type
 302+# Undefined properties (those without pages or whose pages have no "has type"
 303+# statement) will be assumed to be of this type. This is an internal type id.
 304+# See the file languages/SMW_LanguageXX.php to find what IDs to use for
 305+# datatpyes in your language. The default corresponds to "Type:Page".
 306+##
 307+$smwgPDefaultType = '_wpg';
 308+##
 309+
 310+###
 311+# Settings for RSS export
 312+##
 313+$smwgRSSEnabled = true; // use to switch off RSS (it's not worse than querying Special:Ask, but attracts more users)
 314+$smwgRSSWithPages = true; // Should RSS feeds deliver whole pages or just link to them?
 315+##
 316+
 317+###
 318+# Settings for OWL/RDF export
 319+##
 320+$smwgAllowRecursiveExport = false; // can normal users request recursive export?
 321+$smwgExportBacklinks = true; // should backlinks be included by default?
 322+$smwgOWLFullExport = false; // decides, if the RDF export will export, by default,
 323+ // OWL Full or rather nice OWL DL.
 324+ // Can be overriden in the RDF export class.
 325+// global $smwgNamespace; // The Namespace of exported URIs.
 326+// $smwgNamespace = "http://example.org/id/"; // Will be set automatically if
 327+// nothing is given, but in order to make pretty URIs you will need to set this
 328+// to something nice and adapt your Apache configuration appropriately. This is
 329+// done, e.g., on semanticweb.org, where URIs are of the form
 330+// http://semanticweb.org/id/FOAF
 331+##
 332+
 333+###
 334+# The maximal number that SMW will normally display without using scientific exp
 335+# notation. The deafult is rather large since some users have problems understanding
 336+# exponents. Scineitfic applications may prefer a smaller value for concise display.
 337+##
 338+$smwgMaxNonExpNumber = 1000000000000000;
 339+##
 340+
 341+###
 342+# SMW defers some tasks until after a page was edited by using the MediaWiki
 343+# job queueing system (see http://www.mediawiki.org/wiki/Manual:Job_queue).
 344+# For example, when the type of a property is changed, all affected pages will
 345+# be scheduled for (later) update. If a wiki generates too many jobs in this
 346+# way (Special:Statistics and "showJobs.php" can be used to check that), the
 347+# following setting can be used to disable jobs. Note that this will cause some
 348+# parts of the semantic data to get out of date, so that manual modifications
 349+# or the use of SMW_refreshData.php might be needed.
 350+##
 351+$smwgEnableUpdateJobs = true;
 352+##
 353+
 354+###
 355+# Overwriting the following array, you can define for which namespaces
 356+# the semantic links and annotations are to be evaluated. On other
 357+# pages, annotations can be given but are silently ignored. This is
 358+# useful since, e.g., talk pages usually do not have attributes and
 359+# the like. In fact, is is not obvious what a meaningful attribute of
 360+# a talk page could be. Pages without annotations will also be ignored
 361+# during full RDF export, unless they are referred to from another
 362+# article.
 363+##
 364+$smwgNamespacesWithSemanticLinks = array(
 365+ NS_MAIN => true,
 366+ NS_TALK => false,
 367+ NS_USER => true,
 368+ NS_USER_TALK => false,
 369+ NS_PROJECT => true,
 370+ NS_PROJECT_TALK => false,
 371+ NS_IMAGE => true,
 372+ NS_IMAGE_TALK => false,
 373+ NS_MEDIAWIKI => false,
 374+ NS_MEDIAWIKI_TALK => false,
 375+ NS_TEMPLATE => false,
 376+ NS_TEMPLATE_TALK => false,
 377+ NS_HELP => true,
 378+ NS_HELP_TALK => false,
 379+ NS_CATEGORY => true,
 380+ NS_CATEGORY_TALK => false,
 381+ SMW_NS_PROPERTY => true,
 382+ SMW_NS_PROPERTY_TALK => false,
 383+ SMW_NS_TYPE => true,
 384+ SMW_NS_TYPE_TALK => false,
 385+ SMW_NS_CONCEPT => true,
 386+ SMW_NS_CONCEPT_TALK => false,
 387+);
 388+##
 389+
 390+###
 391+# Properties (usually given as internal ids or DB key versions of property
 392+# titles) that are relevant for declaring the behaviour of a property P on a
 393+# property page in the sense that changing their values requires that all
 394+# pages that use P must be processed again. For example, if _PVAL (allowed
 395+# values) for a property change, then pages must be processed again. This
 396+# setting is not normally changed by users but by extensions that add new
 397+# types that have their own additional declaration properties.
 398+##
 399+$smwgDeclarationProperties = array( '_PVAL', '_LIST' );
 400+##
 401+
 402+// some default settings which usually need no modification
 403+
 404+###
 405+# -- FEATURE IS DISABLED --
 406+# Setting this to true allows to translate all the labels within
 407+# the browser GIVEN that they have interwiki links.
 408+##
 409+$smwgTranslate = false;
 410+
 411+###
 412+# -- FEATURE IS DISABLED --
 413+# If you want to import ontologies, you need to install RAP,
 414+# a free RDF API for PHP, see
 415+# http://www.wiwiss.fu-berlin.de/suhl/bizer/rdfapi/
 416+# The following is the path to your installation of RAP
 417+# (the directory where you extracted the files to) as seen
 418+# from your local filesystem. Note that ontology import is
 419+# highly experimental at the moment, and may not do what you
 420+# extect.
 421+##
 422+// $smwgRAPPath = $smwgIP . 'libs/rdfapi-php';
 423+// $smwgRAPPath = '/another/example/path/rdfapi-php';
 424+##
 425+
 426+###
 427+# If the following is set to true, it is possible to initiate the repairing
 428+# or updating of all wiki data using the interface on Special:SMWAdmin.
 429+##
 430+$smwgAdminRefreshStore = true;
 431+##
Property changes on: trunk/extensions/SemanticMediaWiki/SMW_Settings.php
___________________________________________________________________
Name: svn:eol-style
1432 + native
Index: trunk/extensions/SemanticMediaWiki/SemanticMediaWiki.php
@@ -0,0 +1,18 @@
 2+<?php
 3+
 4+/**
 5+ * Main entry point for the Semantic MediaWiki extension.
 6+ */
 7+
 8+/**
 9+ * This documentation group collects source code files belonging to Semantic
 10+ * MediaWiki.
 11+ *
 12+ * For documenting extensions of SMW, please do not use groups starting with
 13+ * "SMW" but make your own groups instead. Browsing at
 14+ * http://semantic-mediawiki.org/doc/ is assumed to be easier this way.
 15+ *
 16+ * @defgroup SMW Semantic MediaWiki
 17+ */
 18+
 19+require_once dirname( __FILE__ ) . '/SMW_settings.php';
\ No newline at end of file
Property changes on: trunk/extensions/SemanticMediaWiki/SemanticMediaWiki.php
___________________________________________________________________
Name: svn:eol-style
120 + native

Follow-up revisions

RevisionCommit summaryAuthorDate
r66483Follow up to r66478 - fixed upper case letter in filenamejeroendedauw17:52, 15 May 2010

Status & tagging log