- From: David Poehlman <poehlman@clark.net>
- Date: Tue, 25 Aug 1998 08:02:07 -0400 (EDT)
- To: "Charles (Chuck) Oppermann" <chuckop@MICROSOFT.com>
- cc: "'Jon Gunderson'" <jongund@staff.uiuc.edu>, w3c-wai-ua@w3.org
I originally posted this as part of the smil track because those of us in that subgroup are looking at all of these types of pluggins and operables if you will just like we all look at the different browsers. My reason then was to provide something besides g2 and the wgbh smil examples for us to look at for issue comparison. I think unless jim allan and the rest of the ggroup are ready to do so that I'm not aware of, we don't have a guideline or an issue track as yet unless you look at the current work. Also chuck, I'm quite interested in the audio description component soon to be added. and I've a question. is there going to be a player independant util for this. for one reason or annother some of us will not or cannot use the ms media player. I am not one of them but there are issues even if rhumoured you know. Thanks! On Mon, 24 Aug 1998, Charles (Chuck) Oppermann wrote: CCOSo is the question "Should SAMI be included in the guidelines similar to CCOMSAA and JAP?" or is the question "Let's review SAMI as part of the UA CCOguidelines?" CCO CCOOf course, I'm just talking about the first question. CCO CCO-----Original Message----- CCOFrom: Jon Gunderson [mailto:jongund@staff.uiuc.edu] CCOSent: Monday, August 24, 1998 2:39 PM CCOTo: Charles (Chuck) Oppermann; David Poehlman; w3c-wai-ua@w3.org CCOSubject: RE: <smil> SAMI Closed Captions are now available for your revi CCOew (fwd) CCO CCO CCOWe recommend the use of accessibility APIs, and have a reference to known CCOaccessibility APIs including Active Accessibility. But we don't try to set CCOor discuss specifications for those accessibility API standards. We can CCOhave input into W3C recommendations. CCO CCOIs SAMI part of any W3C recommendation processes? CCOJon CCO CCO CCO CCOAt 11:51 AM 8/24/98 -0700, Charles (Chuck) Oppermann wrote: CCO>A couple of points - the W3C does not create standards, they create CCO>recommendations. The guidelines reference Java Accessibility API which is CCO>considered fairly proprietary. If the guidelines recommend those, why CCO>should they not recommend SAMI? CCO> CCO>-----Original Message----- CCO>From: Jon Gunderson [mailto:jongund@staff.uiuc.edu] CCO>Sent: Monday, August 24, 1998 7:59 AM CCO>To: David Poehlman; w3c-wai-ua@w3.org CCO>Subject: Re: <smil> SAMI Closed Captions are now available for your CCO>review (fwd) CCO> CCO> CCO>I don't believe SAMI is a W3C standard. SAMI I belive is a proprietary CCO>standard of Microsoft and the W3C from my understanding does not comment on CCO>proprietary standards. If some one from Microsoft or anywhere else has any CCO>other information, please post to the list. This same issue came up with CCO>accessibility APIs. CCO>Jon CCO> CCO> CCO>At 07:19 AM 8/21/98 -0400, David Poehlman wrote: CCO>>should we include this? CCO>>I think this is what was promised. CCO>> CCO>> CCO>>-- CCO>>Hands-On-Technolog(eye)s CCO>>touching the internet CCO>>voice: 1-(301) 949-7599 CCO>>poehlman@clark.net CCO>>ftp://ftp.clark.net/pub/poehlman CCO>>http://www.clark.net/pub/poehlman CCO>>Dynamic solutions Inc. CCO>>Best of service for your Small Business network Needs CCO>>Http://www.dnsolutions.com CCO>> CCO>> CCO>>---------- Forwarded message ---------- CCO>>Date: Fri, 21 Aug 1998 04:10:28 -0500 CCO>>From: David Bolnick <davebo@MICROSOFT.com> CCO>>Reply-To: uaccess-l@trace.wisc.edu CCO>>To: Multiple recipients of list <uaccess-l@trace.wisc.edu> CCO>>Subject: SAMI Closed Captions are now available for your review CCO>> CCO>>SAMI Article #1: CCO>> CCO>>With the recent release of Windows Media Player came SAMI captions. SAMI, CCO>>Synchronized Accessible Media Interchange, is a single authoring format CCOfor CCO>>captions and audio descriptions. This article and set of demos focus on CCO>>captioning. There will be subsequent articles on audio description (see CCO>list CCO>>below). CCO>> CCO>>SAMI Overview article: http://microsoft.com/enable/products/multimedia.htm CCO>><http://microsoft.com/enable/products/multimedia.htm> CCO>> CCO>>******* Please review the following before you download any SAMI CCO>>demos******** CCO>> CCO>>SAMI Format article: http://microsoft.com/enable/products/sami.htm CCO>><http://microsoft.com/enable/products/sami.htm> CCO>> CCO>>There has been much confusion about the role of SAMI vs. the role of SMIL. CCO>>The two are quite different though they use similar techniques to CCO>accomplish CCO>>their goals. SMIL is a set of XML based elements used for presenting and CCO>>positioning synchronized components of a multimedia presentation. On the CCO>>other hand, SAMI is an authoring format solely designed to deliver CCO>>synchronized captions and audio description. SAMI has been designed to CCO>>provide multiple language and style support. The latter is critical for CCO>>accessibility. That is, if the user is unable to read the captions due to CCOa CCO>>visual impairment then we can question whether we have provided captions CCOto CCO>>that user. Thus, SAMI supports multiple styles so the caption author can CCO>>provide, in addition to a standard font, several varieties of large print CCO>or CCO>>color combinations for the user to select from. Furthermore, SAMI CCO>introduces CCO>>an optional Source ID line that continuously displays the source of the CCO>>sound. This is valuable for many dyslexics and people with short-term CCO>memory CCO>>loss (those, like myself, over 40). CCO>> CCO>>Future articles: CCO>>* Using SAMI for Closed Captions on the Web (mid September) CCO>>* SAMI Support of Audio Description (mid October) CCO>>* SAMI as an authoring format for EIA608, EIA708, DVD, and Web encoding - CCO>>full SAMI spec (mid November) CCO>>* SAMI Caption Authoring Tool (mid December) CCO>> CCO>>Note: CCO>>We are currently working on version 2 of Windows Media Player's SAMI CCO>>support. Please send your suggestions directly to me. CCO>> CCO>>David. CCO>> CCO>>David A. Bolnick CCO>>Accessibility Program Manager: Multimedia, Telecommunications CCO>>Microsoft Corporation, One Microsoft Way, Redmond, WA 98052 CCO>>E-mail: <mailto:davebo@microsoft.com> davebo@microsoft.com Web: CCO>><http://microsoft.com/enable> http://microsoft.com/enable CCO>> CCO>Jon Gunderson, Ph.D., ATP CCO>Coordinator of Assistive Communication and Information Technology CCO>Division of Rehabilitation - Education Services CCO>University of Illinois at Urbana/Champaign CCO>1207 S. Oak Street CCO>Champaign, IL 61820 CCO> CCO>Voice: 217-244-5870 CCO>Fax: 217-333-0248 CCO>E-mail: jongund@uiuc.edu CCO>WWW: http://www.staff.uiuc.edu/~jongund CCO> http://www.als.uiuc.edu/InfoTechAccess CCO> CCOJon Gunderson, Ph.D., ATP CCOCoordinator of Assistive Communication and Information Technology CCODivision of Rehabilitation - Education Services CCOUniversity of Illinois at Urbana/Champaign CCO1207 S. Oak Street CCOChampaign, IL 61820 CCO CCOVoice: 217-244-5870 CCOFax: 217-333-0248 CCOE-mail: jongund@uiuc.edu CCOWWW: http://www.staff.uiuc.edu/~jongund CCO http://www.als.uiuc.edu/InfoTechAccess CCO -- Hands-On-Technolog(eye)s touching the internet voice: 1-(301) 949-7599 poehlman@clark.net ftp://ftp.clark.net/pub/poehlman http://www.clark.net/pub/poehlman Dynamic solutions Inc. Best of service for your Small Business network Needs Http://www.dnsolutions.com
Received on Tuesday, 25 August 1998 08:01:45 UTC