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
|
|---|---|---|---|---|---|---|---|
82a7638f_ltimodal_Interaction_Use_Cases__Resulting_Action | [User Action/External Input] GPS Input at regular intervals (indicating driver is off course) [Action on Device] N/A [Event Description] GPS_Data_In Event [Event Handler] Device processes location data and determines that user is off course [Resulting Action] | Map on graphical display is updated and textual message is displayed indicating that route is not correct. Prompt is played from the device indicating that route is being recalculated | [] | Multimodal Interaction Use Cases | Resulting Action | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
82a7638f_ltimodal_Interaction_Use_Cases__Resulting_Action | [User Action/External Input] N/A [Action on Device] Route request is sent to app server including new location data [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Event Handler] App Server processes input and returns data to device [Resulting Action] | Device processes results and updates graphical display with route and directions highlighting next step | [] | Multimodal Interaction Use Cases | Resulting Action | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
82a7638f_ltimodal_Interaction_Use_Cases__Resulting_Action | [User Action/External Input] Alert received on device based on traffic conditions [Action on Device] N/A [Event Description] Route_Change Alert [Event Handler] Device processes event and initiates dialog to determine if route should be recalculated [Resulting Action] | User is informed of traffic conditions and asked whether route should be recalculated. | [] | Multimodal Interaction Use Cases | Resulting Action | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
82a7638f_ltimodal_Interaction_Use_Cases__Resulting_Action | [User Action/External Input] User requests recalculation of route based on current traffic conditions [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Event Handler] App Server processes input and returns data to device [Resulting Action] | Device processes results and updates graphical display with route and directions highlighting next step | [] | Multimodal Interaction Use Cases | Resulting Action | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
82a7638f_ltimodal_Interaction_Use_Cases__Resulting_Action | [User Action/External Input] User presses button on steering wheel [Action on Device] Connection to ASR server is established [Event Description] Start_Listening Event [Event Handler] ASR Server receives request and establishes connection [Resulting Action] | User hears acknowledgement prompt for continuation, and "listening" icon appears on display | [] | Multimodal Interaction Use Cases | Resulting Action | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
82a7638f_ltimodal_Interaction_Use_Cases__Resulting_Action | [User Action/External Input] User requests new destination by destination type while still depressing button on steering wheel (may improve recognition accuracy by sending grammar constraints to server based on a local dialog with the user) [Action on Device] N/A [Event Description] N/A [Event Handler] ASR Server processes speech and returns results to device [Resulting Action] | Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display | [] | Multimodal Interaction Use Cases | Resulting Action | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
82a7638f_ltimodal_Interaction_Use_Cases__Resulting_Action | [User Action/External Input] User confirms destination via a multiple interaction dialog to determine exact destination [Action on Device] Device executes dialog based on user responses (using local ASR Processing) and accesses app server as needed [Event Description] HTTP requests to app server for dialog and data specific to user response [Event Handler] App server responds with appropriate dialog [Resulting Action] | User interacts in a dialog and selects destination. User is asked whether this is a new destination | [] | Multimodal Interaction Use Cases | Resulting Action | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
82a7638f_ltimodal_Interaction_Use_Cases__Resulting_Action | [User Action/External Input] User indicates that this is a stop on the way to original destination [Action on Device] Devices sends updated destination information to app server [Event Description] HTTP Request for updated directions (based on current location, detour destination, and ultimate destination) [Event Handler] App Server processes input and returns data to device [Resulting Action] | Device processes results and updates graphical display with new route and directions highlighting next step | [] | Multimodal Interaction Use Cases | Resulting Action | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] User presses button on steering wheel [Event Description] HTTP Request to app server [Event Handler] App server returns initial page to device [Resulting Action] Welcome prompts are played. Authentication dialog is initiated (may be initiated via speaker identification or key identification). [Action on Device] | Service is initiated and GPS satellite detection begins | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] User interacts in an authentication dialog [Event Description] HTTP Request to app server which includes user credentials [Event Handler] App server returns initial page to device including user preferences [Resulting Action] User is prompted for a destination (if additional services are availble after authentication, assume that user selects driving direction application) [Action on Device] | Device executes authentication dialog using local ASR processing | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] Initial GPS Input [Event Description] GPS_Data_In Event [Event Handler] Device handles location information [Resulting Action] Device updates map on graphical display (assumes all maps are stored locally on device) [Action on Device] | N/A | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] User selects option to change volume of on-board unit using touch display. [Event Description] Touch_screen_event (includes x, y coordinates) [Event Handler] Touch screen detects and processes input [Resulting Action] Volume indicator changes on screen. Volume of speech output is changed [Action on Device] | N/A | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] User presses button on steering wheel [Event Description] Start_Listening Event [Event Handler] ASR Server receives request and establishes connection [Resulting Action] "listening" icon appears on display (utterances prior to establishing the connection are buffered) [Action on Device] | Device initiates connection to ASR server | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] User says destination address (may improve recognition accuracy by sending grammar constraints to server based on a local dialog with the user instead of allowing any address from the start) [Event Description] N/A [Event Handler] ASR Server processes speech and returns results to device [Resulting Action] Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display [Action on Device] | N/A | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] User confirms destination [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Action on Device] | Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] GPS Input at regular intervals [Event Description] GPS_Data_In Event [Event Handler] Device processes location data and checks if location milestone is hit [Resulting Action] Device updates map on graphical display (assumes all maps are stored locally on device) and highlights current step. When milestone is hit, next instruction is played to user [Action on Device] | N/A | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] GPS Input at regular intervals (indicating driver is off course) [Event Description] GPS_Data_In Event [Event Handler] Device processes location data and determines that user is off course [Resulting Action] Map on graphical display is updated and textual message is displayed indicating that route is not correct. Prompt is played from the device indicating that route is being recalculated [Action on Device] | N/A | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] N/A [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Action on Device] | Route request is sent to app server including new location data | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] Alert received on device based on traffic conditions [Event Description] Route_Change Alert [Event Handler] Device processes event and initiates dialog to determine if route should be recalculated [Resulting Action] User is informed of traffic conditions and asked whether route should be recalculated. [Action on Device] | N/A | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] User requests recalculation of route based on current traffic conditions [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Action on Device] | Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] User presses button on steering wheel [Event Description] Start_Listening Event [Event Handler] ASR Server receives request and establishes connection [Resulting Action] User hears acknowledgement prompt for continuation, and "listening" icon appears on display [Action on Device] | Connection to ASR server is established | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] User requests new destination by destination type while still depressing button on steering wheel (may improve recognition accuracy by sending grammar constraints to server based on a local dialog with the user) [Event Description] N/A [Event Handler] ASR Server processes speech and returns results to device [Resulting Action] Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display [Action on Device] | N/A | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] User confirms destination via a multiple interaction dialog to determine exact destination [Event Description] HTTP requests to app server for dialog and data specific to user response [Event Handler] App server responds with appropriate dialog [Resulting Action] User interacts in a dialog and selects destination. User is asked whether this is a new destination [Action on Device] | Device executes dialog based on user responses (using local ASR Processing) and accesses app server as needed | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
ccf1477c_ltimodal_Interaction_Use_Cases__Action_on_Device | [User Action/External Input] User indicates that this is a stop on the way to original destination [Event Description] HTTP Request for updated directions (based on current location, detour destination, and ultimate destination) [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with new route and directions highlighting next step [Action on Device] | Devices sends updated destination information to app server | [] | Multimodal Interaction Use Cases | Action on Device | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] User presses button on steering wheel [Action on Device] Service is initiated and GPS satellite detection begins [Event Handler] App server returns initial page to device [Resulting Action] Welcome prompts are played. Authentication dialog is initiated (may be initiated via speaker identification or key identification). [Event Description] | HTTP Request to app server | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] User interacts in an authentication dialog [Action on Device] Device executes authentication dialog using local ASR processing [Event Handler] App server returns initial page to device including user preferences [Resulting Action] User is prompted for a destination (if additional services are availble after authentication, assume that user selects driving direction application) [Event Description] | HTTP Request to app server which includes user credentials | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] Initial GPS Input [Action on Device] N/A [Event Handler] Device handles location information [Resulting Action] Device updates map on graphical display (assumes all maps are stored locally on device) [Event Description] | GPS_Data_In Event | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] User selects option to change volume of on-board unit using touch display. [Action on Device] N/A [Event Handler] Touch screen detects and processes input [Resulting Action] Volume indicator changes on screen. Volume of speech output is changed [Event Description] | Touch_screen_event (includes x, y coordinates) | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] User presses button on steering wheel [Action on Device] Device initiates connection to ASR server [Event Handler] ASR Server receives request and establishes connection [Resulting Action] "listening" icon appears on display (utterances prior to establishing the connection are buffered) [Event Description] | Start_Listening Event | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] User says destination address (may improve recognition accuracy by sending grammar constraints to server based on a local dialog with the user instead of allowing any address from the start) [Action on Device] N/A [Event Handler] ASR Server processes speech and returns results to device [Resulting Action] Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display [Event Description] | N/A | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] User confirms destination [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Event Description] | HTTP Request is sent to app server (includes current location and destination information) | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] GPS Input at regular intervals [Action on Device] N/A [Event Handler] Device processes location data and checks if location milestone is hit [Resulting Action] Device updates map on graphical display (assumes all maps are stored locally on device) and highlights current step. When milestone is hit, next instruction is played to user [Event Description] | GPS_Data_In Event | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] GPS Input at regular intervals (indicating driver is off course) [Action on Device] N/A [Event Handler] Device processes location data and determines that user is off course [Resulting Action] Map on graphical display is updated and textual message is displayed indicating that route is not correct. Prompt is played from the device indicating that route is being recalculated [Event Description] | GPS_Data_In Event | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] N/A [Action on Device] Route request is sent to app server including new location data [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Event Description] | HTTP Request is sent to app server (includes current location and destination information) | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] Alert received on device based on traffic conditions [Action on Device] N/A [Event Handler] Device processes event and initiates dialog to determine if route should be recalculated [Resulting Action] User is informed of traffic conditions and asked whether route should be recalculated. [Event Description] | Route_Change Alert | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] User requests recalculation of route based on current traffic conditions [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Event Description] | HTTP Request is sent to app server (includes current location and destination information) | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] User presses button on steering wheel [Action on Device] Connection to ASR server is established [Event Handler] ASR Server receives request and establishes connection [Resulting Action] User hears acknowledgement prompt for continuation, and "listening" icon appears on display [Event Description] | Start_Listening Event | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] User requests new destination by destination type while still depressing button on steering wheel (may improve recognition accuracy by sending grammar constraints to server based on a local dialog with the user) [Action on Device] N/A [Event Handler] ASR Server processes speech and returns results to device [Resulting Action] Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display [Event Description] | N/A | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] User confirms destination via a multiple interaction dialog to determine exact destination [Action on Device] Device executes dialog based on user responses (using local ASR Processing) and accesses app server as needed [Event Handler] App server responds with appropriate dialog [Resulting Action] User interacts in a dialog and selects destination. User is asked whether this is a new destination [Event Description] | HTTP requests to app server for dialog and data specific to user response | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
29be99bf_ltimodal_Interaction_Use_Cases__Event_Description | [User Action/External Input] User indicates that this is a stop on the way to original destination [Action on Device] Devices sends updated destination information to app server [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with new route and directions highlighting next step [Event Description] | HTTP Request for updated directions (based on current location, detour destination, and ultimate destination) | [] | Multimodal Interaction Use Cases | Event Description | http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/ | 6/1438042981576.7_20150728002301-00270-ip-10-236-191-2_813693905_4.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 1. A method of distributing content, comprising: creating a cryptographic hash of at least a portion of content; creating a ticket file including the cryptographic hash; and distributing the ticket file to a user system. | WARP does not make use of any cryptographic information. WARP does not create a ticket file including the cryptographic hash. WARP does not distribute a ticket file to a user system or anything to the system. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 2. The method of claim 1, where creating a ticket file comprises: including in the ticket file information relating to downloading the content from a distribution site over the network; digitally signing the ticket file; receiving a request for the content from the user system; and sending the user system the ticket file separate from the content. | WARP does nothing relating to the above | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 3. The method of claim 1, further comprising: receiving notification from the user system that verification of the digital signature has failed; and initiating a security action in response to the notification. | WARP does not make use of digital signatures. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 4. The method of claim 3, where initiating a security action comprises: initiating a revocation service. | WARP has no relation to initializing revocation services. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 5. The method of claim 3, where initiating a security action comprises: preventing user systems from downloading the content. | WARP does not rely in cryptographic methods to prevent user systems from downloading content. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 6. A method of downloading content from a network, comprising: sending a request for content to a content aggregator site; and receiving from the content aggregator site a digitally signed ticket file including a first cryptographic hash of at least a portion of content. | WARP does not download any content. WARP does not make use of any cryptographic hashes or any cryptography. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 7. The method of claim 6, further comprising: downloading the content to a user system over a network, where the content is downloaded separately from the ticket file; and verifying the digital signature of the ticket file. | WARP has no relationship to digital signatures or ticket files. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 8. The method of claim 7, where verifying the digital signature comprises: creating a second cryptographic hash of the downloaded content; comparing the second cryptographic hash with the first cryptographic hash; and if the hashes do not match, initiating a security action. | See above 7. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 9. The method of claim 8, where initiating a security action comprises: deleting the content from the user system. WARP does not interact with the user's system. | WARP does not have the ability to demand that, or have any provisions that would require, content be deleted from the user's system. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 10. The method of claim 8, where initiating a security action comprises: notifying the content aggregator site of a failed verification if the hashes do not match; and receiving a command for revoking the digital signature of the ticket file. | WARP has no means to contact other sites on failure. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 11. The method of claim 8, where initiating a security action comprises: scanning the user system for instances of revoked content. | WARP most definitely does not have any provisions to scan the user's hard drive deleting content | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 12. The method of claim 1, further comprising: creating a security log on the user system that includes a history of content installation | WARP does not write anything to the user's hard drive or do any privacy violating things like keeping records of stuff on user's hard drives. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 13. A computer-readable medium having stored thereon instructions which, when executed by a processor, causes the processor to perform the operations of: creating a cryptographic hash of at least a portion of content; creating a ticket file including the cryptographic hash; and distributing the ticket file to a user system. | WARP does not cryptographically do anything… specially nothing relating to content. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 14. The computer-readable medium of claim 13, where creating a ticket file comprises: including in the ticket file information relating to downloading the content from a distribution site over the network; digitally signing the ticket file; receiving a request for the content from the user system; and sending the user system the ticket file separate from the content. | WARP does not cryptographically do anything… specially nothing relating to content. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 15. The computer-readable medium of claim 13, further comprising: receiving notification from the user system that verification of the digital signature has failed; and initiating a security action in response to the notification. | WARP has nothing to do with digital signatures or events based on signatures failing of being verified. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 16. The computer-readable medium of claim 15, where initiating a security action comprises: initiating a revocation service. | WARP has nothing to do with digital signatures or events based on signatures failing of being verified. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 17. The computer-readable medium of claim 15, where initiating a security action comprises: preventing user systems from downloading the content. | WARP has nothing to do with digital signatures or events based on signatures failing of being verified. Hence this does not apply. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 18. A computer-readable medium having stored thereon instructions which, when executed by a processor, causes the processor to perform the operations of: sending a request for content to a content aggregator site; and receiving from the content aggregator site a digitally signed ticket file including a first cryptographic hash of at least a portion of content. | WARP does not access content. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 19. The computer-readable medium of claim 18, further comprising: downloading the content to a user system over a network, where the content is downloaded separately from the ticket file; and verifying the digital signature of the ticket file. | WARP does not access content. WARP does not download or deal with ticket files. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 20. The computer-readable medium of claim 18, where verifying the digital signature comprises: creating a second cryptographic hash of the downloaded content; comparing the second cryptographic hash with the first cryptographic hash; and if the hashes do not match, initiating a security action. | WARP does not do any cryptographic checks. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 21. The computer-readable medium of claim 20, where initiating a security action comprises: deleting the content from the user system. | WARP does not do any cryptographic checks. WARP does not do deletion of people's content. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 22. The computer-readable medium of claim 20, where initiating a security action comprises: notifying the content aggregator site of a failed verification if the hashes do not match; and receiving a command for revoking the digital signature of the ticket file. | WARP does not do any cryptographic checks. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 23. The computer-readable medium of claim 20, where initiating a security action comprises: scanning the user system for instances of revoked content. | WARP does not do any cryptographic checks. WARP does not do deletion of people's content. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 24. The computer-readable medium of claim 18, further comprising: creating a security log on the user system that includes a history of content installation. | WARP does not write log files about their computer's content. WARP does not generate security logs. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 25. A method of installing content, comprising: receiving content from a content distributor, the content including a first cryptographic hash of the content; creating a second cryptographic hash of the content; comparing the second cryptographic hash with the first cryptographic hash; and if the hashes do not match, initiating a security action. | WARP does not do this as it does not do any cryptographic checks. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
f5bf300e_ess_Request_Policy__PAG_Report__Application_and_WARP_Features_against_the_WARP_Specification | 26. The method of claim 25, further comprising: comparing the content to one or more lists of content to determine if the content can be safely installed. | WARP does not do this. it has nothing to do with content installation. | [] | WARP: Widgets Access Request Policy: PAG Report | Evaluation against the WARP Specification | http://www.w3.org/2009/11/widgets-pag/pagreport.html | 6/1438042988860.4_20150728002308-00046-ip-10-236-191-2_819374747_0.json |
c24713f4_abulary___ODRL_Community_Group___function__of_the_entity_Role_Comment | [Identifier] assigner [Semantics] The Party is the issuer of the policy statement [Comment] | Must be supported. | [] | ODRL Version 2.1 Common Vocabulary | ODRL Community Group | Comment | https://www.w3.org/community/odrl/vocab/2.1/?rev=339 | 6/1438042987135.9_20150728002307-00036-ip-10-236-191-2_932861800_7.json |
c24713f4_abulary___ODRL_Community_Group___function__of_the_entity_Role_Comment | [Identifier] assignee [Semantics] The Party is the recipient of the policy statement [Comment] | Must be supported. | [] | ODRL Version 2.1 Common Vocabulary | ODRL Community Group | Comment | https://www.w3.org/community/odrl/vocab/2.1/?rev=339 | 6/1438042987135.9_20150728002307-00036-ip-10-236-191-2_932861800_7.json |
c24713f4_abulary___ODRL_Community_Group___function__of_the_entity_Role_Comment | [Identifier] attributedParty [Semantics] The Party to be attributed [Comment] | May be specified as part of the attribute action. | [] | ODRL Version 2.1 Common Vocabulary | ODRL Community Group | Comment | https://www.w3.org/community/odrl/vocab/2.1/?rev=339 | 6/1438042987135.9_20150728002307-00036-ip-10-236-191-2_932861800_7.json |
c24713f4_abulary___ODRL_Community_Group___function__of_the_entity_Role_Comment | [Identifier] consentingParty [Semantics] The Party to obtain consent from [Comment] | May be specified as part of the obtainConsent action. | [] | ODRL Version 2.1 Common Vocabulary | ODRL Community Group | Comment | https://www.w3.org/community/odrl/vocab/2.1/?rev=339 | 6/1438042987135.9_20150728002307-00036-ip-10-236-191-2_932861800_7.json |
c24713f4_abulary___ODRL_Community_Group___function__of_the_entity_Role_Comment | [Identifier] informedParty [Semantics] The Party to be informed of all uses [Comment] | May be specified as part of the inform action. | [] | ODRL Version 2.1 Common Vocabulary | ODRL Community Group | Comment | https://www.w3.org/community/odrl/vocab/2.1/?rev=339 | 6/1438042987135.9_20150728002307-00036-ip-10-236-191-2_932861800_7.json |
c24713f4_abulary___ODRL_Community_Group___function__of_the_entity_Role_Comment | [Identifier] compensatedParty [Semantics] The Party is the recipient of the compensation [Comment] | May be specified as part of the compensate duty action. | [] | ODRL Version 2.1 Common Vocabulary | ODRL Community Group | Comment | https://www.w3.org/community/odrl/vocab/2.1/?rev=339 | 6/1438042987135.9_20150728002307-00036-ip-10-236-191-2_932861800_7.json |
c24713f4_abulary___ODRL_Community_Group___function__of_the_entity_Role_Comment | [Identifier] trackingParty [Semantics] The Party is the usage tracker [Comment] | May be specified as part of the acceptTracking action. | [] | ODRL Version 2.1 Common Vocabulary | ODRL Community Group | Comment | https://www.w3.org/community/odrl/vocab/2.1/?rev=339 | 6/1438042987135.9_20150728002307-00036-ip-10-236-191-2_932861800_7.json |
3faa42c5___GSP_____Linked_Data_Platform__LDP_Collection___GSP_graph | [0] GET [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict, GSP returns undefined [LDP Collection = GSP endpoint] No conflict, GSP returns undefined [LDP Collection = GSP graph] | No conflict | [] | Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform | LDP Collection = GSP graph | http://www.w3.org/2012/ldp/wiki/index.php?title=Linked_Data_Platform_(LDP)_vs_SPARQL_Graph_Store_HTTP_Protocol_(GSP)&curid=163&diff=2867&oldid=2866 | 6/1438042988860.4_20150728002308-00100-ip-10-236-191-2_836421201_28.json |
3faa42c5___GSP_____Linked_Data_Platform__LDP_Collection___GSP_graph | [0] HEAD [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict; added LDP headers [LDP Collection = GSP endpoint] No conflict; added LDP headers [LDP Collection = GSP graph] | No conflict; added LDP headers | [] | Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform | LDP Collection = GSP graph | http://www.w3.org/2012/ldp/wiki/index.php?title=Linked_Data_Platform_(LDP)_vs_SPARQL_Graph_Store_HTTP_Protocol_(GSP)&curid=163&diff=2867&oldid=2866 | 6/1438042988860.4_20150728002308-00100-ip-10-236-191-2_836421201_28.json |
3faa42c5___GSP_____Linked_Data_Platform__LDP_Collection___GSP_graph | [0] OPTIONS [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict; added LDP headers [LDP Collection = GSP endpoint] No conflict; added LDP headers [LDP Collection = GSP graph] | No conflict; added LDP headers | [] | Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform | LDP Collection = GSP graph | http://www.w3.org/2012/ldp/wiki/index.php?title=Linked_Data_Platform_(LDP)_vs_SPARQL_Graph_Store_HTTP_Protocol_(GSP)&curid=163&diff=2867&oldid=2866 | 6/1438042988860.4_20150728002308-00100-ip-10-236-191-2_836421201_28.json |
3faa42c5___GSP_____Linked_Data_Platform__LDP_Collection___GSP_graph | [0] PUT [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] Conflict [LDP Collection = GSP endpoint] Conflict [LDP Collection = GSP graph] | No conflict | [] | Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform | LDP Collection = GSP graph | http://www.w3.org/2012/ldp/wiki/index.php?title=Linked_Data_Platform_(LDP)_vs_SPARQL_Graph_Store_HTTP_Protocol_(GSP)&curid=163&diff=2867&oldid=2866 | 6/1438042988860.4_20150728002308-00100-ip-10-236-191-2_836421201_28.json |
3faa42c5___GSP_____Linked_Data_Platform__LDP_Collection___GSP_graph | [0] POST [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] Conflict [LDP Collection = GSP endpoint] Conflict [LDP Collection = GSP graph] | No conflict? Different functionality is to be expected, but do not influence each other | [] | Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform | LDP Collection = GSP graph | http://www.w3.org/2012/ldp/wiki/index.php?title=Linked_Data_Platform_(LDP)_vs_SPARQL_Graph_Store_HTTP_Protocol_(GSP)&curid=163&diff=2867&oldid=2866 | 6/1438042988860.4_20150728002308-00100-ip-10-236-191-2_836421201_28.json |
3faa42c5___GSP_____Linked_Data_Platform__LDP_Collection___GSP_graph | [0] DELETE [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict [LDP Collection = GSP endpoint] No conflict [LDP Collection = GSP graph] | No conflict | [] | Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform | LDP Collection = GSP graph | http://www.w3.org/2012/ldp/wiki/index.php?title=Linked_Data_Platform_(LDP)_vs_SPARQL_Graph_Store_HTTP_Protocol_(GSP)&curid=163&diff=2867&oldid=2866 | 6/1438042988860.4_20150728002308-00100-ip-10-236-191-2_836421201_28.json |
3faa42c5___GSP_____Linked_Data_Platform__LDP_Collection___GSP_graph | [0] PATCH [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict [LDP Collection = GSP endpoint] No conflict [LDP Collection = GSP graph] | Conflict; changes through GSP can break consistency in LDPC | [] | Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform | LDP Collection = GSP graph | http://www.w3.org/2012/ldp/wiki/index.php?title=Linked_Data_Platform_(LDP)_vs_SPARQL_Graph_Store_HTTP_Protocol_(GSP)&curid=163&diff=2867&oldid=2866 | 6/1438042988860.4_20150728002308-00100-ip-10-236-191-2_836421201_28.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i1 : How to create an XHTML document? [Concerning] XHTML [State] | resolved | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i2 : lack a method to easily access the HEAD element [Concerning] improvement [State] | rejected | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i3 : Convenient methods to create elements [Concerning] improvement [State] | rejected | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i4 : methods that return instances of specific elements should have a specific return type [Concerning] improvement [State] | rejected | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i5 : HTMLFrameElement::src should dynamically update [Concerning] improvement [State] | rejected | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i6 : HTMLFormElement::submit [Concerning] clarification [State] | active | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i7 : HTMLInputElement::size [Concerning] type error [State] | resolved | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i8 : HTMLTableElement: there are tFoot, tHead and caption should be readonly. [Concerning] readwrite/readonly? [State] | rejected | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i9 : select.options.length should be read/write [Concerning] readwrite/readonly? [State] | resolved | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i9b : select.options array [Concerning] array manipulation [State] | rejected | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i10 : HTMLInputElement.indeterminate [Concerning] new property [State] | Subsumed by issue i24 | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i11 : XHTML 1.0 [Concerning] General [State] | resolved | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i12 : HTML DOM and DTDs [Concerning] clarifications [State] | resolved | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i13 : XHTML 1.0 DTDs [Concerning] clarification [State] | resolved | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i14 : HTML 4, 4.0, and 4.01 [Concerning] clarification [State] | resolved | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i15 : name or id [Concerning] clarification [State] | resolved | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i16 : HTMLDocument.anchors [Concerning] convenience [State] | resolved | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i17 : HTMLDocument.images [Concerning] convenience [State] | resolved | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i18 : Element.className [Concerning] textual issue [State] | resolved | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
29039c6b_DOM_Level_2_HTML_Issues_List__State | [Id: Title] i20 : HTMLInputElement.indeterminate, checked and the form itself [Concerning] incompatibility [State] | rejected | [
[
"r",
"e",
"s",
"o",
"l",
"v",
"e",
"d"
],
[
"r",
"e",
"j",
"e",
"c",
"t",
"e",
"d"
],
[
"a",
"c",
"t",
"i",
"v",
"e"
],
[
"S",
"u",
"b",
"s",
"u",
"m",
"e",
"d",
" ",
"b",
"y",
" ",
"i",
"s",
"s",
"u",
"e",
" ",
"i",
"2",
"4"
]
] | DOM Level 2 HTML Issues List | State | http://www.w3.org/2001/12/DOM-Level-2-issues | 6/1438042981576.7_20150728002301-00293-ip-10-236-191-2_806876641_0.json |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.