Warning:
This wiki has been archived and is now read-only.
CoreVocabularySubmissions
Properties submitted to the Core Vocabulary
These properties have been submitted via the public process for consideration by the DDWG as part of the work to create a Core Vocabulary for the Device Description Repository.
- Discuss these submissions on the dedicated public mailing list. public-ddr-vocab@w3.org (Join list)
- View the most recent version of the CoreVocabulary
- View ALL the submissions received, CoreVocabularyAllSubmissions
Properties of the DDWG Core Vocabulary
There is a need to know some of the hardware features and functionalities in order to provide a good browsing experience.
Display Properties
Screen Width
Description: The total number of addressable pixels in the horizontal direction of a rectangular display when held in its default orientation. The property does not apply to screen shapes that are not rectangular or square.
Measurement: The pixels are counted from the top left corner to the top right corner, and the result expressed as an integer whose units are 'pixels'.
Type: Non-negative integer.
Justification: Needed to fit/crop images, text or other width-adaptable content to the screen. Especially useful for LTR and RTL content, where vertical scrolling would be the norm but horizontal scrolling is not desirable. Identified as an important property by the DDWG in its Top N finding. Present in UAProf. Present (and used) in existing adaptation solutions.
Property Name: screenWidth
Related properties: screenHeight
Ontology Name: <none>
| Status: CORE |
Screen Height
Description: The total number of addressable pixels in the vertical direction of a rectangular display when held in its default orientation. The property does not apply to screen shapes that are not rectangular or square.
Measurement: The pixels are counted from the top left corner to the bottom left corner, and the result expressed as an integer whose units are 'pixels'.
Type: Non-negative integer.
Justification: Needed to fit/crop images, text or other height-adaptable content to the screen. Especially useful for vertical content. Suggested that it may be an important property by the DDWG in its Top N finding. Present in UAProf. Present (and used) in existing adaptation solutions. Needed if the screen orientation is rotated 90 degrees, in which case this property would represent the width of the rotated screen.
Property Name: screenHeight
Related properties: screenWidth
Ontology Name: <none>
| Status: CORE |
Screen Color Depth
Description: Screen color depth
Measurement: The value should be defined based on the bits usable for color definition.
Type: Integer positive number
Justification: If you are making any image or video transcoding it is important to know the maximum colors addressable by the screen. Measuring in bits should make it easier for programmatic conversions.
Property Name: screenColorDepth
Related properties: <none>
Ontology Name: <none>
| Status: CORE |
Usable Screen Height
Description: The total number of addressable pixels in the vertical direction in the current orientation of the device left after any reduction of the number resulting from manipulations of the current delivery context - e.g. browser chrome, operator transcoding/gateway etc.
Measurement: The result is derived from knowing the adjustments that the various components of the delivery context apply to the known underlying actual dimention provided by the underlying hardware.
Type: Non-negative integer.
Justification: Used in conjunction with the screenHeight property - if you don't know how much space is taken up by components of the delivery context you can't size images and other things properly.
Property Name: usableScreenHeight
Related properties: screenHeight
Ontology Name: <none>
| Status: Undecided |
Usable Screen Width
Description: The total number of addressable pixels in the horizontal direction in the current orientation of the device left after any reduction of the number resulting from manipulations of the current delivery context - e.g. browser chrome, operator transcoding/gateway etc.
Measurement: The result is derived from knowing the adjustments that the various components of the delivery context apply to the known underlying actual dimention provided by the underlying hardware.
Type: Non-negative integer.
Justification: Used in conjunction with the screenWidth property - if you don't know how much space is taken up by components of the delivery context you can't size images and other things properly.
Property Name: usableScreenWidth
Related properties: screenWidth
Ontology Name: <none>
| Status: Undecided |
Display Orientation
Description: Describes whether the display is wider than it is high, or higher than it is wide, or an indication that it is square. The property does not apply to screen shapes that are not rectangular or square. This property will describe the orientation of the display in its most common or default usage. If supported by the appropriate technology, this property may indicate the current orientation if the device is capable of reporting it. This information can be used to modify the interpretation of properties which describe the display width and height (in its default orientation).
Measurement: The display orientation is a single value from an enumerated set of values: "portrait", "landscape", "square" or "undefined". The value "portrait" means that the orientation is such that the display's height is greater than its width. The value "landscape" means that the orientation is such that the display's width is greater than its height.. The value "square" means that display's height and width are the same. The value "undefined" may be used if the display has no meaningful orientation in these terms, for example if the display is not a square or rectangle.
Type: String
Justification: This is a property that appears to be easily derived from display width and height. However there will be scenarios where a page author wishes to make decisions about page design or layout based purely one the orientation of the display rather than its actual dimensions and the presence of this property will reduce the burden on the page author. In a vocabulary which includes values that can be updated in relation to a specific delivery context, display orientation is a property that could change value dynamically, for example if a device or its display is rotated 90 degrees. In such a case, the display orientation may be compared with the ratio of width and height, and the result, used to transpose the interpretation of the display width and display height properties.
Property Name: displayOrientation
Related properties: screenWidth and screenHeight
Ontology Name: <none>
| Status: Undecided |
Alternative Orientation
Description: Defines if the device is capable of displaying content using an orientation different from the default one.
Measurement: Some mobile devices allow for a default orientation such as portrait, but also allow the user to change and use the device in landscape orientation.
Type: Boolean, true means the device has this option.
Justification: The screen width and height sizes are referred to the default orientation and those can also be used to deduce which is the current orientation. It is also important to know if the user is able to change this parameter and thus exchanging the effective screen width and height.
Property Name: supportsAlternativeDisplayOrientation
Related properties: displayOrientation
Ontology Name: <none>
| Status: Undecided |
Content Types and Mark-ups
Mark-up
Description: Set of values of mark-ups the browser can render. Each value will represent one markup language representing a Web page (or fragment thereof) that can be rendered by the device Web browser(s)
Measurement: See individual values, normally conformance to the minimum compliance requirements. More detail may appear in other specific properties such as tableSupport.
Type: set of values, returned as an unordered Array of the supported mark-up names.
Justification: In order to provide the appropriate mark-up when serving a web page, it is required that the server knows the supported mark-ups. Accept headers are often not accurate enough and can be modified by proxies in-between.
Property Name: markup
Related properties: <none>
Ontology Name: <none>
| Status: CORE |
possible values
| Name | Description | Measurement | Justification | Related properties | Ontology Name | status | |
| xhtmlBasic10 | XHTML Basic 1.0 | conformance to the requirements | often the Accept headers are not enough detailed to go down to a specific mark-up version, XHTML Basic is the basis for many more complex mark-ups | <none> | <none> | Undecided | |
| xhtmlMp10 | XHTML-MP 1.0 | conformance to the requirements | many mobile browsers are based on WAP standards, XHTML-MP is part of WAP 2 | <none> | <none> | Undecided | |
| xhtmlBasic11 | XHTML Basic 1.1 | conformance to the requirements | XHTML 1.1 is the evolution of 1.0, many browsers already support it. Next versions of WAP 2 are based on this too | markup.xhtmlBasic10 | <none> | Undecided |
XHTML Basic 1.0 MIME Type
Description: Describes which is the appropriate MIME Type to serve XHTML Basic 1.0 pages.
Measurement: Verify that the mark-up is rendered appropriately when served with this MIME Type. The MIME Type must also be present in the Accept header sent by the browser.
Type: String.
Justification: In order to provide the appropriate mark-up when serving a web page, it is required that the server knows the supported mark-ups. Accept headers are often not accurate enough and can be modified by proxies in-between.
Property Name: xhtmlBasic10MimeType
Related properties: markup.xhtmlBasic10
Ontology Name: <none>
| Status: Undecided |
XHTML-MP 1.0 MIME Type
Description: Describes which is the appropriate MIME Type to serve XHTML-MP 1.0 pages. Measurement: Verify that the mark-up is rendered appropriately when served with this MIME Type. The MIME Type must also be present in the Accept header sent by the browser.
Type: String.
Justification: In order to provide the appropriate mark-up when serving a web page, it is required that the server knows the supported mark-ups. Accept headers are often not accurate enough and can be modified by proxies in-between.
Property Name: xhtmlMp10MimeType
Related properties: markup.xhtmlMp10
Ontology Name: <none>
| Status: Undecided |
XHTML Basic 1.1 MIME Type
Description: Describes which is the appropriate MIME Type to serve XHTML Basic 1.1 pages.
Measurement: Verify that the mark-up is rendered appropriately when served with this MIME Type. The MIME Type must also be present in the Accept header sent by the browser.
Type: String.
Justification: In order to provide the appropriate mark-up when serving a web page, it is required that the server knows the supported mark-ups. Accept headers are often not accurate enough and can be modified by proxies in-between.
Property Name: xhtmlBasic11MimeType
Related properties: markup.xhtmlBasic11
Ontology Name: <none>
| Status: Undecided |
Style Sheets
Description: Set of values of Style sheet recommendations the browser can render. Each value will represent one style sheet recommendation
Measurement: See individual values, normally conformance to the minimum compliance requirements. More detail may appear in other specific properties such as tableSupport.
Type: set of values, returned as an unordered Array of the supported style sheet names.
Justification: Style sheets are needed to define how the page should be layed out, positions and colors.
Property Name: styleSheet
Related properties: markup
Ontology Name: <none>
| Status: CORE |
possible values
| Name | Description | Measurement | Justification | Related properties | Ontology Name | status | |
| css10 | CSS 1.0 | conformance to the requirements | often the Accept headers are not enough detailed to go down to a specific mark-up version, CSS 1.0 is the first defined and most widely supported | markup.xhtmlBasic10 | <none> | Undecided | |
| wcss10 | WCSS 1.0 | conformance to the requirements | part WAP 2 specification | markup.xhtmlMp10 | <none> | Undecided | |
| css21 | CSS 2.1 | The BPWG knows that full and exact support is rarely achieved and believes that DDWG should consider what is meant by support, if and when it should be possible to assert that a markup is supported even if not all the elements and attributes are completely supported. DDWG should also consider make these findings available to the public in association with the property definitions. | CSS 2.1 support is important to know if and how it can be used to define the page layout | styleSheet.css10 | <none> | Undecided |
Image Formats
Description: Set of values of image formats the browser can render in-line. Each value will represent one image format.
Measurement: See individual values, normally conformance to the minimum compliance requirements. More detail may appear in other specific properties such as transparency, animation, etc.
Type: set of values, returned as an unordered Array of the supported image format names.
Justification: Images are the first step to make content more compelling. Accept headers are often not accurate enough and can be modified by proxies in-between.
Property Name: imageFormat
Related properties: <none>
Ontology Name: <none>
| Status: CORE |
possible values
| Name | Description | Measurement | Justification | Related properties | Ontology Name | status | |
| gif87 | display a GIF87 image in a mobile web page | correctly load and display a GIF87 image | GIF is the most widely used image format | <none> | <none> | Undecided | |
| gif89a | display a GIF89a image in a mobile web page | The browser shows the image appropriately in a web page | GIF89a adds animation and other evolutions to the basic GIF specification | imageFormat.gif87 | <none> | Undecided | |
| jpg | display an image created following the JPEG standard in a web page | The browser shows the image appropriately in a web page | JPEG is one of the most common formats | <none> | <none> | Undecided | |
| png | display an image created following the PNG standard in a web page | The browser shows the image appropriately in a web page | PNG is one of the most common formats and is an open standard | <none> | <none> | Undecided |
GIF87 MIME Type
Description: The MIME Type for GIF87 images
Measurement: The browser shows the image appropriately in a web page.
Type: String
Justification: Images need to be served with an appropriate MIME Type.
Property Name: Gif87MimeType
Related properties: supportsGif87
Ontology Name: <none>
| Status: Undecided |
GIF89a MIME Type
Description: The MIME Type for GIF89a images
Measurement: The browser shows the image appropriately in a web page.
Type: String
Justification: Images need to be served with an appropriate MIME Type.
Property Name: Gif89aMimeType
Related properties: supportsGif89a
Ontology Name: <none>
| Status: Undecided |
JPEG MIME Type
Description: The MIME Type for JPEG images
Measurement: The browser shows the image appropriately in a web page.
Type: String
Justification: Images need to be served with an appropriate MIME Type.
Property Name: JpegMimeType
Related properties: supportsJpeg
Ontology Name: <none>
| Status: Undecided |
PNG MIME Type
Description: The MIME Type for PNG images
Measurement: The browser shows the image appropriately in a web page.
Type: String
Justification: Images need to be served with an appropriate MIME Type.
Property Name: PngMimeType
Related properties: supportsPng
Ontology Name: <none>
| Status: Undecided |
ECMAScript
Description: Some browsers are capable of supporting ECMAScript. Scripting can provide some advanced functionalities on the client-side.
Measurement: Verify that script is interpreted appropriately when served.
Type: Boolean, true if supported
Justification: Scripting on the client-side can provide some very efficient tools and especially on the mobile context allow for easier navigation, smooth form filling and other tasks that would aid navigation. This would be needed for adaptation softwares to know if the browser is capable of using scripting or if other navigation paths should be used as an alternative.
Property Name: supportsEcmaScript
Related properties: <none>
Ontology Name: <none>
| Status: Undecided |
UTF-8
Description: Browser support of UTF-8 character encoding.
Measurement: Support should be tested with a number of random character encodings if not with the full list of possible valid encodings.
Type: Boolean, true if supported.
Justification: UTF-8 is a widely supported character encoding, it is important to know if and when it is supported to be able to apply the appropriate encoding.
Property Name: supportsUtf8
Related properties: <none>
Ontology Name: <none>
| Status: Undecided |
Page Rendering
Memory limit for page rendering
Description: Memory limit for page rendering
Measurement: Limit should be tested with a page composed of a supported markup, at least 1 external CSS if supported and 1 or more media files if supported.
Type: Float number representing the KB of usable memory
Justification: It is important to know the memory limit both for page contents and media files that can be referenced.
Property Name: pageContentMemoryLimit
Related properties: <none>
Ontology Name: <none>
| Status: Undecided |
Table support
Description: Support for table element and its sub-elements or an alternative composition to achieve the same result.
Measurement: The BPWG knows that the measurement of the exact support can be hardly defines and suggests that DDWG investigate the issue and consider make these findings available to the public in association with the property definitions
Type: Boolean, true if supported
Justification: Tables are not a suggested practice for layout purposes unless really needed, nevertheless it is common practice to use it for specific cases or sometimes to overcome layout issues of specific browsers.
Property Name: supportsXhtmlTable
Related properties: supportsXhtmlBasic10, supportsXhtmlMp10
Ontology Name: <none>
| Status: Undecided |
Italic
Description: Italic is a typical font effect that help authors.
Measurement: The browser is capable to show text using the italic style effect
Type: Boolean, true if supported
Justification: Mobile devices sometimes don't support any style face or syle effects other than the default one. It would be useful for authors to know if a syle effect is supported or not and in case be able to use alternative methods to achieve a similar effect.
Property Name: supportsItalic
Related properties: supportsXhtmlBasic10, supportsXhtmlMp10
Ontology Name: <none>
| Status: Undecided |
Bold
Description: Bold is a typical font effect that help authors.
Measurement: The browser is capable to show text using the bold style effect
Type: Boolean, true if supported
Justification: Mobile devices sometimes don't support any style face or style effects other than the default one. It would be useful for authors to know if a style effect is supported or not and in case be able to use alternative methods to achieve a similar effect.
Property Name: supportsBold
Related properties: supportsXhtmlBasic10, supportsXhtmlMp10
Ontology Name: <none>
| Status: Undecided |
Access Keys
Description: Support of accesskeys as defined by the markup recommendation.
Measurement: If accesskey is supported, the user should be able to click on that key and automatically follow the associated link.
Type: Boolean, true if supported
Justification: Accesskeys are an important part of accessibility in general. Specifically to the mobile it's a way to aid navigation in general and to speed up some repetitive selections.
Property Name: supportsXhtmlAccessKey
Related properties: supportsXhtmlBasic10, supportsXhtmlMp10
Ontology Name: <none>
| Status: Undecided |
Show Access Keys
Description: This property should describe if the browser automatically shows a key associated with an anchor via an accesskey.
Measurement: Check if accesskey is automatically printed next to the anchor.
Type: Boolean, true if supported
Justification: If the associated key is automatically displayed, the page designer should not print the same number again. This is a common issue with some browsers showing it automatically and some other not showing it or showing it in some selected cases.
Property Name: showsXhtmlAccessKey
Related properties: supportsXhtmlBasic10, supportsXhtmlMp10
Ontology Name: <none>
| Status: Undecided |
Generic HTTP
HTTP-Equiv-Refresh Support
Description: Describes if the browser supports and fulfills actions defined using the meta element and the 'http-equiv="Refresh"' attribute.
Measurement: If the action is fulfilled as requested, then it's supported.
Type: Boolean, true if supported
Justification: Redirection and page refresh are important accessibility points and specifically to the mobile are important as users are in a special environment and might not pay the same attention as while sitting at their desk. This is an important functionality to know if it is supported when adapting for different browsers and contexts.
Property Name: supportsHttpEquivRefresh
Related properties: <none>
Ontology Name: <none>
| Status: Undecided |
Alternative for HTTP-Equiv-Refresh
Description: There is a non-standard HTTP header that can be used in place of the meta tag for http-equiv. While it is not standard it is supported by many browsers, this property should describe if this header is supported.
Measurement: If the action is fulfilled as requested, then it's supported.
Type: Boolean, true if supported
Justification: As an alternative to meta elements, this header can be used. It is important when used in combination with the other proposed property about refresh and redirection.
Property Name: supportsAlternativeHttpEquivRefresh
Related properties: supportsHttpEquivRefresh
Ontology Name: <none>
| Status: Undecided |
Caching
Description: Some browsers are capable of caching content. Caching means being able of storing in the local memory some contents such as style sheets or media files and avoiding to retrive them if needed again when browsing back or loading a page that references to the same external contents.
Measurement: BPWG understands that measurement of cache support and behaviour can be tricky and delegates to DDWG to investigate further.
Type: Boolean, true if supported
Justification: Caching is a practice that can in general save network usage and dramatically shorten waiting times. In the mobile space this is of great effect and can be of great use when creating and adapting content.
Property Name: supportsCachingDirectives
Related properties: <none>
Ontology Name: <none>
| Status: Undecided |
Streaming video of H264 Baseline Profile Level 1.0
Description: Device is capable of streaming video of H264 Baseline Profile (BP) Level 1.0: Primarily for lower-cost applications with limited computing resources, this profile is used widely in videoconferencing and mobile applications.
| Max macroblocks per second | 1485 | |
| Max frame size (macroblocks) | 99 | |
| Max video bit rate (VCL) for Baseline, Extended and Main Profiles | 64 kbit/s | |
| Max video bit rate (VCL) for High Profile | 80 kbit/s | |
| Max video bit rate (VCL) for High 10 Profile | 192 kbit/s | |
| Max video bit rate (VCL) for High 4:2:2 and High 4:4:4 Predictive Profiles | 256 kbit/s | |
| Examples for high resolution @ frame rate (max stored frames) in Level | 128x96 @ 30.9 (8) 176x144 @ 15.0 (4) |
[source: wikipedia, h264: http://en.wikipedia.org/wiki/H264#Profiles]
Measurement: The property is measured by trying to stream a conformant H264 video at baseline profile level 1.0,to the device.
Type: Boolean, true if supported
Justification: Needed to delivery adapted optimal quality adapted video to device. Indicating that device can streaming H264 is not enough. Description must be more precise with respect to which profile and level device supports, so guarantee of playback at optimal quality can take place. If no such description is available, one is forced to use the least common denominator, which is level 1.0. This will however not result in the best user experience, as a user should will not get the best quality the device support within the Delivery context. Also, if one tries to delivery a video with a to high level, the video will not play on the device at all.
Related Properties:
Ontology Name: <none>
| Status: NOT CORE |
Streaming video of H264 Baseline Profile Level 1.3
Description: Device is capable of streaming video of H264 Baseline Profile (BP) Level 1.3: Primarily for lower-cost applications with limited computing resources, this profile is used widely in videoconferencing and mobile applications.
| Max macroblocks per second | 11880 | |
| Max frame size (macroblocks) | 396 | |
| Max video bit rate (VCL) for Baseline, Extended and Main Profiles | 768 kbit/s | |
| Max video bit rate (VCL) for High Profile | 960 kbit/s | |
| Max video bit rate (VCL) for High 10 Profile | 2304 kbit/s | |
| Max video bit rate (VCL) for High 4:2:2 and High 4:4:4 Predictive Profiles | 3072 kbit/s | |
| Examples for high resolution @ frame rate (max stored frames) in Level | 320x240 @ 36.0 (7) 352x288 @ 30.0 (6) |
[source: wikipedia, h264: http://en.wikipedia.org/wiki/H264#Profiles]
Measurement: The property is measured by trying to stream a conformant H264 video at baseline profile level 1.3,to the device.
Type: Boolean, true if supported
Justification: Needed to delivery adapted optimal quality adapted video to device. Indicating that device can streaming H264 is not enough. Description must be more precise with respect to which profile and level device supports, so guarantee of playback at optimal quality can take place. If no such description is available, one is forced to use the least common denominator, which is level 1.0. This will however not result in the best user experience, as a user should will not get the best quality the device support within the Delivery context. Also, if one tries to delivery a video with a to high level, the video will not play on the device at all.
Related Properties:
Ontology Name: <none>
| Status: NOT CORE |
Document Object Model (DOM) level
Description: The Document Object Model (DOM) level that a browser supports.
Measurement: DOM Level 1, DOM Level 2, DOM Level 3
Type: String
Justification: When creating rich mobile applications (specially applications that rely on AJAX technologies) it is important to know what is the DOM Level Support in order to know the allowed methods to access and modify a page.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: NOT CORE |
XMLHttpRequest
Description: This property indicates whether the browser implements the XMLHttpRequest as it is specified in the normative document http://www.w3.org/TR/XMLHttpRequest/
Measurement: Verify the browser sends the information appropriately and behaves as expected
Type: Boolean, true if supported
Justification: There are some situations where a mobile solution can benefit from calling the server to obtain new data without reloading a whole page. If an application knows that a device supports the XMLHttpRequest object it will be able to use AJAX interactions when needed.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: NOT CORE |
Characters per line
Description: The total number of characters that can be displayed on a line (without scrolling) of the device when the default font is selected.
Measurement: Using the default font face and an agreed character, verify how many appear on the same line
Type: non-negative integer
Justification: Needed to adjust pagination of text, or in any situation where knowing the maximum number of characters in a line is valuable, like the paginations made in the MyMobileWeb project. Example:
http://forge.morfeo-project.org/wiki_en/images/9/94/Table_linktoeachpage_opw.jpg
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: NOT CORE |
Device model name
Description: The model name of the device (in the case of the browser this property will be the browser version, or do we need a different property?)
Measurement: Does not apply
Type: String?
Justification: Needed to for marketing purposes (offer some functionality only on a device), for workaround of problems on an specific device, etc.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Shows page title by default
Description: Indicates whether the Web Browser displays the title of the document on the top of the screen or not.
Measurement: Verify that when a title element is specified in the head part of the page, the browser displays the text by default.
Type: Boolean, true if supported
Justification: Needed to adapt in casee the browser doesn't display the title. Sometimes developers put important information on the title of the document and if it is not finally displayed the user might lose important information
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Preferred layout method
Description: The preferred method for laying out elements in the screen.
Measurement: {CSS,Table}
Type: Set of values
Justification: There are a lot of Mobile Web Browsers that do not support CSS positioning of elements on the screen. In that cases it is necessary to fallback to another layout or to use a table as a layout mechanism.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Best Background Colors
Description: The background colors that are best readable on the screen of the device
Measurement: Verify in different conditions such as darkness and sunlight, with default font color, links and visited links, which is the background colors that gives the best readability.
Type: This will be an ordered enumerated set of colors (expressed in RGB format).
Justification: Depending on the quality of the screen of the device some colors are best readable as background than others. From an adaptation perspective this can be used to use the background colors more suitable for providing a good usability.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Preferred font
Description: This property indicates which is the best readable font (and font size) for a specific device.
Measurement: Test the browser / device. Issue: What is the criteria to be followed to determine what is the best readable font on a device?
Type: String
Justification: Needed to adapt the contents on a device in order to use the best font in terms of readability.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Device Brand
Description: The name of the device brand.
Measurement: This is a value inherent to each device.
Type: String
Justification: Needed to adapt to an specific device due to limitations or optimizations demanded by the user.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: deviceVendor
| Status: Undecided |
File Upload
Description: This property indicates if it is possible to upload a file (stored on the device) from the browser.
Measurement: Test the browser with an <input type="file"
Type: Boolean
Justification: Needed to adapt the presentation of <input type="file" ..> components. If a browser does not support this feature it can be degraded gracefully hidding the input control or providing an alternative way of uploading the file, for example, by sending an MMS
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Form Text Input Mode
Description: This property indicates the preferred way of supporting specific formats for input type="text" fields. This can be done with the 'format' attribute, as a W-CSS property or using the 'inputmode' attribute.
Measurement: Test the browser with <input type="text" controls specifying the format with the mechanisms cited above.
Type: enumerated {format_as_attribute, format_as_css, format_using_inputmode}
Justification: Needed to adapt to different delivery contexts in order to respect user intentions with respect to format restrictions and at the same time improving text user input.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Tel URI Schema
Description: This property indicates if it is possible to launch a phone call from the browser.
Measurement: Test the browser with a URI schema "tel:xxx"
Type: Boolean
Justification: Needed to adapt the presentation of <a href="tel:xxx"> links. If an adaptation platform knows that a browser does not support launching phone calls then it can gracefully degrade the link to a label (decorated with a tiny image of a phone, for example), avoiding a bad experience from the user point of view
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Marquee
Description: This property indicates whether the device supports marquee effects or not.
Measurement: Test the browser with -wap-marquee properties and see the achieved results.
Type: Boolean
Justification: Useful for authors at design time in order to know what devices (from the expected set of devices that will connect to the application) will support marquee effects.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Maximum Image Height on Screen
Description: This property indicates the maximum height of images (in pixels) that can be rendered properly by the Web Browser.
Measurement: Test the browser with different image heights until the image cannot be displayed.
Type:
Justification:
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Maximum Image Width on Screen
Description: This property indicates the maximum width (in pixels) of images that can be rendered by the Web Browser without rescaling.
Measurement: Test the browser with different image widths until the image cannot be displayed. The property will be measured in pixels.
Type: non negative integer
Justification: Needed to adapt images in a way that it is guaranteed that the image will be viewable on the user's browser.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Maximum Download Size
Description: This property indicates the maximum size (in Kb) of objects that can be downloaded from the web browser to the device.
Measurement: Test the browser with objects with different sizes until the memory is overflowed. The property will be measured in Kb.
Type: non negative integer
Justification: Needed to offer the user only those contents that meets the device download restrictions.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
CSS White Space nowrap
Description: This property indicates if the browser honours the 'white-space: nowrap' property and what is the mechanism to allow the user to see the content that does not fit on the screen.
Measurement: Test the browser with a paragraph setted to white-space: nowrap
Type: enumerated {not_supported,supported_times_square_mode,supported_horizontal_scrolling}
Justification: Needed to know if the device supports the no wrap behaviour (and the way to achieve it) in order to adapt the presentation
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Has a Pointing Device
Description: Indicates whether the device has a pointing device or not. A pointing device allows the user to select any pixel on the screen.
Measurement: Test the device or red manufacturer's documentation
Type: Boolean
Justification: Needed to provide a user experience adapted to the device that the user owns. For example, if the device has a pointing mechanism it makes sense to use image maps to provide a more graphical interaction.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: pointingResolution
| Status: Undecided |
Preferred Image Format
Description: Although web browsers might support a variery of image formats, normally there will be an image format that will provide the best results in terms of rendering quality or consumed resources.
Measurement: Test the browser with the different image formats supported and decide what is the best Issue: What would be the criteria to decide that one format is preferred over another???
Type: String
Justification: Needed to serve images in the most suitable format for a browser.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: preferredImageType
| Status: Undecided |
Preferred Mark-up
Description: Although web browsers might support a variery of markup languages, normally there will be a markup language that will provide the best results in terms of realability and standards support.
Measurement: Test the browser in the different markup languages supported and decide what is the best. Issue: What would be the criteria to decide that one format is preferred over another???
Type: String
Justification: Needed to serve pages in the most suitable markup for a browser.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: preferredPageMarkup
| Status: Undecided |
Text Rows on Screen
Description: This property indicates the number of rows that the device can display without scrolling when the default font browser is selected.
Measurement: Test the browser with a set paragraphs of a one line length, white-space: wrap and see what is the number of rows that appear in the screen until the scroll bar appears.
Type: non negative integer
Justification: Needed to adjust default pagination parameters of tables, lists, etc.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Select Control Rendering
Description: Indicates how a <select> control of a form is displayed by the browser.
Measurement: Test the browser to check if the select is showed as a drop down list, as a set of inline radio buttons (or checkboxes) or as a link to a set of external radio buttons (or checkboxes).
Type: enumeration {select_as_drop_down_list,select_as_inline_radiobuttons, etc.}
Justification: Needed to adapt the rendering of a select control to a multiplicity of delivery contexts avoiding wasting space on the screen. For example, if by default the select is displayed as a set of inline radio buttons, an adaptation solution might choose to present the select (using HTML and/or Javascript) in a way that avoids the waste of space in the screen (i.e. simulating a drop down list).
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
SMS URI Schema
Description: This property indicates if it is possible to send an SMS from the browser.
Measurement: Test the browser with a URI schema "sms:xxx"
Type: Boolean
Justification: Needed to adapt the presentation of <a href="sms:xxx"> links. If an adaptation platform knows that a browser does not support sending SMS then it can gracefully degrade the link to a label (decorated with a tiny image of a message, for example), avoiding a bad experience from the user point of view.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Font Faces
Description: This property enumerates the different fonts which its respective sizes supported by the device.
Measurement: Test the browser / device and read the documentation to determine what are the fonts and sizes supported
Type: Enumeration
Justification: Needed to adapt the contents on a device in order to use the best available fonts without sacrifying usability and trying to respect author intentions.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
Cookie
Description: The ability of a web browser to support cookies.
Measurement: A web server sets a cookie in an HTTP Response. The mobile web browser makes a subsequent HTTP request. If the browser supports cookies the HTTP request should contain the cookie previously set by the web server.
Type: Boolean
Justification: It is very important to know if a browser support cookies, among other things, to support the concept of user session. An adaptation solution that knows that a device does not support cookies should fallback to a URI rewriting mechanism.
Related Properties:
Submitted by: José Manuel Cantera Fonseca
Ontology Name: <none>
| Status: Undecided |
|