deviceVendor is /device/deviceName/deviceVendor deviceModel is /device/deviceName/deviceModel deviceVersion does not yet have a definition screenHeight you have a choice here. For the hardware values you could chose: /device/deviceHardware/display[0]/totalDisplayPixelsY/pixelCount /device/deviceHardware/display[0]/totalDisplayPixelsY/maximumPixelCount /device/deviceHardware/display[0]/totalDisplayPixelsY/minimumPixelCount /device/deviceHardware/display[0]/totalDisplayPixelsY/defaultPixelCount for the browser usable values you could chose: /device/deviceSoftware/webBrowserSupport/activeWebBrowser/browserUsableDisplayPixelsY/maximumPixelCount /device/deviceSoftware/webBrowserSupport/activeWebBrowser/browserUsableDisplayPixelsY/minimumPixelCount /device/deviceSoftware/webBrowserSupport/activeWebBrowser/browserUsableDisplayPixelsY/defaultPixelCount screenWidth you have a choice here: For the hardware values you could chose: /device/deviceHardware/display[0]/totalDisplayPixelsX/pixelCount /device/deviceHardware/display[0]/totalDisplayPixelsX/maximumPixelCount /device/deviceHardware/display[0]/totalDisplayPixelsX/defaultPixelCount for the browser usable values you could chose: /device/deviceSoftware/webBrowserSupport/activeWebBrowser/browserUsableDisplayPixelsX/maximumPixelCount /device/deviceSoftware/webBrowserSupport/activeWebBrowser/browserUsableDisplayPixelsX/minimumPixelCount /device/deviceSoftware/webBrowserSupport/activeWebBrowser/browserUsableDisplayPixelsX/defaultPixelCount screenColorDepth is /device/deviceHardware/display[0]/displayBitsPerPixel inputDevices is made up of a couple of ontology entries /device/deviceHardware/tactileInputType[0]/keyboardTypeName defines types such as: Virtual Keyboard (touch, on screen) Numeric Keypad Phone Keypad Full Keyboard Buttons Currently there is no equivalent of this for pointing input devices. There is, however, a definition of the resolution of the pointing device. /device/deviceHardware/pointingResolution/pointingResolutionName defines names such as Line Character Pixel This is an omission and needs to be corrected before FPWD of the ontology. In addition to the values in the vocabulary, other common options present themselves, such as the classic '4 way navigation' control often found on Nokia phones (and my DAB digital radio,as it happens!). markupSupport is a combination of: /device/deviceSoftware/webBrowserSupport/activeWebBrowser/pageMarkupSupport/preferredPageMarkupLanguage/pageMarkupVersion /device/deviceSoftware/webBrowserSupport/activeWebBrowser/pageMarkupSupport/preferredPageMarkupLanguage/pageMarkupName stylesheetSupport is not in the ontology currently. This needs to be corrected before FPWD of the ontology. It will be similar to the way markupSupport is represented in the ontology. imageFormatSupport is not in the ontology currently. The ImageSupport class needs to be linked to the browser. inputModeSupport - not in ontology currently. Isn't this XHTML specific? Isn't this something to do with the way that XHTML support is implemented in the browser? cookieSupport - not in ontology currently. Needs to be added as browser property