Changes

This guide lists and describes all Semantic Wiki semantic wiki categories used on this site. We differentiate between Semantic semantic annotations based on the type of the device or technology they are used to describedescribing.

The semantic Semantic wiki properties are almost exclusively used in [[Infobox_(HMDs)|Infoboxes]] but they can also be used throughout the text of the article. For an in-depth guide on the semantic properties and semantic wiki in general, please see the [https://www.semantic-mediawiki.org/wiki/Help:User_manual Semantic Wiki User Manual].

== Head Mounted Displays category semantic properties Category Semantic Properties ==

This is a list of properties used on pages categorized categorised as [[Smartglasses]] or [[Virtual Reality Devices]].

! Property name Name !! Property value Value (example value)

| [[Property:Announced in|Announced in]] || The date when the device was announced. , (e.g. , 9 September 2013).

| [[Property:Controls are|Controls are]] || Available means of controlling the device. , (e.g. , inertial, peripherals, positional tracking).

| [[Property:Costs|Costs]] || The cost of the device in USD. (e.g. , 400). For this value, use only the number. The USD part will be added automatically.

| [[Property:Developed by|Developed by]] || The developer and/or/and manufacturer of the device. , (e.g. , Oculus VR, Facebook, Inc.).

| [[Property:Has resolution of|Has resolution of]] || The resolution of the device's display in pixels. Combined resolution in case of binocular displays. The ending 'pixels' will be added automatically. , (e.g. , 2560x1440).

| [[Property:Is categorized as|Is categorized as]] || The type of technology we categorize the device as. , (e.g. , Smartglasses).

| [[Property:Operating system is|Operating system is]] || The operating system the device is using or can be used with. , (e.g. , Microsoft Windows).

| [[Property:Released for consumers|Released for consumers]] || The date the device was released to general consumers. Can be used to indicate a rumoured or announced future release date. (e.g. , January 2016).

| [[Property:Released for developers in|Released for developers in]] || The date the device was made available for developers but it has not entered the general market yet. May indicate possible developer release in the future. , (e.g. May 2015).

| [[Property:Weights|Weights]] || The weight of the device in grams. The unit 'g' will be added automatically, (e.g. (, 400).

Click on any property to learn more about it's its semantic Type and usage.

== How to use semantic annotations Use Semantic Annotations in text Text ==

While the creation of new semantic properties is not forbidden, it is highly discouraged to do so without discussing it first with other authors and administrators in order to avoid creating too much more or less of the same semantic categories that serve no real purpose other but confusing than to confuse anyone who would want to browse the wiki. If you have an idea to create a new semantic category, please discuss it first!

To use a semantic property in the text outside of the infobox, you type <code><nowiki>[[property_name::value]]</nowiki></code> anywhere you want to assign a property to the <code>value</code>. For example, you are writing about the history of a virtual reality device. You want to semantically indicate, that the year the device was first manufactured is the year of was 2015. You take a look at the raw text, find the number of the year , and from just <code>2015</code> you change it to <code><nowiki>[[Manufactured in::2015]]</nowiki></code>. The text will remain the same, but you successfully assigned the year 2015 a semantic property , and the device is now searchable by the year it was manufactured in.

When you are creating a new semantic property, try to make it form a sentence. This is the strength of the semantic search, because you can now search and filter the properties by using natural language. Using the above example, you should type <code>Manufactured in:</code> instead of something like <code>Manufacture date:</code>.

== Dealing with multiple values Multiple Values ==

When using semantic properties, be it in the infoboxes or the body of the article itself, you will inevitably encounter a problem - : what to do when I have multiple values of the same property? Thankfully, the solution is not complicated. Consider a the following case example case. You are writing about a device that features three sensors: accelerometer, thermometer, and barometer. And you You want all these three categories to be recognized recognised by the semantic wiki. The correct way is to use the property <code>Has sensors</code> multiple times! Compare the two lines below:

<div style="background-color: #FFCCCC; border: 1px solid #FFB2B2; padding: 10px; margin-bottom: 1em;">'''The wrong way:''' <code><nowiki>[[Has sensors::accelerometer, thermometer, barometer]]</nowiki></code> . This will not work correctly because the system will consider this to be just one sensor that is called accelerometer, thermometer, barometer.</div>

<div style="background-color: #E9FFE6; border: 1px solid #CEF2E0; padding: 10px;">'''The correct way:''' <code><nowiki>[[Has sensors::accelerometer]], [[Has sensors::thermometer]], [[Has sensors::barometer]]</nowiki></code> . This time around we used the property <code>Has sensors</code> multiple times, individually for each of the sensors. The wiki will now understand that the device you are writing about features three different sensors. Also , notice how the <code>,</code> is outside the semantic wiki tags. This is so the semantic values have only the name of the sensor, but not the comma between them , as the comma is not an actual part of the name.</div>

As you can see, you can use all of the properties multiple times without any problems ; but , before you do so, think about whether making multiple properties like this one actually make makes sense. Making multiple properties for multiple different sensors is logical and encouraged, but creating four different properties for the announcement date is nonsensical because there can be only one announcement date (unless there are some very special circumstances which should be explicitly mentioned in the article).