SMW notes: Difference between revisions

165 bytes added ,  26 August 2009
Line 1: Line 1:
/* CSS placed here will be applied to all skins */
http://smwforum.ontoprise.com/smwforum/images/a/ad/Manual_SMW.pdf
/* @import "/css/basic.css"; */
@import "/css/galleriffic-3.css";


.tpllabel {
http://smw.referata.com/wiki/Special:BrowseData/Tips
        float: left;
        width: 15%;
}


.tplvalue {
(from mailing list)
        float: right;
        width: 83%;
}


== Data design ==


h1.firstHeading {
- Create a top category for Semantic Classes. I called mine 'Categories'.
  display: none;
It holds only categories used to define a 'Is-a' relationship. Doing so has
}
at least two benefits : 1- You can do a query on your core content by
restricting it to the 'Categories' level. 2- You can define other
categories outside of that structure for whatever your system needs.


.cleared {
http://smwforum.ontoprise.com/smwforum/index.php/Example:How_to_realize_a_range_constraint_for_a_property
  clear: both;
}


td.month_name {
== Discussion ==
  font-size: large;
}


#p-logo a { background: url(/images/smacw1.png) 35% 50% no-repeat !important; }
Categories can be hierarchical; properties can't (yet).


.noticebox {
 
  -moz-border-radius: 1em;
== MW tricks ==
  -webkit-border-radius: 1em;
 
   background: #eee;
If you want to clear out old pages you can delete them and use
  padding: 5px;
deleteArchivedRevisions.php to erase the deleted revisions from the
}
database.
 
=== Variables ===
 
You can make use of the VariablesExtension [1] and store the query (or its
result? I'd like to know which one, but in the end it doesn't really matter) in
a variable, which is helpful when you need the same query multiple times within
a page. It looks like this:
 
{{ #vardefine: some_variable_name | {{#show:{{PAGENAME}}| ?propertyname}} }}
(silent) or
  {{ #vardefineecho: some_variable_name | {{#show:{{PAGENAME}}| ?propertyname}} }} (with output)
 
Further down in the page you can write
 
  {{ #var: some_variable_name }}
 
=== Specific searches ===
 
  <nowiki>
  <inputbox>
  type=search
  width=30
  namespaces=Help**,Wikipedia**,Template**
  searchbuttonlabel=Search help pages
  bgcolor=#cee0f2
  break=no
  </inputbox>
  </nowiki>
 
=== Hiding set data ===
 
   <nowiki>[[propertyA::{{{propertyA|}}}|]]</nowiki>
 
By adding the | after the enclosing }}}, the property value will not show.
 
For multi value properties:
 
  <nowiki>{{#arraymap:{{{Eating disorders behaviors|}}}|,|x|[[Eating disorders         
> behaviors::x|]]}}</nowiki>
 
== Misc ==
 
=== Enable links in property values ===
 
$smwgLinksInValues = true;
 
=== Must add namespaces to config ===
 
Otherwise they won't have semantic properties.
 
$smwgNamespacesWithSemanticLinks array
 
== Media ==
 
Neat talk on MW, with refs to SMW: http://www.youtube.com/watch?v=Ukytqe9pwDM
 
[[Semantics]]