- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Wed, 03 May 2006 08:41:45 +0200
- To: Jim Ley <jim@jibbering.com>
- Cc: Johannes Koch <johannes.koch@fit.fraunhofer.de>, public-wai-ert@w3.org
It seems there may be two approaches to record such snippets: 1. define a single earl:content and use a property (eg earl:contentType) to record the encoding 2. define individual property for each content type (eg earl:textContent and earl:base64Content) While the first approach seems to be very flexible, the second one seems less complex yet adequate. We can also have a compromise solution of using the first approach, but defining "text" and "base64" as the *default* values for EARL 1.0 (to mean that if tools output such snippets, they must use at least one of these two values in addition to any other values they may provide). Thoughts? Regards, Shadi Jim Ley wrote: > > "Johannes Koch" <johannes.koch@fit.fraunhofer.de> >>> <earl:snippet> >>> <earl:Snippet> >>> >>> <earl:byteContent>214328764328764387ae343eeee7e7ee</earl:byteContent> >>> <earl:byteOffset>15</earl:byteOffset> >>> </earl:Snippet> >>> </earl:snippet> >>> >>> Is that ok JK? >> >> You need to record the byte->character encoding scheme (e.g. Base64) >> somewhere. > > I was thinking of defining byteContent to be base64 encoded, do you > think that would not be a good idea? > > Jim. > > -- Shadi Abou-Zahra Web Accessibility Specialist for Europe | Chair & Staff Contact for the Evaluation and Repair Tools WG | World Wide Web Consortium (W3C) http://www.w3.org/ | Web Accessibility Initiative (WAI), http://www.w3.org/WAI/ | WAI-TIES Project, http://www.w3.org/WAI/TIES/ | Evaluation and Repair Tools WG, http://www.w3.org/WAI/ER/ | 2004, Route des Lucioles - 06560, Sophia-Antipolis - France | Voice: +33(0)4 92 38 50 64 Fax: +33(0)4 92 38 78 22 |
Received on Wednesday, 3 May 2006 06:41:53 UTC