m (WikiSysop moved page Wiki Ontology Practices 1.0 to Wiki Ontology 1.0 without leaving a redirect)
Line 1: Line 1:
{| style='width:100%;'  
{| style='width:100%;'  
|style='width:25%'|  
|style='width:25%'|  
|style='widt:30%'|
|style='width:25%'|  
|style='width:25%'|  
|style='width:25%'|
|style='width:14em'|
|style='width:25%'|
|-
|-
  !colspan='3' style='text-align:left;font-size:xx-large;'| <div style='font-size:medium;padding:.2em 1em auto .1em;float:left;margin-right:12px;'>[[File:W3c home.png]]</div><span style='padding-bottom:6px;font-size:small;display:block;'>Best Practice:</span><span style='line-height:110%'>''{{PAGENAME}}''</span><br/><span style='font-size:x-small;color:gray;font-variant:small-caps'>Source: http://www.w3.org/TR/mobile-bp/#d0e630</span>
  !colspan='3' style='text-align:left;font-size:xx-large;'| <div style='font-size:medium;padding:.2em 1em auto .1em;float:left;margin-right:12px;'>[[File:BestPracticesWiki_140x140.gif|100px]]</div><span style='padding-bottom:6px;font-size:small;display:block;'>Best Practice:</span><span style='line-height:110%'>''{{PAGENAME}}''</span><br/><span style='font-size:x-small;color:gray;font-variant:small-caps'>Source: http://www.w3.org/TR/mobile-bp/#d0e630</span>


  !colspan='1' rowspan='3' style='vertical-align:top;background-color:lightyellow'|<div style='font-size:medium;padding:1em;float:left;margin-right:4px;'>[[File:Type - Best Practice.png|50px]]</div><big style='font-family:cursive'>A Best Practice</big><hr/>[[{{FULLPAGENAME}}|{{PAGENAME}}]]
  !colspan='1' rowspan='3' style='vertical-align:top;background-color:lightyellow'|<div style='font-size:medium;padding:1em;float:left;margin-right:4px;'>[[File:Type - Best Practice.png|50px]]</div><big style='font-family:cursive'>A Best Practice</big><hr/>[[{{FULLPAGENAME}}|{{PAGENAME}}]]
Line 27: Line 27:
<br/><small>[[help:Contributor|contributors]]: </small>
<br/><small>[[help:Contributor|contributors]]: </small>
<br/><small>[[help:Editor|editor]]: </small>
<br/><small>[[help:Editor|editor]]: </small>
<br/><small>[[help:Publisher|publisher]]: </small>http://www.bestpracticeswiki.net
<br/><small>[[help:Publisher|publisher]]: </small>[http://www.bestpracticeswiki.net BestPractices]
<br/><small>[[help:Rights|rights]]: </small>.
<br/><small>[[help:Rights|rights]]: </small>.
</div>
</div>
|-
|-
|colspan='3' style='background-color:white;font-size:small;'|<!--
|colspan='3' style='background-color:white;font-size:small;'|<!--
--><span style='display:block;padding:1.5em;font-size:medium'><!--
--><div style='padding:1.5em;font-size:medium'><!--
-->This document specifies Practices underlying the ontology developed for {{SITENAME}}. Principal objectives of the ontology are
-->This document specifies Practices underlying the ontology developed for {{SITENAME}}. Principal objectives of the ontology are
# a consistent set of conventions for users to name properties whose values are associated with wiki pages
# a set of conventions to name properties with values attached to wiki pages
# a Topic Map -specific syntax widget for direct, textual entry of page properties
# a structured query syntax easier for users to learn and use
# a structured query syntax easier for users to learn and use
# user-level Topic Map syntax widgets for direct, textual entry, exploiting ''namespaces'' as the ''names of <u>topic types</u>'' consistent with ISO Topic Maps.
# a coherent class framework for multiple standards covering semantic and socio-economic ontologies
# a coherent framework to stitch together semantic web and socio-economic ontologies
This material is primarily directed at web developers associated with {{SITENAME}} and of any others that use the [[Ontology:Wiki Topic Maps|Wiki Topic Maps Ontology]].  Readers of this document are expected to be familiar with Semantic MediaWiki and its suites of software extensions.<!--
This material is primarily directed at web developers associated with {{SITENAME}} and of any others that use the [[Ontology:Wiki Topic Maps|Wiki Topic Maps Ontology]].  Readers of this document are expected to be familiar with Semantic MediaWiki and its suites of software extensions.<!--
--></span><!--
--></div><!--
--><span style='padding-left:0em;font-variant:small-caps'>in bundle: </span><!--
--><span style='padding-left:0em;font-variant:small-caps'>in bundle: </span><!--
--><!--
--><!--
Line 50: Line 50:
===''"Rules of Thumb"'' Advice===
===''"Rules of Thumb"'' Advice===
*[[Rule:Rule #272|<small style='float:right'>(Rule #272)</small>]]<!--
*[[Rule:Rule #272|<small style='float:right'>(Rule #272)</small>]]<!--
-->[TEXT PROPERTIES] Text property names begin with a "period" followed by a lower case letter; and may have substructure indicating language or one or more numeric facets.
-->[ATTRIBUTE NAMESPACE] Rename the SMW ''Property'' namespace to ''Attribute'' in order to preserve "property" as a quasi-legal term.
*[[Rule:Rule #272|<small style='float:right'>(Rule #272)</small>]]<!--
-->[TEXT PROPERTIES] Identify the names of all text properties by (1) a "period" followed by (2) a lower case letter which may have a suffix to indicate language or facets of a numeric property value.
*[[Rule:Rule #273|<small style='float:right'>(Rule #273)</small>]]<!--
*[[Rule:Rule #273|<small style='float:right'>(Rule #273)</small>]]<!--
-->[NUMERIC FACETS] Numeric facet names begin with a "period" followed by a lower case letter. Facets such as numeric precision, variance and statistical measures are represented by suffixing its name to the name of any "Number" property.
-->[VALUE FACETS] Identify the names of value facets by (1)  a "period" followed by (2) a lower case letter. Include facets for numeric precision, variance and statistical measures.
*[[Rule:Rule #274|<small style='float:right'>(Rule #274)</small>]]<!--
-->[OBJECT PROPERTIES] Identify the names of all object properties by a Capital Letter and do not follow any camel-casing convention.  
*[[Rule:Rule #274|<small style='float:right'>(Rule #274)</small>]]<!--
*[[Rule:Rule #274|<small style='float:right'>(Rule #274)</small>]]<!--
-->[OBJECT PROPERTIES] Object property names begin with a Capital Letter and do not follow any camel-casing convention.  
-->[NUMERIC PROPERTIES] Support RDF-style numeric property names, e.g., "1" and "2", when used as suffixes to either a text or an object property name.
*[[Rule:Rule #261|<small style='float:right'>(Rule #261)</small>]]<!--
*[[Rule:Rule #261|<small style='float:right'>(Rule #261)</small>]]<!--
-->[PROPERTY NAMES] Property names may not contain any special characters other than ''en-dash'' and ''hash'' characters.
-->[PROPERTY NAMES] Disallow from property names all special characters other than ''en-dash'' and ''hash'' characters.
*[[Rule:Rule #109|<small style='float:right'>(Rule #109)</small>]]<!--
*[[Rule:Rule #109|<small style='float:right'>(Rule #109)</small>]]<!--
-->[ISO PROPERTIES] International Standards Organization (ISO) codes for currencies & languages are required names for monetary and text/string properties; for the property name, each code is preceded by a period.
-->[ISO PROPERTIES] Support all International Standards Organization (ISO) codes for currencies & languages as property names for monetary and text/string data.
*[[Rule:Rule #280|<small style='float:right'>(Rule #280)</small>]]<!--
*[[Rule:Rule #280|<small style='float:right'>(Rule #280)</small>]]<!--
-->[SI PROPERTIES] Systeme Internationale (SI) abbreviations for numeric quantities are required names in the ontology.
-->[SI PROPERTIES] Support all Systeme Internationale (SI) abbreviations for types of numeric quantities as property names.
*[[Rule:Rule #282|<small style='float:right'>(Rule #282)</small>]]<!--
*[[Rule:Rule #282|<small style='float:right'>(Rule #282)</small>]]<!--
-->[BALANCE] Take into account the trade-off between having too many links on a page and asking the user to follow too many links to reach what they are looking for.
-->[WIKI NAMESPACES] Require a wiki page's namespaces to be the primary mechanism for communicating the ''type of topic'' that the page represents.
*[[Rule:Rule #283|<small style='float:right'>(Rule #283)</small>]]<!--
-->[WIKI PAGENAMES] Assume that the name of a page in a wiki is the topic of the page, and a topic of the wiki.
*[[Rule:Rule #283|<small style='float:right'>(Rule #283)</small>]]<!--
*[[Rule:Rule #283|<small style='float:right'>(Rule #283)</small>]]<!--
-->[NAVIGATION] Provide consistent navigation mechanisms.
-->[WIKI REDIRECTS] Consider REDIRECTs to be alternate names, or aliases, in the Topic Map sense.
*[[Rule:Rule 301|<small style='float:right'>(Rule 301)</small>]]<!--
-->[DUBLIN CORE] Adopt & intimately integrate all Dublin Core properties for general provenance purposes.
*[[Rule:Rule 301|<small style='float:right'>(Rule 301)</small>]]<!--
-->[XML SCHEMA] Support all XML Schema datatypes as property names for low-level data transmissions or queries.
*[[Rule:Rule 301|<small style='float:right'>(Rule 301)</small>]]<!--
-->[RDF] Support all RDF properties and classes for RDF-level data transmissions and RDF-level queries.
*[[Rule:Rule 301|<small style='float:right'>(Rule 301)</small>]]<!--
*[[Rule:Rule 301|<small style='float:right'>(Rule 301)</small>]]<!--
-->[ACCESS_KEYS] Assign access keys to links in navigational menus and frequently accessed functionality.
-->[RDF SCHEMA] Support all RDF Schema properties and classes for data exchanges and queries.
 
*[[Rule:Rule 301|<small style='float:right'>(Rule 301)</small>]]<!--
*[[Rule:Rule 301|<small style='float:right'>(Rule 301)</small>]]<!--
-->[LINK_TARGET_ID] Clearly identify the target of each link.
-->[LINK_TARGET_ID] Clearly identify the target of each link.

Revision as of 23:18, 26 March 2013

BestPracticesWiki 140x140.gif
Best Practice:Wiki Ontology 1.0
Source: http://www.w3.org/TR/mobile-bp/#d0e630
Type - Best Practice.png
A Best Practice
Wiki Ontology 1.0
This document specifies Practices underlying the ontology developed for Best Practices Wiki. Principal objectives of the ontology are
  1. a set of conventions to name properties with values attached to wiki pages
  2. a Topic Map -specific syntax widget for direct, textual entry of page properties
  3. a structured query syntax easier for users to learn and use
  4. a coherent class framework for multiple standards covering semantic and socio-economic ontologies
This material is primarily directed at web developers associated with Best Practices Wiki and of any others that use the Wiki Topic Maps Ontology. Readers of this document are expected to be familiar with Semantic MediaWiki and its suites of software extensions.
in bundle: narrower than: Ontologiesbroader than:

"Rules of Thumb" Advice

  • (Rule #272)[ATTRIBUTE NAMESPACE] Rename the SMW Property namespace to Attribute in order to preserve "property" as a quasi-legal term.
  • (Rule #272)[TEXT PROPERTIES] Identify the names of all text properties by (1) a "period" followed by (2) a lower case letter which may have a suffix to indicate language or facets of a numeric property value.
  • (Rule #273)[VALUE FACETS] Identify the names of value facets by (1) a "period" followed by (2) a lower case letter. Include facets for numeric precision, variance and statistical measures.
  • (Rule #274)[OBJECT PROPERTIES] Identify the names of all object properties by a Capital Letter and do not follow any camel-casing convention.
  • (Rule #274)[NUMERIC PROPERTIES] Support RDF-style numeric property names, e.g., "1" and "2", when used as suffixes to either a text or an object property name.
  • (Rule #261)[PROPERTY NAMES] Disallow from property names all special characters other than en-dash and hash characters.
  • (Rule #109)[ISO PROPERTIES] Support all International Standards Organization (ISO) codes for currencies & languages as property names for monetary and text/string data.
  • (Rule #280)[SI PROPERTIES] Support all Systeme Internationale (SI) abbreviations for types of numeric quantities as property names.
  • (Rule #282)[WIKI NAMESPACES] Require a wiki page's namespaces to be the primary mechanism for communicating the type of topic that the page represents.
  • (Rule #283)[WIKI PAGENAMES] Assume that the name of a page in a wiki is the topic of the page, and a topic of the wiki.
  • (Rule #283)[WIKI REDIRECTS] Consider REDIRECTs to be alternate names, or aliases, in the Topic Map sense.
  • (Rule 301)[DUBLIN CORE] Adopt & intimately integrate all Dublin Core properties for general provenance purposes.
  • (Rule 301)[XML SCHEMA] Support all XML Schema datatypes as property names for low-level data transmissions or queries.
  • (Rule 301)[RDF] Support all RDF properties and classes for RDF-level data transmissions and RDF-level queries.
  • (Rule 301)[RDF SCHEMA] Support all RDF Schema properties and classes for data exchanges and queries.
  • (Rule 301)[LINK_TARGET_ID] Clearly identify the target of each link.
  • (Rule 301)[LINK_TARGET_FORMAT] Note the target file's format unless you know the device supports it.
  • (Rule 301)[IMAGE_MAPS] Do not use image maps unless you know the device supports them effectively.
  • (Rule 301)[POP_UPS] Do not cause pop-ups or other windows to appear and do not change the current window without informing the user.
  • (Rule 301)[AUTO_REFRESH] Do not create periodically auto-refreshing pages, unless you have informed the user and provided a means of stopping it.
  • (Rule 301)[REDIRECTION] Do not use markup to redirect pages automatically. Instead, configure the server to perform redirects by means of HTTP 3xx codes.
  • (Rule 301)[EXTERNAL_RESOURCES] Keep the number of externally linked resources to a minimum.
  • (Rule 301)[SUITABLE] Ensure that content is suitable for use in a mobile context.
  • more...

{{#formlink:form=Advice|link text=Add another "Rule of Thumb" (from the same source only)|link type=|query string=|query string parameters|target=|tooltip=|popup|new window}}

Media links

{{#ask:Link:+|format=list|default=No media items found
}} {{#formlink:form=Link|link text=Add a link|link type=button|query string=|query string parameters|target=|tooltip=|popup|new window}}

See also

{{#ask:Relation:+|format=list|default=No other items found
}} {{#formlink:form=Relation|link text=Add a link|link type=button|query string=|query string parameters|target=|tooltip=|popup|new window}}

Community Contacts

{{#ask:Advice:+|format=list|default=No contacts found
}}


{{#formlink:form=Expert|link text=Be a go-to expert
about this practice|link type=|query string=|query string parameters|target=|tooltip=|popup|new window}}
{{#formlink:form=Practitioner|link text=Do you or your organization use this best practice ?|link type=|query string=|query string parameters|target=|tooltip=|popup|new window}}

{{#formlink:form=Search|link text=Search for more
Best Practices
like this one
|link type=button|query string=|query string parameters|target=|tooltip=|popup|new window}}

Group Blog

{{#formlink:form=Blog|link text=Start a group blog
for this best practice
|link type=button|query string=|query string parameters|target=|tooltip=|popup|new window}}

Snap Poll

{{#formlink:form=Practitioner|link text=Do you or your organization use this best practice ?|link type=|query string=|query string parameters|target=|tooltip=|popup|new window}} {{#formlink:form=Poll|link text=Create a poll|link type=button|query string=|query string parameters|target=|tooltip=|popup|new window}}

Case studies, datasets & surveys

{{#ask:Study:+|format=list|default=No case studies found
}} {{#formlink:form=Study|link text=Add a case study|link type=button|query string=|query string parameters|target=|tooltip=|popup|new window}}


{{#ask:Dataset:+|format=list|default=No open data datasets found
}}

{{#formlink:form=Dataset|link text=Add a dataset|link type=button|query string=|query string parameters|target=|tooltip=|popup|new window}}


{{#ask:Survey:+|format=list|default=No surveys found}}

{{#formlink:form=Survey|link text=Add a survey|link type=button|query string=|query string parameters|target=|tooltip=|popup|new window}}

Expert Opinions

{{#ask:Opinion:+|format=list|default=No opinions found
}}
nopreview

{{#set:

Article has average rating={{#averagerating:}}

}} {{#showcommentform:}}

?Has comment person ?Has comment date ?Has comment text ?Has comment rating ?Belongs to comment ?Comment was deleted#true,false ?Has comment editor ?Modification date ?Has attached article format=template template=CommentResult sort=Has comment date order=asc link=none limit=100

}}


{{#formlink:form=Expert|link text=Add an expert opinion about this best practice|link type=|query string=|query string parameters|target=|tooltip=|popup|new window}}

{{#css: h1#firstHeading {display:none} }}