Meeting summary – 21 Jan 2008
[Meeting summary – 21 Jan 2008] Scripting as a vocabulary entry, F2F agenda.
[Scripting] It has been proposed that the Core Vocabulary should include a property representing information about the client’s support for scripting. It is unclear what is meant by "supports script", since it is known that few if any devices support 100% the official scripting specifications. Therefore a Boolean property would be of little value as it would generally be False. Alternatively, the group has already decided that regarding image support it would be sufficient to record what the manufacturers claim is supported, rather than what has been verified, as the existence of a claim is easier to test. Finally, it was also suggested that one could identify a common code library (such as the recent OpenAjax Hub or some WURFL accessors as used in MyMobileWeb), and test the client to see if it will support these scripts. This would provide a meaningful Boolean interpretation for “supports script”.
It was also noted that knowing about scripting support would not be sufficient for even basic Ajax applications, which would need to know about the DOM support and possibly the specific mechanism for asynchronous callback. For detailed Ajax use cases, it was suggested that a domain-specific vocabulary would be needed and that perhaps the OpenAjax community could devise one.
Scripts can be considered as an external/embeddable resource, just like stylesheets, images, audio and so on. It was proposed that perhaps the vocabulary should simply have a single property that enumerated all embeddable resource types, rather than have separate properties for each category. This would be more extensible than a categorised approach, and would be better able to handle resource types that might belong to multiple categories or to new/unanticipated categories. Most of the participants who expressed an opinion on this felt that the categorised approach better suited the expectations of developers. It is also possible for the same value to be in more than one category, such as GIF89a which could be a 2D image format and (in some interpretations) a video format. It was suggested that programmable formats (like scripts) should not be considered in the same category as passive data such as images. However, SVG was held up as a counter example, which can be considered as a representation of an image but is also a programmable format.
The group discussed the two views (to use categories for properties or just use a single property to enumerate all embeddable formats) in detail, but did not reach a conclusion. This issue will be discussed during the week and at the next call.
Regarding the value representing support for script, the importance of types of script and their versions were considered important. The group resolved not to use a Boolean property type. Instead there will be many values and these values will also reveal the type and version, much like is already proposed for image formats (based on MIME types).
At this point it seems certain that the Core Vocabulary will mention script support, but the manner in which this (and other embeddable resource types) is represented remains to be decided.
[F2F] The date of the Face-to-Face has been confirmed as Thursday 6and Friday 7 of March, in Seoul, Korea. Three topics are proposed for the agenda: the Core API editors’ draft, the final version of the Core Vocabulary and a review of the Structures WG Note.
Attendees: Nacho, Jongpil, Pontus, Anders, Matt, José, Rotan, Jo, Bryan
Meeting Summary - 14 Jan 2008
[Meeting Summary – 14 Jan 2008] Priorities for 2008, Editors’ meeting, Roadmap.
[Priorities] The group commenced the meeting by reviewing the outstanding tasks to produce the chartered deliverables by the target date of May 2008. The key deliverables in this time frame are the Core API, the corresponding Conformance Requirements (an appendix to the Core API document), the completion of the Core Vocabulary, some work on the identification of devices and user agents, and (optionally) a Note on an API extension to deal with structures (of device descriptions), and calls for implementations and data contributions.
It was proposed that the group aim for a Candidate Recommendation in April, one month ahead of the scheduled end of the group’s charter. This will give time for implementations to be presented. Already there is progress on implementations from a number of group participants, based on work already undertaken, especially the work during the previous face-to-face meetings.
There are some outstanding matters to consider in the Core Vocabulary. Some essential properties may yet be included (e.g. “script support” – possibly linked to “ability to support the OpenAjax Hub”) and there needs to be some description of “Aspects”, a concept introduced during the previous face-to-face. It was proposed that Aspects could be incorporated as an annex to the Core API, as perhaps the Core Vocabulary should be. The group requested investigation by the W3C team to determine if the Vocabulary of Device Properties and Vocabulary of Device Aspects could be re-cast as annexes of the Core API. Furthermore, a comparison between Aspects and a similar concept in UAProf was suggested.
There will be another face-to-face in March, at which the group expects to have an editors’ draft of the Core API and a final version of the Core Vocabulary for ratification.
The recent departure of Rhys Lewis as coordinator of the UWA Ontology was noted, but the group feels that there are sufficient resources to keep this work active. New people are also expected to join and assist.
[Editors Meeting] There will be a face-to-face meeting of the editors of the Core API document, in Dublin, Ireland, at the end of January. Editors are requested to attend, and other group members may attend at their own discretion.
[AOB#1] It was noted that the Mobile Web 2.0 mobileOK test suite has started with a service launch planned for later this year. With growing attention on the production of good quality Web presentation on mobile devices, one can also expect a growing demand for device descriptions for adaptive solutions.
[AOB#2] For the meetings in March, it is anticipated that the DDWG will be allocated the latter part of the week for the face-to-face.
[Roadmap] Based on the discussion in this meeting, the roadmap for 2008 looks as follows:
- Core API editor’s meeting at the end of January;
- Core Vocabulary contributions cease at the end of first week of February;
- Core API “Editors’ Draft” ready for the F2F in March;
- final version of Core Vocabulary “WG Note” ready by the F2F in March;
- Core API “Candidate Recommendation” in April;
- calls for implementations and data contributions in May.