task
stringlengths 12
101
| input
stringlengths 5
5.87k
| output
stringlengths 1
5.47k
| options
sequence | pageTitle
stringlengths 0
151
| outputColName
stringlengths 1
142
| url
stringlengths 24
147
| wdcFile
stringlengths 71
75
|
|---|---|---|---|---|---|---|---|
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-299 Ian Jacobs [Comment] * Does "link on page" mean that it links to something on the current page, or could it also be a link that points to a different page? * I don't know what "balance" means here. I imagine it means "roughly equal to in number," but it may not be about equality. * Does "depth of navigation" mean "to other pages"? * Do you mean something like "Users tend to give up if they have to follow more than 2-3 links in order to find something." * I hoped I would understand this point better by reading the "What it means" text, but the first sentence is confusing: it uses "navigation links" and "navigate multiple links" as though they mean something different, but the phrases are very similar. [Working Group decision] We have substantially reworded the Best Practice on balance to clarify that the balance was between the number of links per pages and the number of pages the user has to download to go to his or her intended result. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-300 Ian Jacobs [Comment] * You refer to "links"; do you mean "what you get when you follow the link?" * I suggest expressing this point in terms of serving roughly equivalent representations rather than in terms of links. * You might want to citeWebarch section 3.5.1, which says "A URI owner SHOULD provide representations of the identified resource consistently and predictably". * Since this is the "One Web" point, I think it belongs at the front of the document. You might want to retitle it "One Web Principle" rather than "Thematic Consistency". * You might want to simplify to "[One Web Principle] Because you never know for sure who will be reading your content (and their device, browser, and human capabilities), you should start by designing for a broad audience, then optimize your content for targetted audiences." [Working Group decision] We have changed the Best Practice to mention URIs instead of links, and the text now refers to the Web Architecture principle. We have not renamed it since the wording "thematic consistency" is about the expected goal not the implied principle. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-303 Ian Jacobs [Comment] * You might want to shorten this and combine it with the next point as follows:[Describe Link Targets] To help users decide whether to follow a given link, provide this information about the target of the link: * What it is, in clear language * How large it is (which may imply a time-consuming download) * The file format (which the user may know is not supported by the device). * I would note that in UAAG 1.0 we require the user agent to provide some of these services so the author doesn't have to; seecheckpoint 10.5. That helps address part of the goal of the following point about "knowing" whether the device supports a given format. [Working Group decision] We have shortened the best practice by moving it in the explanatory text that also has been clarified. We haven't combined it with link_target_format since we want to to be clear on both these points. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-314 Ian Jacobs [Comment] * Delete "if they can be determined". This is an instance of a qualifier that weighs down the point you are making and should be described elsewhere. [Working Group decision] We have removed the conditional statement since it is indeed taken into account by the default delivery context. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-315 Ian Jacobs [Comment] * What do you mean by "direction"? Do you mean "down, not up"? Do you mean "Don't make people scroll horizontally? * Delete "unless secondary scrolling cannot be avoided." In general, delete "except where impossible" as I've mentioned above. [Working Group decision] We have added the following explanatory paragraph: "The page should lay out so that simple repeated scrolling in the same direction (axis) allows the user to experience all its content." We have kept the opt out clause, with explanations on cases where this might be needed (e.g. a map). [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-316 Ian Jacobs [Comment] * I do not understand how this point differs from the previous one. [Working Group decision] We agreed and removed the second best practice on scrolling. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-321 Ian Jacobs [Comment] * This is another instance of the general point "Don't do X". I think you should regroup all of those points in one and relate them to the default delivery context. [Working Group decision] The Best Practice was dropped, so this comment doesn't apply anymore. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-325 Ian Jacobs [Comment] * Please stick very close to WCAG 2.0 on this one as well. [Working Group decision] WCAG 2.0 is still a Working Draft, so the group has chosen to align with WCAG 1.0 which is a Recommendation. In particular, we have syncronized the text of this BP with the WCAG 1.0 guideline. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-334 Ian Jacobs [Comment] * Perhaps you can be more specific about HTTP (is it "accept" headers?) since that is an explicit assumption above. * The user may wish to receive content even if its device does not directly support it (e.g., to save and use it later). Please make it clear that the user can, on demand, request content that is not supported by software on the client. [Working Group decision] We have clarified that a user should always be able to at least download items (in LINK_TARGET_FORMAT), no matter the level of support his or her device has for the said format. We have also mentioned the various ways one can determine which format is supported or not. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-402 Zev Blut [Comment] 5.2.2 Navigation Bar I am not quite certain if having a navigation bar on the top page and having the navigation links on the same line is really a best practice that I agree with. Perhaps providing a definition or example of what a navigation bar is for a mobile site would help those who disagree with this. In many cases having navigation items like home and back links of the top of the page distracts the user from viewing the content that the user is currently looking for. The user must skip through a number of links before getting the view the content, which is not desirable in some cases. In such an example I think that having the navigation bar at the bottom is preferable when the user has found the searched for content. Although, in the case that the current page is not what the user is looking for having the navigation at the top is certainly better, for the quickness of getting out of the page. Perhaps this section could use a bit more explanation. This may be a difference of interpretation depending upon the if the handsets force the user to traverse each link or can skip links that are on the same line. [Working Group decision] We have clarified that only a few links should be placed at the top of the page, leaving the rest of the navigation links to the bottom, and added a note to the effect that user should be able to see the content of the page without scrolling. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-404 Zev Blut [Comment] 5.4.5 Non Text Items The way that current i-mode handsets deal with handsets that cannot support the object tag differs from this recommendation. This may make many i-mode sites break the best practices rules. You can refer to the following link for more detail: link [Working Group decision] The DoCoMo way of doing this is in the spirit of this BP i.e. the user will receive an appropriate message if his or her phone does not support the OBJECT tag, but we agree that the Best Practice was a worded a bit too restrictively. We have changed the wording of the Best Practice to: [OBJECTS_OR_SCRIPTS] Do not rely on embedded objects and/or scripts. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-407 Zev Blut [Comment] 5.4.14 Cookies Does this prevent systems that make use of Set-Cookie to determine if the phone supports cookies from getting the mobileOK mark? [Working Group decision] We have clarified that we really meant "do not rely on cookies being available"; i.e. it is indeed fine to make use of Set-Cookie to determine if the phone support cookies. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-419 on behalf of I18N WG [Comment] Comment from the i18n review of: link Comment 4 At link Editorial/substantive: E Owner: FS Location in reviewed document: Sec. 1.4 [link] Comment: Please point to the specification XHTML Basic [link] . [Working Group decision] We have added a reference to XHTML Basic. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-420 on behalf of I18N WG [Comment] Comment from the i18n review of: link Comment 5 At link Editorial/substantive: E Owner: FS Location in reviewed document: Sec. 1.6 [link] Comment: This section seems to fit better at the beginning of the document. [Working Group decision] We agreed and moved it to section 1.2 and move the other sections down correspodingly. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-424 on behalf of I18N WG [Comment] Comment from the i18n review of: link Comment 9 At link Editorial/substantive: E Owner: FS Location in reviewed document: Sec. 2.7 [link] Comment: Please correct the line break before \"communications.\". [Working Group decision] We have removed the spurrious line break. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-428 on behalf of I18N WG [Comment] Comment from the i18n review of: link Comment 13 At link Editorial/substantive: E Owner: FS Location in reviewed document: General Comment: CDFWG is in the references, but not in the text. [Working Group decision] This was a Dangling Reference from an earlier version which did make reference to CDF. The reference has been removed. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-430 on behalf of I18N WG [Comment] Comment from the i18n review of: link Comment 15 At link Editorial/substantive: E Owner: FS Location in reviewed document: General Comment: UAProf is mentioned several times in the text, but not in the references. We guess you mean UAProf profile repository [link] . [Working Group decision] Thanks for pointing this out. We have included a reference to the OMA documentation on UAPROF. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-431 on behalf of I18N WG [Comment] Comment from the i18n review of: link Comment 16 At link Editorial/substantive: E Owner: RI Location in reviewed document: Sec. 5.4.12 [link] Comment: Please refer to the tutorial on Character sets & encoding in XHTML, HTML and CSS [link] , and the QA on Setting encoding in web authoring applications [link] , instead of the \"HTTP charset\" document. [Working Group decision] We have added references to these documents. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-438 Al Gilman on behalf of WAI [Comment] section 3.1 which ever content adaptation implementation model is used, the model must retain necessary accessibility information (alt, label, etc.) and convey that information to the mobile device and the user. [Working Group decision] We have added the following note to the section on content adaptation: "Whatever the adaptation model at work, the process of adaptation should not diminish accessibility." [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-371 Bruno von Niman (ANEC W3C) on behalf of ANEC [Comment] Chapter 1.1, Purpose of the Document: The purpose should stretch beyond “…to promote more effective delivery…” and provide design guidelines applicable to the usability and accessibility of the mobile Web or, at least, specifics of interacting with mobile Web sites. [Working Group decision] We agree and have changed the text to read "to improve the user experience of the Web on mobile devices." [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-380 Bruno von Niman (ANEC W3C) on behalf of ANEC [Comment] Chapter 2.7, Advantages: “Connected” should be added to the popularity reasons. [Working Group decision] We have added that aspect to the list of advantages. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-383 Bruno von Niman (ANEC W3C) on behalf of ANEC [Comment] Chapter 5.1.4, Testing: Update the recommendation to “…devices and provided specific software versions…”. [Working Group decision] We have added the suggested mention of software versions. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-386 Bruno von Niman (ANEC W3C) on behalf of ANEC [Comment] Chapter 5.2.4.1, What it means: Connectivity and download speed issues should be mentioned. [Working Group decision] We've added a note to the sentence "irrespective of differences in presentation capabilities": "and access mechanism." [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-342 Charles McCathieNevile on behalf of Opera Software [Comment] This Best Practice should require that content not rely on scripting, unless the delivery context is known to support them. Some mobile browsers allow the user to turn off javascript (handy where you are trying to save battery). It should also lean away from using script unless necessary - it is one of the more battery-intensive ways to do most things. It should also cross-reference requirements on page size, and a best practice on page size vs latency (see Opera's comment on "missing points") cheers Chaals [Working Group decision] We have updated the document to clarify that content should not rely on scripting, and avoid using scripting as much as possible due to battery considerations. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-356 Charles McCathieNevile on behalf of Opera Software [Comment] 1. Meaning The text does not make it clear whether the characteristics are minimum specifications, or actual specifications that should be assumed. For example should a developer assume in the absence of other information that the width of a device is 120 px, or that there may be no more than 120 px width available. [Working Group decision] We have qualified the screen width as being a minimum. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-410 Charles McCathieNevile on behalf of Opera Software [Comment] [This is a comment on Mobile Best Practices, but cc'ed to WCAG as a comment for them on text the are currently using] The wording "Ensure that perceivable structures within the content can be programatically determined", copied verbatim from the WCAG working draft, has proven to be very difficult to understand for the majority of the developers I have ased to comment on this draft (which is only a couple of dozen). Perhaps something more straightforward, like "use markup, properly" is simpler for a title, with the current title moved into the "what it means" session as a couple of sentences. cheers chaals [Working Group decision] We have changed the wording to: "Use features of the markup language to indicate logical document structure." [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-411 Charles McCathieNevile on behalf of Opera Software [Comment] Testing for the absence of tabindex, and the absence of complex layouts (absolute positioning, etc) should also be enough. cheers Chaals [Working Group decision] We have reworded the "how to test" section accordingly. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-412 Charles McCathieNevile on behalf of Opera Software [Comment] Another test for this is to see if there is rendered content that is not inside a table - if there is none, it is quite likely that tables are being used for layout. (Even more so if there is no caption or summary element on the outermost table). cheers Chaals [Working Group decision] We have added a test along these lines in the "what to test" section. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-413 Charles McCathieNevile on behalf of Opera Software [Comment] Rather than the negative "Do not take a least common denominator approach", this could be better phrased as "... to maximise usability" or something similar. It needs to be clear that while thispractise does authorise sending enhanced content to users who are clearly able to make use of it, it does not authorise breaking the "one web" principle and simply ignoring users (provided they have at least a "baseline-capable" device). cheers Chaals [Working Group decision] We have changed the wording to read: "[CAPABILITIES] Exploit device capabilities to provide an enhanced user experience.". [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-258 Ian Jacobs [Comment] Please start early with the "One Web" message, for example by adding something like this to the end of the preceding sentence: "An important Web design principle (discussed, for example, insection 4.3of "Architecture of the World Wide Web") is to design content that is flexible enough to enable a valuable user experience for a variety of devices. This document explains how to design for "one Web" while also optimizing for the mobile experience." [Working Group decision] We have elevated THEMATIC CONSISTENCY to the most prominent in the document and hence have given it the precedence it deserves. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-259 Ian Jacobs [Comment] What does "in context" mean? [Working Group decision] We have removed the incriminated sentence. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-260 Ian Jacobs [Comment] I suggest merging the previous two paragraphs; I otherwise was unsure about the mobileOK trustmark in the paragraph where it was introduced. [Working Group decision] The paragraph boundary was indeed unnecessary and we have merged the two paragraphs accordingly. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-263 Ian Jacobs [Comment] The first reference to "phase of work" is confusing. Does it mean "phase of this WG?" or "phase of this document"? Please clarify. It may be described in [Scope], but I think you need to provide a short summary of what "phasing" means or of what the phases are. [Working Group decision] We have expanded the consideration on phasing and have added a mention of the expected longevity of the document. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-265 Ian Jacobs [Comment] What does "perhaps" mean here? [Working Group decision] We have replaced perhaps by "for example" and "for instance". [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-266 Ian Jacobs [Comment] The document says "as far as is possible." When is it not possible? I think you can safely say that it is considered "best practice not to exclude access." You don't have to add disclaimers. If there are specific cases that you are thinking of (e.g., there may be privacy or security reasons), please call them out rather than say "as far as possible." I make similar comments below. [Working Group decision] We have reworded this to read "not to exclude access from any particular class of device, except where this is necessary because of device limitations." [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-268 Ian Jacobs [Comment] The first sentence confused me because the title of the section includes "context" and the first sentence includes "content". I thought it was a mistake at first. It might help to say very quickly that there are two things discussed; context and content. [Working Group decision] We have reworded the introduction to the default delivery context section and think it sets now more clearly what concerns the content and what concerns the device/context. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-270 Ian Jacobs [Comment] I find "pointer to" to be very informal. [Working Group decision] The incriminated text has been removed. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-271 Ian Jacobs [Comment] I think "Appendices" is more common than "Annexes" in W3C specs. [Working Group decision] We have replaced "annexes" by "appendices". [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-273 Ian Jacobs [Comment] What is an "entertainment application"? Do you mean a game? [Working Group decision] We have reworeded the paragraph to read: "Equally, mobile users are typically less interested in lengthy documents or in browsing. The ergonomics of the device are frequently unsuitable for reading lengthy documents, and users will often only access such information from mobile devices as a last resort, because more convenient access is not available." [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-276 Ian Jacobs [Comment] I am not sure what implicit user identification means. Also, it sounds ominous to me, and therefore I'm not convinced it is always an "advantage". Do you plan to address privacy concerns? [Working Group decision] We have removed the reference to this aspect, as we agreed it's not always something you get with mobile access. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-278 Ian Jacobs [Comment] See also previous comment on "phase"; I suggest a link to where the term is first explained. [Working Group decision] We have added link to the discussion on the phasing of our work. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-279 Ian Jacobs [Comment] I think you can cut this entire section (4.1). The explanations do not add more than the text in the . I find they are not necessary anyway to my understanding of the document. [Working Group decision] We have removed the section accordingly. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-280 Ian Jacobs [Comment] There is an editorial problem around "by using URI reference composed" in the previous paragraph. Also, I think you should use "URI: instead of "URI Reference". [Working Group decision] We have removed the wording altogether and have instead created a list of the best practices with the links pointing to the relevant URIs. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-281 Ian Jacobs [Comment] In both WAI Guidelines and theWebarchdocuments I worked on, we found it useful to provide short mnemonic labels for best practices and similar statements. In Webarch, we created a navigation bar to the statements at the top of the document (after the TOC), so people could access them individually and rapidly. [Working Group decision] We have resolved to keep the labels the same, but we have added a table of BPs. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-296 Ian Jacobs [Comment] You say "how to do it" and then don't say how to do it --- you just say "don't make the user do X." Instead, what about talking about how to configure the server to do the right thing for index.html or similar? [Working Group decision] We agreed with the weakness of the section and have added more detailed advice on shortening URIs. Meanwhile, we keep the specifics of configuring a server to that end for the techniques. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-298 Ian Jacobs [Comment] If "The device will take care of wrapping" is true enough to be stated as you have done, then add a best practice note: "Do not put explicit line breaks in navigation bars because browsers on mobile devices will do the right thing." or something more eloquent. [Working Group decision] We have removed the incriminated sentence. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-301 Ian Jacobs [Comment] * Because the word "use" suggests "user", I recommend making this sound a bit more clearly like it is intended for authors. "Provide navigation mechanisms that are consistent across pages." [If you mean something else, then that's another issue.] [Working Group decision] We have replaced "use" with "provide" as suggested. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-317 Ian Jacobs [Comment] * The key [CENTRAL_MEANING] is less communicative than "Frontload important information". See my earlier comment about using short labels that capture the essence (even if imperfectly) of the point. [Working Group decision] This one is meant to be about not putting banner ads, and other clutter in advance of the text. The "frontloading" aspect is discussed under [CLARITY]; we have added a link from one to the other to highlight their relationship. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-318 Ian Jacobs [Comment] The first sentence of the previous paragraph is more communicative than 5.2.2 as written. [Working Group decision] We have referenced the text of this Best Practice from the text of the best practice on navigation bar, with clarification on why it is important to keep navigation bars short in the mobile context. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-327 Ian Jacobs [Comment] * Why do you use "Always" here and not in other points? I recommend deleting "Always" for the same reason I suggest deleting "when possible". * What about markup languages that don't support this? [Working Group decision] We have removed the word "always" and have instead clarified in the explanatory text that this is an exception to the best practices on relative measures. All the markup languages in scope for this document (XHTML Basic and above) have support for this feature. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-332 Ian Jacobs [Comment] * Delete "as possible", and * Add this to the list of things to "keep short" [Working Group decision] We have removed "as possible". [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-339 Ian Jacobs [Comment] * Perhaps "tab order" is the term of art. Do people use a tab key on mobile devices? In UAAG 1.0 we talk about "sequential navigation" (distinguished from "direct navigation" through keyboard shortcuts). [Working Group decision] We have removed the word "tab" and used a more generic wording about navigation order. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
77acb5fa_hemas_Accessibility___W3C_Wiki__Description | [Expected Values] annotations [Description] | The work includes annotations from the author, instructor and/or others. | [] | WebSchemas/Accessibility - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/Accessibility&oldid=72343 | 12/1438042990114.79_20150728002310-00181-ip-10-236-191-2_809100269_2.json |
77acb5fa_hemas_Accessibility___W3C_Wiki__Description | [Expected Values] bookmarks [Description] | The work includes bookmarks to facilitate navigation to key points. | [] | WebSchemas/Accessibility - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/Accessibility&oldid=72343 | 12/1438042990114.79_20150728002310-00181-ip-10-236-191-2_809100269_2.json |
77acb5fa_hemas_Accessibility___W3C_Wiki__Description | [Expected Values] index [Description] | The work includes an index to the content. | [] | WebSchemas/Accessibility - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/Accessibility&oldid=72343 | 12/1438042990114.79_20150728002310-00181-ip-10-236-191-2_809100269_2.json |
77acb5fa_hemas_Accessibility___W3C_Wiki__Description | [Expected Values] printPageNumbers [Description] | The work includes equivalent print page numbers. This setting is most commonly used with ebooks for which there is a print equivalent. | [] | WebSchemas/Accessibility - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/Accessibility&oldid=72343 | 12/1438042990114.79_20150728002310-00181-ip-10-236-191-2_809100269_2.json |
77acb5fa_hemas_Accessibility___W3C_Wiki__Description | [Expected Values] readingOrder [Description] | The reading order of the content is clearly defined in the markup (e.g., figures, sidebars and other secondary content has been marked up to allow it to be skipped automatically and/or manually escaped from. | [] | WebSchemas/Accessibility - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/Accessibility&oldid=72343 | 12/1438042990114.79_20150728002310-00181-ip-10-236-191-2_809100269_2.json |
77acb5fa_hemas_Accessibility___W3C_Wiki__Description | [Expected Values] structuralNavigation [Description] | The use of headings in the work fully and accurately reflects the document hierarchy, allowing navigation by assistive technologies. | [] | WebSchemas/Accessibility - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/Accessibility&oldid=72343 | 12/1438042990114.79_20150728002310-00181-ip-10-236-191-2_809100269_2.json |
77acb5fa_hemas_Accessibility___W3C_Wiki__Description | [Expected Values] taggedPDF [Description] | The structures in a PDF have been tagged to improve the navigation of the content. | [] | WebSchemas/Accessibility - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/Accessibility&oldid=72343 | 12/1438042990114.79_20150728002310-00181-ip-10-236-191-2_809100269_2.json |
24d63f2d_t_XML_Interchange__EXI__Primer_Table_2_3__EXI_Options_EXI_Option | [Description] Alignment of event codes and content items [EXI Option] | alignment | [
[
"a",
"l",
"i",
"g",
"n",
"m",
"e",
"n",
"t"
],
[
"c",
"o",
"m",
"p",
"r",
"e",
"s",
"s",
"i",
"o",
"n"
],
[
"f",
"r",
"a",
"g",
"m",
"e",
"n",
"t"
],
[
"p",
"r",
"e",
"s",
"e",
"r",
"v",
"e"
],
[
"s",
"c",
"h",
"e",
"m",
"a",
"I",
"D"
],
[
"c",
"o",
"d",
"e",
"c",
"M",
"a",
"p"
],
[
"b",
"l",
"o",
"c",
"k",
"S",
"i",
"z",
"e"
],
[
"[",
"u",
"s",
"e",
"r",
" ",
"d",
"e",
"f",
"i",
"n",
"e",
"d",
"]"
]
] | Efficient XML Interchange (EXI) Primer | EXI Option | http://www.w3.org/TR/2007/WD-exi-primer-20071219/ | 12/1438042990114.79_20150728002310-00250-ip-10-236-191-2_828897262_3.json |
24d63f2d_t_XML_Interchange__EXI__Primer_Table_2_3__EXI_Options_EXI_Option | [Description] Indicates if EXI compression is to be used for better compactness [EXI Option] | compression | [
[
"a",
"l",
"i",
"g",
"n",
"m",
"e",
"n",
"t"
],
[
"c",
"o",
"m",
"p",
"r",
"e",
"s",
"s",
"i",
"o",
"n"
],
[
"f",
"r",
"a",
"g",
"m",
"e",
"n",
"t"
],
[
"p",
"r",
"e",
"s",
"e",
"r",
"v",
"e"
],
[
"s",
"c",
"h",
"e",
"m",
"a",
"I",
"D"
],
[
"c",
"o",
"d",
"e",
"c",
"M",
"a",
"p"
],
[
"b",
"l",
"o",
"c",
"k",
"S",
"i",
"z",
"e"
],
[
"[",
"u",
"s",
"e",
"r",
" ",
"d",
"e",
"f",
"i",
"n",
"e",
"d",
"]"
]
] | Efficient XML Interchange (EXI) Primer | EXI Option | http://www.w3.org/TR/2007/WD-exi-primer-20071219/ | 12/1438042990114.79_20150728002310-00250-ip-10-236-191-2_828897262_3.json |
24d63f2d_t_XML_Interchange__EXI__Primer_Table_2_3__EXI_Options_EXI_Option | [Description] Indicates if the body is to be encoded as an EXI fragment instead of an EXI document [EXI Option] | fragment | [
[
"a",
"l",
"i",
"g",
"n",
"m",
"e",
"n",
"t"
],
[
"c",
"o",
"m",
"p",
"r",
"e",
"s",
"s",
"i",
"o",
"n"
],
[
"f",
"r",
"a",
"g",
"m",
"e",
"n",
"t"
],
[
"p",
"r",
"e",
"s",
"e",
"r",
"v",
"e"
],
[
"s",
"c",
"h",
"e",
"m",
"a",
"I",
"D"
],
[
"c",
"o",
"d",
"e",
"c",
"M",
"a",
"p"
],
[
"b",
"l",
"o",
"c",
"k",
"S",
"i",
"z",
"e"
],
[
"[",
"u",
"s",
"e",
"r",
" ",
"d",
"e",
"f",
"i",
"n",
"e",
"d",
"]"
]
] | Efficient XML Interchange (EXI) Primer | EXI Option | http://www.w3.org/TR/2007/WD-exi-primer-20071219/ | 12/1438042990114.79_20150728002310-00250-ip-10-236-191-2_828897262_3.json |
24d63f2d_t_XML_Interchange__EXI__Primer_Table_2_3__EXI_Options_EXI_Option | [Description] A set of options that controls whether comments, processing instructions, etc. are preserved [EXI Option] | preserve | [
[
"a",
"l",
"i",
"g",
"n",
"m",
"e",
"n",
"t"
],
[
"c",
"o",
"m",
"p",
"r",
"e",
"s",
"s",
"i",
"o",
"n"
],
[
"f",
"r",
"a",
"g",
"m",
"e",
"n",
"t"
],
[
"p",
"r",
"e",
"s",
"e",
"r",
"v",
"e"
],
[
"s",
"c",
"h",
"e",
"m",
"a",
"I",
"D"
],
[
"c",
"o",
"d",
"e",
"c",
"M",
"a",
"p"
],
[
"b",
"l",
"o",
"c",
"k",
"S",
"i",
"z",
"e"
],
[
"[",
"u",
"s",
"e",
"r",
" ",
"d",
"e",
"f",
"i",
"n",
"e",
"d",
"]"
]
] | Efficient XML Interchange (EXI) Primer | EXI Option | http://www.w3.org/TR/2007/WD-exi-primer-20071219/ | 12/1438042990114.79_20150728002310-00250-ip-10-236-191-2_828897262_3.json |
24d63f2d_t_XML_Interchange__EXI__Primer_Table_2_3__EXI_Options_EXI_Option | [Description] Identifies the schema used during encoding [EXI Option] | schemaID | [
[
"a",
"l",
"i",
"g",
"n",
"m",
"e",
"n",
"t"
],
[
"c",
"o",
"m",
"p",
"r",
"e",
"s",
"s",
"i",
"o",
"n"
],
[
"f",
"r",
"a",
"g",
"m",
"e",
"n",
"t"
],
[
"p",
"r",
"e",
"s",
"e",
"r",
"v",
"e"
],
[
"s",
"c",
"h",
"e",
"m",
"a",
"I",
"D"
],
[
"c",
"o",
"d",
"e",
"c",
"M",
"a",
"p"
],
[
"b",
"l",
"o",
"c",
"k",
"S",
"i",
"z",
"e"
],
[
"[",
"u",
"s",
"e",
"r",
" ",
"d",
"e",
"f",
"i",
"n",
"e",
"d",
"]"
]
] | Efficient XML Interchange (EXI) Primer | EXI Option | http://www.w3.org/TR/2007/WD-exi-primer-20071219/ | 12/1438042990114.79_20150728002310-00250-ip-10-236-191-2_828897262_3.json |
24d63f2d_t_XML_Interchange__EXI__Primer_Table_2_3__EXI_Options_EXI_Option | [Description] Identifies any pluggable CODECs used to encode the body [EXI Option] | codecMap | [
[
"a",
"l",
"i",
"g",
"n",
"m",
"e",
"n",
"t"
],
[
"c",
"o",
"m",
"p",
"r",
"e",
"s",
"s",
"i",
"o",
"n"
],
[
"f",
"r",
"a",
"g",
"m",
"e",
"n",
"t"
],
[
"p",
"r",
"e",
"s",
"e",
"r",
"v",
"e"
],
[
"s",
"c",
"h",
"e",
"m",
"a",
"I",
"D"
],
[
"c",
"o",
"d",
"e",
"c",
"M",
"a",
"p"
],
[
"b",
"l",
"o",
"c",
"k",
"S",
"i",
"z",
"e"
],
[
"[",
"u",
"s",
"e",
"r",
" ",
"d",
"e",
"f",
"i",
"n",
"e",
"d",
"]"
]
] | Efficient XML Interchange (EXI) Primer | EXI Option | http://www.w3.org/TR/2007/WD-exi-primer-20071219/ | 12/1438042990114.79_20150728002310-00250-ip-10-236-191-2_828897262_3.json |
24d63f2d_t_XML_Interchange__EXI__Primer_Table_2_3__EXI_Options_EXI_Option | [Description] Specifies the block size used for EXI compression [EXI Option] | blockSize | [
[
"a",
"l",
"i",
"g",
"n",
"m",
"e",
"n",
"t"
],
[
"c",
"o",
"m",
"p",
"r",
"e",
"s",
"s",
"i",
"o",
"n"
],
[
"f",
"r",
"a",
"g",
"m",
"e",
"n",
"t"
],
[
"p",
"r",
"e",
"s",
"e",
"r",
"v",
"e"
],
[
"s",
"c",
"h",
"e",
"m",
"a",
"I",
"D"
],
[
"c",
"o",
"d",
"e",
"c",
"M",
"a",
"p"
],
[
"b",
"l",
"o",
"c",
"k",
"S",
"i",
"z",
"e"
],
[
"[",
"u",
"s",
"e",
"r",
" ",
"d",
"e",
"f",
"i",
"n",
"e",
"d",
"]"
]
] | Efficient XML Interchange (EXI) Primer | EXI Option | http://www.w3.org/TR/2007/WD-exi-primer-20071219/ | 12/1438042990114.79_20150728002310-00250-ip-10-236-191-2_828897262_3.json |
24d63f2d_t_XML_Interchange__EXI__Primer_Table_2_3__EXI_Options_EXI_Option | [Description] User defined headers may be added [EXI Option] | [user defined] | [
[
"a",
"l",
"i",
"g",
"n",
"m",
"e",
"n",
"t"
],
[
"c",
"o",
"m",
"p",
"r",
"e",
"s",
"s",
"i",
"o",
"n"
],
[
"f",
"r",
"a",
"g",
"m",
"e",
"n",
"t"
],
[
"p",
"r",
"e",
"s",
"e",
"r",
"v",
"e"
],
[
"s",
"c",
"h",
"e",
"m",
"a",
"I",
"D"
],
[
"c",
"o",
"d",
"e",
"c",
"M",
"a",
"p"
],
[
"b",
"l",
"o",
"c",
"k",
"S",
"i",
"z",
"e"
],
[
"[",
"u",
"s",
"e",
"r",
" ",
"d",
"e",
"f",
"i",
"n",
"e",
"d",
"]"
]
] | Efficient XML Interchange (EXI) Primer | EXI Option | http://www.w3.org/TR/2007/WD-exi-primer-20071219/ | 12/1438042990114.79_20150728002310-00250-ip-10-236-191-2_828897262_3.json |
bc03c2f0_t_XML_Interchange__EXI__Format_XI_Options_in_Options_Document_EXI_Option | [Description] Alignment of event codes and content items [Default Value] bit-packed [EXI Option] | alignment | [] | Efficient XML Interchange (EXI) Format | EXI Option | http://www.w3.org/TR/2011/REC-exi-20110310/exi.xml | 12/1438042981460.12_20150728002301-00145-ip-10-236-191-2_816112923_10.json |
bc03c2f0_t_XML_Interchange__EXI__Format_XI_Options_in_Options_Document_EXI_Option | [Description] EXI compression is used to achieve better compactness [Default Value] false [EXI Option] | compression | [] | Efficient XML Interchange (EXI) Format | EXI Option | http://www.w3.org/TR/2011/REC-exi-20110310/exi.xml | 12/1438042981460.12_20150728002301-00145-ip-10-236-191-2_816112923_10.json |
bc03c2f0_t_XML_Interchange__EXI__Format_XI_Options_in_Options_Document_EXI_Option | [Description] Strict interpretation of schemas is used to achieve better compactness [Default Value] false [EXI Option] | strict | [] | Efficient XML Interchange (EXI) Format | EXI Option | http://www.w3.org/TR/2011/REC-exi-20110310/exi.xml | 12/1438042981460.12_20150728002301-00145-ip-10-236-191-2_816112923_10.json |
bc03c2f0_t_XML_Interchange__EXI__Format_XI_Options_in_Options_Document_EXI_Option | [Description] Body is encoded as an EXI fragment instead of an EXI document [Default Value] false [EXI Option] | fragment | [] | Efficient XML Interchange (EXI) Format | EXI Option | http://www.w3.org/TR/2011/REC-exi-20110310/exi.xml | 12/1438042981460.12_20150728002301-00145-ip-10-236-191-2_816112923_10.json |
bc03c2f0_t_XML_Interchange__EXI__Format_XI_Options_in_Options_Document_EXI_Option | [Description] Specifies whether the support for the preservation of comments, pis, etc. is each enabled [Default Value] all false [EXI Option] | preserve | [] | Efficient XML Interchange (EXI) Format | EXI Option | http://www.w3.org/TR/2011/REC-exi-20110310/exi.xml | 12/1438042981460.12_20150728002301-00145-ip-10-236-191-2_816112923_10.json |
bc03c2f0_t_XML_Interchange__EXI__Format_XI_Options_in_Options_Document_EXI_Option | [Description] Enables self-contained elements [Default Value] false [EXI Option] | selfContained | [] | Efficient XML Interchange (EXI) Format | EXI Option | http://www.w3.org/TR/2011/REC-exi-20110310/exi.xml | 12/1438042981460.12_20150728002301-00145-ip-10-236-191-2_816112923_10.json |
bc03c2f0_t_XML_Interchange__EXI__Format_XI_Options_in_Options_Document_EXI_Option | [Description] Identify the schema information, if any, used to encode the body [Default Value] no default value [EXI Option] | schemaId | [] | Efficient XML Interchange (EXI) Format | EXI Option | http://www.w3.org/TR/2011/REC-exi-20110310/exi.xml | 12/1438042981460.12_20150728002301-00145-ip-10-236-191-2_816112923_10.json |
bc03c2f0_t_XML_Interchange__EXI__Format_XI_Options_in_Options_Document_EXI_Option | [Description] Specify alternate datatype representations for typed values in the EXI body [Default Value] no default value [EXI Option] | datatypeRepresentationMap | [] | Efficient XML Interchange (EXI) Format | EXI Option | http://www.w3.org/TR/2011/REC-exi-20110310/exi.xml | 12/1438042981460.12_20150728002301-00145-ip-10-236-191-2_816112923_10.json |
bc03c2f0_t_XML_Interchange__EXI__Format_XI_Options_in_Options_Document_EXI_Option | [Description] Specifies the block size used for EXI compression [Default Value] 1,000,000 [EXI Option] | blockSize | [] | Efficient XML Interchange (EXI) Format | EXI Option | http://www.w3.org/TR/2011/REC-exi-20110310/exi.xml | 12/1438042981460.12_20150728002301-00145-ip-10-236-191-2_816112923_10.json |
bc03c2f0_t_XML_Interchange__EXI__Format_XI_Options_in_Options_Document_EXI_Option | [Description] Specifies the maximum string length of value content items to be considered for addition to the string table. [Default Value] unbounded [EXI Option] | valueMaxLength | [] | Efficient XML Interchange (EXI) Format | EXI Option | http://www.w3.org/TR/2011/REC-exi-20110310/exi.xml | 12/1438042981460.12_20150728002301-00145-ip-10-236-191-2_816112923_10.json |
bc03c2f0_t_XML_Interchange__EXI__Format_XI_Options_in_Options_Document_EXI_Option | [Description] Specifies the total capacity of value partitions in a string table [Default Value] unbounded [EXI Option] | valuePartitionCapacity | [] | Efficient XML Interchange (EXI) Format | EXI Option | http://www.w3.org/TR/2011/REC-exi-20110310/exi.xml | 12/1438042981460.12_20150728002301-00145-ip-10-236-191-2_816112923_10.json |
bc03c2f0_t_XML_Interchange__EXI__Format_XI_Options_in_Options_Document_EXI_Option | [Description] User defined meta-data may be added [Default Value] no default value [EXI Option] | [user defined meta-data] | [] | Efficient XML Interchange (EXI) Format | EXI Option | http://www.w3.org/TR/2011/REC-exi-20110310/exi.xml | 12/1438042981460.12_20150728002301-00145-ip-10-236-191-2_816112923_10.json |
7407a4f5_nd_Operators____Review_Version__Meaning | [Function] op:to [Meaning] | Returns the sequence containing every xs:integer between the values of the operands. | [] | XQuery 1.0 and XPath 2.0 Functions and Operators -- Review Version | Meaning | http://www.w3.org/TR/2005/CR-xpath-functions-20051103/diff-from-20050915.html | 12/1438042981460.12_20150728002301-00188-ip-10-236-191-2_826528506_92.json |
7407a4f5_nd_Operators____Review_Version__Meaning | [Function] fn:id [Meaning] | Returns the sequence of element nodes having an ID value matching the one or more of the supplied IDREF values. | [] | XQuery 1.0 and XPath 2.0 Functions and Operators -- Review Version | Meaning | http://www.w3.org/TR/2005/CR-xpath-functions-20051103/diff-from-20050915.html | 12/1438042981460.12_20150728002301-00188-ip-10-236-191-2_826528506_92.json |
7407a4f5_nd_Operators____Review_Version__Meaning | [Function] fn:idref [Meaning] | Returns the sequence of element or attribute nodes with an IDREF value matching one or more of the supplied ID values. | [] | XQuery 1.0 and XPath 2.0 Functions and Operators -- Review Version | Meaning | http://www.w3.org/TR/2005/CR-xpath-functions-20051103/diff-from-20050915.html | 12/1438042981460.12_20150728002301-00188-ip-10-236-191-2_826528506_92.json |
7407a4f5_nd_Operators____Review_Version__Meaning | [Function] fn:doc [Meaning] | Returns a document node retrieved using the specified URI. | [] | XQuery 1.0 and XPath 2.0 Functions and Operators -- Review Version | Meaning | http://www.w3.org/TR/2005/CR-xpath-functions-20051103/diff-from-20050915.html | 12/1438042981460.12_20150728002301-00188-ip-10-236-191-2_826528506_92.json |
7407a4f5_nd_Operators____Review_Version__Meaning | [Function] fn:doc-available [Meaning] | Returns true if a document node can be retrieved using the specified URI. | [] | XQuery 1.0 and XPath 2.0 Functions and Operators -- Review Version | Meaning | http://www.w3.org/TR/2005/CR-xpath-functions-20051103/diff-from-20050915.html | 12/1438042981460.12_20150728002301-00188-ip-10-236-191-2_826528506_92.json |
7407a4f5_nd_Operators____Review_Version__Meaning | [Function] fn:collection [Meaning] | Returns a sequence of nodes retrieved using the specified URI or the nodes in the default collection. | [] | XQuery 1.0 and XPath 2.0 Functions and Operators -- Review Version | Meaning | http://www.w3.org/TR/2005/CR-xpath-functions-20051103/diff-from-20050915.html | 12/1438042981460.12_20150728002301-00188-ip-10-236-191-2_826528506_92.json |
0ae798b0_Indexed_Database_API__Message__Optional_ | [Type] NotFoundError [Message (Optional)] | The operation failed because the requested database object could not be found. For example, an object store did not exist but was being opened. | [] | Indexed Database API | Message (Optional) | http://www.w3.org/TR/IndexedDB/ | 12/1438042990114.79_20150728002310-00326-ip-10-236-191-2_821994982_8.json |
0ae798b0_Indexed_Database_API__Message__Optional_ | [Type] InvalidStateError [Message (Optional)] | An operation was called on an object on which it is not allowed or at a time when it is not allowed. Also occurs if a request is made on a source object that has been deleted or removed. Use TransactionInactiveError or ReadOnlyError when possible, as they are more specific variations of InvalidStateError. | [] | Indexed Database API | Message (Optional) | http://www.w3.org/TR/IndexedDB/ | 12/1438042990114.79_20150728002310-00326-ip-10-236-191-2_821994982_8.json |
0ae798b0_Indexed_Database_API__Message__Optional_ | [Type] InvalidAccessError [Message (Optional)] | An invalid operation was performed on an object. For example transaction creation attempt was made, but an empty scope was provided. | [] | Indexed Database API | Message (Optional) | http://www.w3.org/TR/IndexedDB/ | 12/1438042990114.79_20150728002310-00326-ip-10-236-191-2_821994982_8.json |
0ae798b0_Indexed_Database_API__Message__Optional_ | [Type] AbortError [Message (Optional)] | A request was aborted, for example through a call to IDBTransaction.abort. | [] | Indexed Database API | Message (Optional) | http://www.w3.org/TR/IndexedDB/ | 12/1438042990114.79_20150728002310-00326-ip-10-236-191-2_821994982_8.json |
0ae798b0_Indexed_Database_API__Message__Optional_ | [Type] TimeoutError [Message (Optional)] | A lock for the transaction could not be obtained in a reasonable time. | [] | Indexed Database API | Message (Optional) | http://www.w3.org/TR/IndexedDB/ | 12/1438042990114.79_20150728002310-00326-ip-10-236-191-2_821994982_8.json |
0ae798b0_Indexed_Database_API__Message__Optional_ | [Type] QuotaExceededError [Message (Optional)] | The operation failed because there was not enough remaining storage space, or the storage quota was reached and the user declined to give more space to the database. | [] | Indexed Database API | Message (Optional) | http://www.w3.org/TR/IndexedDB/ | 12/1438042990114.79_20150728002310-00326-ip-10-236-191-2_821994982_8.json |
0ae798b0_Indexed_Database_API__Message__Optional_ | [Type] SyntaxError [Message (Optional)] | The keypath argument contains an invalid key path. | [] | Indexed Database API | Message (Optional) | http://www.w3.org/TR/IndexedDB/ | 12/1438042990114.79_20150728002310-00326-ip-10-236-191-2_821994982_8.json |
0ae798b0_Indexed_Database_API__Message__Optional_ | [Type] DataCloneError [Message (Optional)] | The data being stored could not be cloned by the internal structured cloning algorithm. | [] | Indexed Database API | Message (Optional) | http://www.w3.org/TR/IndexedDB/ | 12/1438042990114.79_20150728002310-00326-ip-10-236-191-2_821994982_8.json |
6c39c59b_mas_VacationRentals___W3C_Wiki__Description | [Property] address [Expected Type] PostalAddress [Description] | Physical address of the item. | [] | WebSchemas/VacationRentals - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/VacationRentals&oldid=63381 | 12/1438042990114.79_20150728002310-00225-ip-10-236-191-2_817723111_0.json |
6c39c59b_mas_VacationRentals___W3C_Wiki__Description | [Property] aggregateRating [Expected Type] aggregateRating [Description] | The overall rating, based on a collection of reviews or ratings, of the item. | [] | WebSchemas/VacationRentals - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/VacationRentals&oldid=63381 | 12/1438042990114.79_20150728002310-00225-ip-10-236-191-2_817723111_0.json |
6c39c59b_mas_VacationRentals___W3C_Wiki__Description | [Property] geo [Expected Type] GeoCoordinates or GeoShape [Description] | The geo coordinates of the place. | [] | WebSchemas/VacationRentals - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/VacationRentals&oldid=63381 | 12/1438042990114.79_20150728002310-00225-ip-10-236-191-2_817723111_0.json |
6c39c59b_mas_VacationRentals___W3C_Wiki__Description | [Property] map [Expected Type] URL [Description] | A URL to a map of the place. | [] | WebSchemas/VacationRentals - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/VacationRentals&oldid=63381 | 12/1438042990114.79_20150728002310-00225-ip-10-236-191-2_817723111_0.json |
6c39c59b_mas_VacationRentals___W3C_Wiki__Description | [Property] photos [Expected Type] ImageObject or Photograph [Description] | Photographs of this place | [] | WebSchemas/VacationRentals - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/VacationRentals&oldid=63381 | 12/1438042990114.79_20150728002310-00225-ip-10-236-191-2_817723111_0.json |
6c39c59b_mas_VacationRentals___W3C_Wiki__Description | [Property] reviews [Expected Type] Review [Description] | Review of the item | [] | WebSchemas/VacationRentals - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/VacationRentals&oldid=63381 | 12/1438042990114.79_20150728002310-00225-ip-10-236-191-2_817723111_0.json |
6c39c59b_mas_VacationRentals___W3C_Wiki__Description | [Property] telephone [Expected Type] Text [Description] | The telephone number. | [] | WebSchemas/VacationRentals - W3C Wiki | Description | http://www.w3.org/wiki/index.php?title=WebSchemas/VacationRentals&oldid=63381 | 12/1438042990114.79_20150728002310-00225-ip-10-236-191-2_817723111_0.json |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.