Number: DS61 Annotea <desc> Description: Is the annotea protocol design useful for supporting annotations of web pages? <narr> Narrative: Documents that discuss the usefulness and relevance of the Annotea protocol are relevant. Messages pointing out problems with Annotea or otherwise arguing against its usefulness should provide concrete examples. Arguments about the future of Annotea are also relevant. Press releases or annoucements of new projects are not relevant unless they specifically address a known problem with Annotea. </top> <top> <num> Number: DS62 <title> DOM and DHTML <desc> Description: What is the relationship of the Dynamic HyperText Markup Language (DHTML) and the Document Object Model (DOM)? <narr> Narrative: Relevant documents will discuss how DHTML supports the DOM or relates to the DOM objectives. Any item which presents only DHTML markup techniques without regard to the standards, effects upon, or intent of the DOM is not relevant. </top> <top> <num> Number: DS63 <title> language translation guidelines <desc> Description: What guidelines are used to determine how W3C information is translated into non-origin languages. <narr> Narrative: E-mails that describe tools used by the W3C to assist in translation efforts are relevant. Examples of portions of a translated document used as an example are relevant. E-mails written in foreign languages, or with an included translation, that do not directly state how to translate are not relevant. </top> <top> <num> Number: DS64 <title> blocking pop-ups <desc> Description: What are the problems associated with different types of pop-up blocking software and what are some of the advantages? <narr> Narrative: E-mails that talk about the advantages and disadvantages or pop-up blocking software are relevant. E-mails that talk about how pop-ups work and what the software does to protect the computer is relevant. Information about viruses, worms, and trojans are not relevant unless they are specific to a type of pop-up. </top> <top> <num> Number: DS65 <title> XML Query XQuery <desc> Description: What is XML Query (XQuery), and what is it being used for? <narr> Narrative: Documents that discuss the state of the XML Query specification are relevant. Applications are relevant if they are discussed, rather than just being press releases or product announcements. Documents that discuss the efficiency of XML Query are relevant. </top> <top> <num> Number: DS66 <title> Semantic Web Services applications <desc> Description: What are the applications of semantic web services? <narr> Narrative: Relevant documents will discuss deployed applications that use semantic web services. Discussions of the utility and relevance of semantic web services are relevant. Efficiency concerns and discussions of implementation issues are also relevant. </top> <top> <num> Number: DS67 <title> UTC GMT local time <desc> Description: What are the problems created by the the differences between UTC, GMT, and local time? <narr> Narrative: Relevant documents will address the problem of using UTC, GMT, or local time and the additional problems that arise with the use of daylight savings time. Discussions that concern the issue of duration of time versus a specific date or time are relevant. Also relevant are documents that discuss the problems involved when the geographic location is not the same as the time zone set for the computer. Documents that discuss the time for a chat or for a conference are not relevant. </top> <top> <num> Number: DS68 <title> assistive technology evaluation tools <desc> Description: How useful are existing evaluation tools for assistive technology? <narr> Narrative: E-mails that detail how well assistive technologies assist, adapt, and rehabilitate devices are relevant. Further, the the processes used in selecting, locating, and using assistive technology are also relevant. Information that relates to general or specific flaws or advantages are relevant. Definitions or assistive technology is not relevant. Types of evaluation tools and e-mails that do not speak to specific applications are not relevant. </top> <top> <num> Number: DS69 <title> P3P Recommendation 1.0 1.1 <desc> Description: Compare and contrast on P3P Recommendations 1.0 and 1.1. <narr> Narrative: As a comparison of standards, relevant documents include comparisons, comments and critiques of P3P 1.0 and P3P 1.1 (the latter of which is in progress). W3C News Releases that include news items referring to P3P draft or standards releases are not relevant. </top> <top> <num> Number: DS70 <title> blind HTML authoring tools <desc> Description: What HyperText Markup Language (HTML) authoring tools are suitable for the visually impaired or blind web designer? <narr> Narrative: Relevant documents discuss opinions/views of the usefulness of various HTML web page authoring tools for the blind or visually impaired. Identifying an authoring tool as being of possible use to the blind or visually impaired may also be relevant, especially if anyone responds with further comment about the named tool(s). </top> <top> <num> Number: DS71 <title> multilingual versus international <desc> Description: What are the differences between multilingual texts and internationalization? <narr> Narrative: Relevant documents discuss the similarities, differences, and distinctions between multilingual texts and international ones. Documents that discuss specific examples are relevant if they address the two concepts. Both words are used in many contexts – only those that discuss the similarities and differences are relevant. </top> <top> <num> Number: DS72 <title> device independence <desc> Description: What is device independence? <narr> Narrative: Relevant documents will discuss device independence. Documents that examine the concept with regard to accessibility are relevant. Documents that simply define the term or that discuss specific devices are not relevant. </top> <top> <num> Number: DS73 <title> RDF/XML Syntax Specification <desc> Description: Compares, contrasts updated RDF/XML Syntax Specification with preexisting RDF recommendations. <narr> Narrative: W3C issued a RDF/XML specification in 2001-02 that superseded a number of preexisting RDF recommendations. In comparing the new specification with earlier specifications, relevant documents may include references to RDF Schema, revised drafts, RDF syntax, and document crosslinks (references). Announcements of the release or publication of specifications are not relevant unless there are attached comments or responses. </top> <top> <num> Number: DS74 <title> scalable vector graphics <desc> Description: What are the advantages and disadvantages of Scalable Vector Graphics (SVG)? <narr> Narrative: Discussion of SVG capabilities are relevant. New or proposed SVG technology is also relevant. Issues surrounding the applications, programming language, platforms, usability, and functionality of SVG are also relevant. However, information that talks about competing technologies are not relevant. </top> <top> <num> Number: DS75 <title> web languages and mobile devices <desc> Description: Discusses the suitability of web languages (such as HTML) for small hand-held devices such as PDAs and wireless telephones. <narr> Narrative: The increasing use of web-capable hand-held devices such as PDAs and wireless telephones has raised questions as to how existing web programming languages interface with these smaller devices. Some relevant issues include SVG/PDA, XHTML, minimal browser capabilities, and mobile multimedia messaging. General documents referring to PDAs and wireless technology are relevant if they address the display of web content on those devices. </top> <top> <num> Number: DS76 <title> PICS parental control <desc> Description: Is PICS useful for supporting parental control and other filtering needs? <narr> Narrative: Relevant documents will discuss whether PICS is useful for implementing parental content controls and/or other filtering needs. Especially relevant are successful filtering applications that use PICS, or demonstrations that PICS is an inadequate solution. Press releases for PICS-based products are not by themselves relevant. </top> <top> <num> Number: DS77 <title> Resource Description Framework <desc> Description: What are the applications of the resource description framework (RDF)? <narr> Narrative: Relevant documents will discuss the various applications of the resource description framework (RDF), and whether RDF is the best approach for those applications. Questions about how to use RDF are not relevant. Discussions about the nature of RDF (that is, whether RDF is in fact a framework, a language, or something else) are relevant if they are in the context of an application. </top> <top> <num> Number: DS78 <title> Timed Text annotation <desc> Description: Discusses the desirability of including a means of annotating timed text (subtitles, on-screen ticker-tape, etc). <narr> Narrative: In drafting a common format for timed text, a question arose over whether or not to include annotation capability (such as Ruby) for languages that use ideograms (such as Chinese or Japanese). Relevant documents should have references to timed text and annotation. </top> <top> <num> Number: DS79 <title> HTTP future web messaging <desc> Description: Is the HyperText Transfer Protocol (HTTP) a suitable transport mechanism for future reliable web messaging? <narr> Narrative: Relevant items discuss use of the HyperText Transfer Protocol in future web messaging. Comparisons to current alternative protocols wherein pros and cons are presented are relevant. Forecasts of future transport scenarios where HTTP is considered are also relevant. Any discussion about HTTP other than in consideration as a future messaging transport mechanism are probably not relevant. </top> <top> <num> Number: DS80 <title> compound documents <desc> Description: What is the impact of compound documents? <narr> Narrative: Documents should discuss the impact of compound document formats. Discussion about exchanging compound documents between users, reading them in different applications, and the impact on network bandwidth efficiency are relevant. Documents that merely identify a compound document format or an application that uses one are not relevant. </top> <top> <num> Number: DS81 <title> Hit-Metering Draft <desc> Description: Find comments, critique, and discussion on the draft proposal for an IESG standard on Hit-Metering. <narr> Narrative: Relevant messages discuss the status of the draft proposal on hit-metering. Documents discussion hit-metering in general or implementations are not relevant unless they are in the context of discussion on the proposed standard. </top> <top> <num> Number: DS82 <title> VoiceXML diacritical marks <desc> Description: Discusses the application of VoiceXML to languages that use diacritical marks to differentiate meanings between identically-spelled words. <narr> Narrative: Voice browsers and speech interface frameworks may not accurately capture languages such as Chinese, Japanese, and Hebrew, which use diacritical marks to give different meanings and pronunciation to words that otherwise use the same characters. Relevant documents should contain references to diacritical marks. Note that press releases that refer to Voice XML without comments or responses attached are not relevant. </top> <top> <num> Number: DS83 <title> CSS1 CSS2 comparison <desc> Description: Compare two W3C recommendations for Cascading Style Sheets (CSS1 and CSS2). <narr> Narrative: Cascading Style Sheets (CSS) is an important web programming tool. W3C issued a recommendation for CSS use (CSS1), and after several years, drafted a second version (CSS2). Relevant documents should contain references to CSS1 and CSS2. Of particular interest are documents that discuss browser capabilities, errors, and UAAG. Documents discussing translation of CSS1 or CSS2 into foreign languages are not relevant. </top> <top> <num> Number: DS84 <title> Browser Link Behavior <desc> Description: What are the problems associated with HTML links that behave differently in different browsers? <narr> Narrative: Any discussion that relates to specific differences in link behavior between Mozilla, Netscape, Internet Explorer, or other browsers is relevant. Attempts to assist by sharing a quick fix, or attempts to gain assistance for a link problem, are relevant. Information about upcoming browser advantages are not relevant unless they include a known correction to a link problem. </top> <top> <num> Number: DS85 <title> WAI guidelines versus standards <desc> Description: Are the Web Accessibility Initiaitive (WAI) guidelines actually guidelines or standards? <narr> Narrative: Relevant documents discuss the difference between WAI guidelines and standards and explain why the author thinks they are one or the other. Documents that discuss how WAI guidelines can act as standards are also relevant. </top> <top> <num> Number: DS86 <title> define SOAP headers <desc> Description: What is a SOAP header? <narr> Narrative: A relevant message defines the structure and/or content of Simple Object Access Protocol (SOAP) headers. Items discussing HTTP or other kinds of headers without regard to SOAP are not relevant </top> <top> <num> Number: DS87 <title> Semantic Web services requirements <desc> Description: What are the functional requirements necessary for the future web architectures for semantic web services? <narr> Narrative: Relevant documents will argue about functions or functionality needed in the web architecture(s) expected to support the future semantic web services concept. Items with only lists of links to possibly related material will not be considered relevant. Discussions about prospective web services and related necessary web architecture are relevant. Semantic web services are relevant but theoretical views about the "semantic web" (not specifying services or applications) are not relevant. </top> <top> <num> Number: DS88 <title> web form reset button <desc> Description: What are the arguments regarding use of a reset button in a web form? <narr> Narrative: Including a reset button on web forms and the effect of that button within visual and non-visual web presentations is of interest. The "reset" function (or button) in non-interactive web applications, such as client server exchanges, etc. is not relevant. </top> <top> <num> Number: DS89 <title> vector graphics raster graphics <desc> Description: What are advantages and disadvantages of vector graphics compared to raster graphics? <narr> Narrative: Documents that discuss the advantages and disadvantages of raster graphics and vector graphics or that argue for one or the other are relevant. Also relevant are documents that discuss how they affect accessibility. Definitions of one or the other are not relevant unless they include advantages or limitations. Documents that talk about only the implementation of vector graphics are not relevant. </top> <top> <num> Number: DS90 <title> P3P vocabulary problems <desc> Description: Is the Platform for Privacy Preferences (P3P) Vocabulary sufficient to adequately satisfy website privacy documentation requirements? <narr> Narrative: Relevant documents discuss differences in view about the P3P Vocabulary elements being robust enough to fulfill the future needs of on-website privacy policy declarations. Other discussions of P3P are not relevant. </top> <top> <num> Number: DS91 <title> internationalization impact <desc> Description: What is the impact of the W3C's guidelines for internationalization? <narr> Narrative: The W3C Internationalization Activity proposes guidelines and techniques for internationalization. What is the impact of these recommendations? Implementation issues and efficiency concerns are relevant. Definitions of internationalization are not relevant. </top> <top> <num> Number: DS92 <title> Tidy SourceForge transition <desc> Description: What problems and concerns arose during HTML Tidy's transition from a personal project to a large open-source effort on SourceForge? <narr> Narrative: At a certain point, Dave Raggett's HTML Tidy program became popular enough that development was moved to SourceForge to allow for many people to easily contribute changes and improvements. E-mails discussing this transition are relevant. For example, problems introduced by moving to SourceForge are relevant, as are discussions of bugs that should be fixed or features that should be introduced now that Tidy has become a larger project. Discussion of proposed new features for Tidy is relevant. Questions about how to use Tidy, or similar programs such as JTidy, are not relevant. </top> <top> <num> Number: DS93 <title> VOIP <desc> Description: What is Voice Over Internet Protocol (VOIP), and what are its advantages and limitations? <narr> Narrative: E-mails that list the technological specifications of the software, computer, external devises, and bandwidth are relevant. Any messages about future developments, the history, or present technology is relevant. Advertisements are not relevant. Anecdotal information is not relevant unless specific technical data is related. </top> <top> <num> Number: DS94 <title> emoticons <desc> Description: Are emoticons and smilies useful and do they promote understanding? <narr> Narrative: A relevant document will discuss emoticons and smilies as a useful shorthand means of expression that promotes understanding. Documents that discuss the negative aspects of the use of emoticons are also relevant. Documents that just define or list kinds of emoticons are not relevant. </top> <top> <num> Number: DS95 <title> cognitive disabilities <desc> Description: What are the challenges in providing web access to the cognitively disabled? <narr> Narrative: Relevant documents present arguments and concerns about the challenges of providing web access to the cognitively disabled web user. A cognitively disabled user is one with a limited ability to perceive, recognize, understand, interpret, and/or respond to information. Also relevant to this query are items wherein defining terminology about the issues is discussed. Items discussing disabled users, without specific reference to "cognitive" disabilities are not relevant. </top> <top> <num> Number: DS96 <title> foreign language Ruby translation <desc> Description: Translation of small character annotations (Ruby) into foreign languages. <narr> Narrative: Relevant documents discuss the translation of small character annotations (Ruby) into languages other than that of the source document, for example, Japanese, German, and French. </top> <top> <num> Number: DS97 <title> evaluation of color contrast <desc> Description: How is color contrast evaluated in connection with making documents accessible for those who are color-blind? <narr> Narrative: Relevant documents will discuss how to evaluate the color contrast in a document or web page. Discussions of color contrasts are relevant if they discuss specific color contrasts as good or bad for accessibility. They are not relevant if they simply talk about colors as a way to enhance the look of a document or logo. </top> <top> <num> Number: DS98 <title> VoiceXML development issues <desc> Description: What were the problems discussed during development of the Voice Extensible Markup Language (VoiceXML, VXML) standards? <narr> Narrative: VXML development issues and discussions about solutions for those issues are relevant. Changes to prior versions, problems in version updating, bugs, etc., incorporated into the latest version (2.0) are relevant. Any items discussing voice browser/interface or speech issues related to the VXML 2.0 standards development are relevant also. Speech recognition grammar and the speech interface framework may be relevant but only if in regards to problems about the VXML standards. </top> <top> <num> Number: DS99 <title> canonical XML draft <desc> Description: Discusses issues raised in response to the proposed release of a draft recommendation for Canonical XML. <narr> Narrative: The release of a draft recommendation for the use of Canonical XML triggered discussion in a number of areas. Relevant documents include references to XML signature use, 118N working group, serial canonicalization, and Infoset. Announcements and calls for comment referring to Canonical XML draft releases are not relevant unless they have comments attached. Messages discussing foreign-language translations are not relevant. </top> <top> <num> Number: DS100 <title> intellectual property <desc> Description: What are the consequences of placing intellectual property on the Internet? <narr> Narrative: Relevant documents will discuss the legal, economic, and social ramifications of intellectual property on the Internet. Discussions indicating what changes occur with regards to copyright once someone places a document on the Internet are relevant. Discussions about the impact of the Internet on the idea of intellectual property are also relevant. </top> <top> <num> Number: DS101 <title> right-to-left languages <desc> Description: Which languages or scripts are right-to-left (RTL)? <narr> Narrative: Documents are relevant if they define which languages are RTL or if they discuss whether one should refer to "RTL languages" or "RTL scripts." Not relevant are discussions about mixed RTL/LTR scripts, for example a text that is written in a LTR language, such as English, but that includes a few RTL words in another language, such as Hebrew. Discussions about texts that are written in a RTL language but include numbers that are written LTR (example: Arabic) are not relevant. </top> <top> <num> Number: DS102 <title> web services orchestration choreography <desc> Description: Comparatively, what is the relationship of web services orchestration and choreography? <narr> Narrative: Relevant documents will relate and compare web orchestration and web choreography as the two terms pertain to user agents or web services/applications interacting on the future web. Documents discussing only orchestration or choreography alone are not relevant. </top> <top> <num> Number: DS103 <title> Domain name assignment <desc> Description: What is the best way to assign domain names? <narr> Narrative: Documents must discuss best practices for assigning domain names to computers. Other kinds of domains, such as knowledge domains or ontologies, are not relevant. Documents may argue for naming by location or by function. </top> <top> <num> Number: DS104 <title> icons accessibility <desc> Description: How do you make sure that icons are accessible and easy to use? <narr> Narrative: Discussions about sizes, colors, etc of specific icons and logos are relevant if they talk about why they aid accessibility for a certain disability, such as blindness or attention deficit disorder. They are not relevant if they simple talk about preferring certain colors or size without mentioning the why in connection with a disability. Nor are discussions relevant if they simply talk about how much space a logo takes up. </top> <top> <num> Number: DS105 <title> reification <desc> Description: What is the definition of reification? <narr> Narrative: Relevant messages contain debate regarding how to define reification. Currently, there is not a universal definition. However, attempts to define the word, details surrounding reification, and illustrative or subjective arguments qualify as relevant. E-mail messages which do not contribute to the debate are not relevant. </top> <top> <num> Number: DS106 <title> mobile device keyboards <desc> Description: How can keyboard commands be made available to applications that run on mobile devices that have a limited (or no) keyboard? <narr> Narrative: Discussions that attempt to solve the problem are relevant. E-mails that consider the functionality and usability of keyboard commands on mobile devises are relevant. E-mails that list the potential flaws and benefits to using mobile mobile devises for keyboard applications are relevant. E-mails that only discuss what different kinds of mobile devises are not relevant. </top> <top> <num> Number: DS107 <title> screen readers <desc> Description: What are the problems and issues related to screen readers? <narr> Narrative: E-mail discussions that mention the various challenges involving screen readers are relevant. However, specific details about the functionality of particular screen reader programs are not relevant. E-mails which do not mention screen readers, or only list information which do not either identify or seek to correct potential issues, are not relevant. </top> <top> <num> Number: DS108 <title> HTML and XHTML <desc> Description: Compare, discuss, comment, critique XHTML in relation to HTML. <narr> Narrative: XHTML introduces XML into the existing HTML Web language. Relevant documents compare the XHTML and HTML, discuss XHTML attributes, XHTML in regard to accessibility, and RDF/XHTML. </top> <top> <num> Number: DS109 <title> OWL ontologies <desc> Description: What are the advantages of OWL for specifying ontologies? <narr> Narrative: Documents that discuss how OWL offers improved facilities for ontology specification are relevant. Discussions regarding the value of proposed new features to OWL are also relevant. Documents that argue for how to keep OWL relevant into the future are relevant. </top> <top> <num> Number: DS110 <title> preferred document language <desc> Description: How does a user get a document served in the preferred language? <narr> Narrative: Relevant documents will discuss language negotiation and how to customize a browser for a preferred language. Documents that discuss the difficulties of language selection and the problems involved with a browser's default language are also relevant. The key is how to get the document in the right language for the user. Not relevant are documents that address the capability of supporting documents in multiple languages. </top>