CoreVocabularyAllSubmissions

From Device Description Working Group Wiki
Revision as of 19:42, 17 September 2008 by Ot (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

All submitted Properties 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.

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. This property is in the class of display properties.

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.

Status: CORE

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. This property is in the class of display properties.

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.

Status: CORE

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.

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 transcding/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: Positive integer.

Justification: Used in conjunction with the Screen Height 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.

Related properties: Screen Height, Screen Width - and there is almost certainly a need for a similar Usable Screen Width

Status: Not yet discussed by DDWG members.

Supported Markups

Description: Browser supported markup languages: the markup languages representing a Web page (or fragment thereof) that can be rendered by the device Web browser(s). Support of a markup language implies that the conformance requirements have been met by the browser implementation as per the relevant markup specification.

Measurement: The union of the markup language MIME-types present in the HTTP Accept request header that are sent by any browsers installed on the device.

Type: A list of properties each of which represents a specific content type. Each content type is identified by its name, for example text/HTML. Valid values are those conformant to MIME-type naming rules (ref: http://www.iana.org/assignments/media-types/)

Justification: In order to avoid sending incompatible markup to the browser, and to allow the use of more advanced markup features where supported. Although this information can be determined at request time from the request header, inclusion in the repository will allow Web content providers to ascertain which markups are most desirable to support, and also to pre-build pages in the supported markups.

Related properties:

Status: Not yet discussed by DDWG members.

Supported image types

Description: Supported Image Types. This property is an unordered list of names of image types/sub-types that are supported by the user agent for display within a web page. This excludes image types/subtypes that can be displayed by dedicated applications on the device but not by the browser as part of a web page.

This property should be one of a set of properties related to image support. Other properties in this set may describe the limits to image file size, image dimensions, file extensions, and the contexts in which images can be used.

Measurement: Each supported image type/sub-type is described by a defined name and the "Supported Image Formats" property is the set of names of all image types that are supported by the device. The image type names are Internet Media Type (ref: http://www.w3.org/2001/tag/2002/0129-mime ) names (e.g. image/jpeg) with additional parameters, when required, to identify specific sub-types of that image type. The image sub-types should only be specified in cases where not all of the sub-types of an image type are supported.

An initial set of allowed image types will be defined as the current set of defined Internet Media Types with the prefix "image/" if an initial list is provided it must be extensible to allow for new image subtypes when they are assigned a new Internet Media Type.

The mechanism for describing image sub-types (for example progressive JPEG images versus baseline JFIF) will need to be defined by the DDWG.

Type: The property is an unordered set of strings.

Justification: Image type adaptation or selection is frequently required when delivering image content to mobile devices. Original images may not be in a format that is supported by the target device, so conversion is required. In cases where an image is available in multiple formats, it is necessary to select a format that will be supported by the device/browser. In both cases, it is vital to be aware of which image formats are supported by the target device or images may not be rendered the device/browser.

Identified as an important property by the DDWG in its Top N finding. Present in UAProf. Present (and used) in existing adaptation solutions.

Related properties:

Status: Not yet discussed by DDWG members.

Display orientation

Description: The Orientation of a display, describing 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.

In a static device description, this property will describe the orientation of the display in its most common or default usage. When used in a dynamic context, this property may indicate the current orientation if the device is capable of reporting its current orientation. This information can be used to modify the interpretation of properties which describe the display width and height (in its default orientation).

If multiple displays are defined for the device, then this property should be defined separately for each display.

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.

Related properties:

Status: Not yet discussed by DDWG members.

XHTML-MP 1.0

Description: Browser support of XHTML-MP 1.0

Measurement: The BPWG knows that full and exact markup 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.

Type: Boolean, true if supported

Justification: Markup support is required to know if the page should be presented using one markup or another and if the browser will be able to render a page.

Related Properties:

Status: Not yet discussed by DDWG members.

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

Related Properties:

Status: Not yet discussed by DDWG members.

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.

Related Properties:

Status: Not yet discussed by DDWG members.

CSS 1 support

Description: CSS 1 support

Measurement: 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.

Type: Boolean, true if supported

Justification: CSS support is important to know if and how it can be used to define the page layout.

Related Properties:

Status: Not yet discussed by DDWG members.

CSS 2.1 support

Description: CSS 2.1 support

Measurement: 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.

Type: Boolean, true if supported

Justification: CSS 2.1 support is important to know if and how it can be used to define the page layout.

Related Properties:

Status: Not yet discussed by DDWG members.

WCSS support

Description: WCSS support

Measurement: 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.

Type: Boolean, true if supported

Justification: WCSS support is important to know if and how it can be used to define the page layout.

Related Properties:

Status: Not yet discussed by DDWG members.

Usable screen width

Description: Usable screen width while browsing

Measurement: The addressable 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: Integer positive number

Justification: The maximum usable width is important both for image scaling and general page layout

Related Properties:

Status: Not yet discussed by DDWG members.

Usable screen height

Description: Usable screen height while browsing

Measurement: The usable 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: Integer positive number

Justification: The maximum usable height is important both for image scaling and general page layout

Related Properties:

Status: Not yet discussed by DDWG members.

XHTML Basic 1.1

Description: Browser support of XHTML Basic 1.1

Measurement: The BPWG knows that full and exact markup 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.

Type: Boolean, true if supported

Justification: Markup support is required to know if the page should be presented using one markup or another and if the browser will be able to render a page.

Related Properties:

Status: Not yet discussed by DDWG members.

Alternative Orientation

Description: There should be a property to define if it is possible for the user to use 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 is possible

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.

Related Properties:

Status: Not yet discussed by DDWG members.

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.

Related Properties:

Status: Not yet discussed by DDWG members.

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.

Related Properties:

Status: Not yet discussed by DDWG members.

Italic and bold

Description: Italic and bold are two typical font effects that help authors.

Measurement: If the browser is capable of showing italic, or bold or another font effect it should be possible to have a properties in the vocabulary to represent this. Listing every single possible font face would be overkill, but we think that basic font effects would fit well in a core vocabulary. Each should be listed on its own.

Type: Boolean, true if supported

Justification: Mobile devices sometimes don't support any font face or font effects other than the default one. We believe it would be useful for authors to know if a font effect is supported or not and in case be able to use alternative methods to achieve a similar effect.

Related Properties:

Status: Not yet discussed by DDWG members.

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.

Related Properties:

Status: Not yet discussed by DDWG members.

HTTP-Equiv Support

Description: The property should describe 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.

Related Properties:

Status: Not yet discussed by DDWG members.

Alt for HTTP-Equiv

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.

Related Properties:

Status: Not yet discussed by DDWG members.

ECMAScript

Description: Some browsers are capable of supporting ECMAScript. Scripting can provide some advanced functionalities on the client-side.

Measurement: BPWG knows that the support degree, especially on scripting can vary and this one of the reasons why some scripting languages have failed. We believe that DDWG should investigate and make public its findings about scripting support and how this can be reflected in one or more properties. Hopefully we can have one Boolean property and then some detailed properties.

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.

Related Properties:

Status: Not yet discussed by DDWG members.

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.

Related Properties:

Status: Not yet discussed by DDWG members.

Image Formats

Description: Image media formats as supported by the browser for in-line display.

Measurement: If the browser is capable of displaying an image in a mobile web page.

Type: Boolean, true if supported.

Justification: Many different image format and sub-formats are present on the market. We believe that at least GIF, JPEG, PNG should be listed in the core vocabulary. Images are a core part of page design and should be present in the database to help both designers and image transcoding applications.

Related Properties:

Status: Not yet discussed by DDWG members.

Shows Access Keys

Description: This property should describe if the browser automatically shows a key associated with an anchor via an accesskey.

Measurement: 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.

Related Properties:

Status: Not yet discussed by DDWG members.

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:

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:

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

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

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

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

Device Brand

Description: The name of the device brand. This property corresponds to the deviceVendor property of the ontology

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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.

This property is related to the pointingResolution property of the ontology.

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

Status: Not yet discussed by DDWG members.

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.

This property corresponds to the preferredImageType property of the ontology.

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

Status: Not yet discussed by DDWG members.

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.

This property corresponds to the preferredPageMarkup property of the ontology.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.

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

Status: Not yet discussed by DDWG members.