- From: Futomi Hatano <futomi.hatano@newphoria.co.jp>
- Date: Tue, 27 Nov 2012 18:43:59 +0900
- To: public-websignage@w3.org
Hi all, We reviewed "Web-based Signage Use cases and Requirements" at TPAC. Thanks for your hard work at TPAC, all of attendees. We decided to tweak the doc as described in the summary of f2f meeting. http://www.w3.org/community/websignage/wiki/Group_meeting_at_TPAC_2012#Reviewing_.22Web-based_Signage_Use_cases_and_Requirements.22 I updated the doc based on our conclusion as blow: * combined R3 and R4. Now the new combined requirement is R3. http://www.w3.org/community/websignage/wiki/Web-based_Signage_Use_cases_and_Requirements#R3._Communication_with_a_personal_device_within_proximity I renumbered the remaining requirements along with this update * Fixed XHR references. Now, "XMLHttpRequest Level 2" has been renamed "XMLHttpRequest". * Added a new requirement proposed by KAIST as R9 : "Prevent displaying time conflicts between scheduled contents and even-driven contents" http://www.w3.org/community/websignage/wiki/Web-based_Signage_Use_cases_and_Requirements#R19._Prevent_displaying_time_conflicts_between_scheduled_contents_and_even-driven_contents Best regards, Futomi -- Newphoria Corporation Chief Technology Officer Futomi Hatano -- futomi.hatano@newphoria.co.jp http://www.newphoria.co.jp/
Received on Tuesday, 27 November 2012 09:43:48 UTC