W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 1998

RE: <smil> SAMI Closed Captions are now available for your revi ew (fwd)

From: Charles (Chuck) Oppermann <chuckop@MICROSOFT.com>
Date: Mon, 24 Aug 1998 18:12:53 -0700
Message-ID: <D70342829C12D2119D0700805FBECA2F75F397@RED-MSG-55>
To: "'Jon Gunderson'" <jongund@staff.uiuc.edu>, David Poehlman <poehlman@clark.net>, w3c-wai-ua@w3.org
So is the question "Should SAMI be included in the guidelines similar to
MSAA and JAP?"  or is the question "Let's review SAMI as part of the UA
guidelines?"

Of course, I'm just talking about the first question.

-----Original Message-----
From: Jon Gunderson [mailto:jongund@staff.uiuc.edu]
Sent: Monday, August 24, 1998 2:39 PM
To: Charles (Chuck) Oppermann; David Poehlman; w3c-wai-ua@w3.org
Subject: RE: <smil> SAMI Closed Captions are now available for your revi
ew (fwd)


We recommend the use of accessibility APIs, and have a reference to known
accessibility APIs including Active Accessibility.  But we don't try to set
or discuss specifications for those accessibility API standards.  We can
have input into W3C recommendations.  

Is SAMI part of any W3C recommendation processes?
Jon

  

At 11:51 AM 8/24/98 -0700, Charles (Chuck) Oppermann wrote:
>A couple of points - the W3C does not create standards, they create
>recommendations.  The guidelines reference Java Accessibility API which is
>considered fairly proprietary.  If the guidelines recommend those, why
>should they not recommend SAMI?
>
>-----Original Message-----
>From: Jon Gunderson [mailto:jongund@staff.uiuc.edu]
>Sent: Monday, August 24, 1998 7:59 AM
>To: David Poehlman; w3c-wai-ua@w3.org
>Subject: Re: <smil> SAMI Closed Captions are now available for your
>review (fwd)
>
>
>I don't believe SAMI is a W3C standard.  SAMI I belive is a proprietary
>standard of Microsoft and the W3C from my understanding does not comment on
>proprietary standards.  If some one from Microsoft or anywhere else has any
>other information, please post to the list.  This same issue came up with
>accessibility APIs.  
>Jon
>
>
>At 07:19 AM 8/21/98 -0400, David Poehlman wrote:
>>should we include this?
>>I think this is what was promised.
>>
>>
>>-- 
>>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
>>
>>
>>---------- Forwarded message ----------
>>Date: Fri, 21 Aug 1998 04:10:28 -0500
>>From: David Bolnick <davebo@MICROSOFT.com>
>>Reply-To: uaccess-l@trace.wisc.edu
>>To: Multiple recipients of list <uaccess-l@trace.wisc.edu>
>>Subject: SAMI Closed Captions are now available for your review
>>
>>SAMI Article #1:
>>
>>With the recent release of Windows Media Player came SAMI captions. SAMI,
>>Synchronized Accessible Media Interchange, is a single authoring format
for
>>captions and audio descriptions.  This article and set of demos focus on
>>captioning. There will be subsequent articles on audio description (see
>list
>>below).
>>
>>SAMI Overview article: http://microsoft.com/enable/products/multimedia.htm
>><http://microsoft.com/enable/products/multimedia.htm> 
>>
>>******* Please review the following before you download any SAMI
>>demos********
>>
>>SAMI Format article: http://microsoft.com/enable/products/sami.htm
>><http://microsoft.com/enable/products/sami.htm> 
>>
>>There has been much confusion about the role of SAMI vs. the role of SMIL.
>>The two are quite different though they use similar techniques to
>accomplish
>>their goals. SMIL is a set of XML based elements used for presenting and
>>positioning synchronized components of a multimedia presentation. On the
>>other hand, SAMI is an authoring format solely designed to deliver
>>synchronized captions and audio description. SAMI has been designed to
>>provide multiple language and style support. The latter is critical for
>>accessibility. That is, if the user is unable to read the captions due to
a
>>visual impairment then we can question whether we have provided captions
to
>>that user. Thus, SAMI supports multiple styles so the caption author can
>>provide, in addition to a standard font, several varieties of large print
>or
>>color combinations for the user to select from. Furthermore, SAMI
>introduces
>>an optional Source ID line that continuously displays the source of the
>>sound. This is valuable for many dyslexics and people with short-term
>memory
>>loss (those, like myself, over 40). 
>>
>>Future articles:
>>* Using SAMI for Closed Captions on the Web (mid September)
>>* SAMI Support of Audio Description (mid October)
>>* SAMI as an authoring format for EIA608, EIA708, DVD, and Web encoding -
>>full SAMI spec (mid November)
>>* SAMI Caption Authoring Tool (mid December)
>>
>>Note:
>>We are currently working on version 2 of Windows Media Player's SAMI
>>support. Please send your suggestions directly to me. 
>>
>>David.
>>
>>David A. Bolnick
>>Accessibility Program Manager: Multimedia, Telecommunications
>>Microsoft Corporation, One Microsoft Way, Redmond, WA  98052
>>E-mail:  <mailto:davebo@microsoft.com> davebo@microsoft.com     Web:
>><http://microsoft.com/enable> http://microsoft.com/enable
>> 
>Jon Gunderson, Ph.D., ATP
>Coordinator of Assistive Communication and Information Technology
>Division of Rehabilitation - Education Services
>University of Illinois at Urbana/Champaign
>1207 S. Oak Street
>Champaign, IL 61820
>
>Voice: 217-244-5870
>Fax: 217-333-0248
>E-mail: jongund@uiuc.edu
>WWW:	http://www.staff.uiuc.edu/~jongund
>	http://www.als.uiuc.edu/InfoTechAccess
> 
Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
University of Illinois at Urbana/Champaign
1207 S. Oak Street
Champaign, IL 61820

Voice: 217-244-5870
Fax: 217-333-0248
E-mail: jongund@uiuc.edu
WWW:	http://www.staff.uiuc.edu/~jongund
	http://www.als.uiuc.edu/InfoTechAccess
Received on Monday, 24 August 1998 21:12:33 UTC

This archive was generated by hypermail 2.3.1 : Friday, 13 July 2018 11:53:07 UTC