On 2012-08-28 18:11, Matthew Miller wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think either of these is ok. I'd still like at least some reference to how
the technology works, since you are using this as a reference of prior art. If
you can't include a reference, then an internet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think either of these is ok. I'd still like at least some reference to how
the technology works, since you are using this as a reference of prior art. If
you can't include a reference, then an internet search of the term needs to
lead very quick
I like choice 1
Gregg
Gregg Vanderheiden Ph.D.
Director Trace R&D Center
Professor Industrial & Systems Engineering
and Biomedical Engineering
University of Wisconsin-Madison
Technical Director - Cloud4all Project - http://Cloud4all.info
Co
Since the spec targets all audiences,
I may have to remove the "TTY" from the introduction, and simply say:
CHOICE #1 (preferred, to avoid expanding "TTY")
-
* Various text telephone technologies (e.g. TTY), used by the deaf and
hard of hearing.
6.6.1 c/"TTY
On 2012-08-23 18:31, Peter Saint-Andre wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/23/12 10:22 AM, Matthew Miller wrote:
I do realize this might seem pointless to some, but I really do
want to understand where this technology is coming from.
Matt, it's basically a matter of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/23/12 10:22 AM, Matthew Miller wrote:
> I do realize this might seem pointless to some, but I really do
> want to understand where this technology is coming from.
Matt, it's basically a matter of the history of computing at this
point. Unfortuna
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 23, 2012, at 00:51, Gunnar Hellström wrote:
> On 2012-08-23 00:34, Matthew Miller wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>> On Aug 22, 2012, at 16:32, Gunnar Hellström wrote:
>>
>>
>>> /The US Access Board has the
Op 23/08/2012 08:51, Gunnar Hellström schreef:
On 2012-08-23 00:34, Matthew Miller wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 22, 2012, at 16:32, Gunnar Hellström wrote:
/The US Access Board has the following definition in its latest proposal for
Accessible procurement, Se
On 2012-08-23 00:34, Matthew Miller wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 22, 2012, at 16:32, Gunnar Hellström wrote:
/The US Access Board has the following definition in its latest proposal for
Accessible procurement, Section 508. E.103.4
/http://www.access-board.gov/
On 2012-08-23 03:27, Peter Saint-Andre wrote:
On 8/22/12 12:30 PM, Matthew Miller wrote:
First, this section is written more as a marketing pitch and less
as a technical description. This bothers me enough that I strongly
urge it be changed.
Strangely, this section didn't bother me much. I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/22/12 12:30 PM, Matthew Miller wrote:
> First, this section is written more as a marketing pitch and less
> as a technical description. This bothers me enough that I strongly
> urge it be changed.
Strangely, this section didn't bother me much.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 22, 2012, at 16:33, Gregg Vanderheiden wrote:
> On Aug 22, 2012, at 5:05 PM, Matthew Miller
> wrote:
>
>> What would help most to alleviate this discussion further is to include an
>> authoritative citation.
>
>
> here is one. TTY takes
Op 23/08/2012 00:32, Gunnar Hellström schreef:
On 2012-08-23 00:05, Matthew Miller wrote:
I do not see TTY as an acronym anymore.
It is like BT that was read out British Telecom before, but is now just BT.
Or AT&T was read out American Telephone and Telegraph, but is now just AT&T
Wiktionary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 22, 2012, at 16:32, Gunnar Hellström wrote:
> /The US Access Board has the following definition in its latest proposal for
> Accessible procurement, Section 508. E.103.4
> /http://www.access-board.gov/sec508/refresh/draft-rule.htm
> /
> TTY.
On Aug 22, 2012, at 5:05 PM, Matthew Miller wrote:
> What would help most to alleviate this discussion further is to include an
> authoritative citation.
here is one. TTY takes you here - and it is all discussed.
http://en.wikipedia.org/wiki/Telecommunications_device_for_the_deaf
Gregg
--
On 2012-08-23 00:05, Matthew Miller wrote:
I do not see TTY as an acronym anymore.
It is like BT that was read out British Telecom before, but is now just BT.
Or AT&T was read out American Telephone and Telegraph, but is now just AT&T
Wiktionary has solved it by putting (originally) after Tele
Op 22/08/2012 23:42, Mark Rejhon schreef:
Is this politics-proof:
"TTY (derived from teletypewriter) and text telephones"
I don't like it, but I am going to leave it unmodified (against M&M
wishes) unless there's a consensus.
I agree with gregg. it's history. At this time many deaf poeple haven
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 22, 2012, at 15:51, Gunnar Hellström wrote:
>
> On 2012-08-22 23:35, Gregg Vanderheiden wrote:
>> agree
>>
>> You can say
>>
>> TTY was derived from Teletypewriter - a device originally used by people who
>> are deaf to communicate. But t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 22, 2012, at 15:42, Mark Rejhon wrote:
> Is this politics-proof:
>
> "TTY (derived from teletypewriter) and text telephones"
>
> I don't like it, but I am going to leave it unmodified (against M&M
> wishes) unless there's a consensus.
>
Si
On 2012-08-22 23:35, Gregg Vanderheiden wrote:
agree
You can say
TTY was derived from Teletypewriter - a device originally used by
people who are deaf to communicate. But today Teletypewriters no
longer exist and TTY is used to refer to a type of telecommunications
device used by people wh
On Aug 22, 2012, at 4:33 PM, Matthew Miller wrote:
> If you use an acronym, you MUST expand it. If Teletypewriter is not the
> correct expansion for TTY, then provide the correct one and include an
> authoritative citation.
Hm. TTY isn't an acronym anymore. It was at one time --
Is this politics-proof:
"TTY (derived from teletypewriter) and text telephones"
I don't like it, but I am going to leave it unmodified (against M&M
wishes) unless there's a consensus.
On Wed, Aug 22, 2012 at 5:35 PM, Gregg Vanderheiden wrote:
> agree
>
> You can say
>
> TTY was derived from Te
agree
You can say
TTY was derived from Teletypewriter - a device originally used by people who
are deaf to communicate. But today Teletypewriters no longer exist and TTY is
used to refer to a type of telecommunications device used by people who are
deaf that supports Baudot (and sometimes ot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 22, 2012, at 15:28, Gunnar Hellström wrote:
> I do not think expansion of TTY to Teletypewriter is a good idea. That tends
> to mean the other use of the term TTY, the device that was often used as a
> computer operator console terminal a l
On 2012-08-22 22:58, Mark Rejhon wrote:
On Wed, Aug 22, 2012 at 4:46 PM, Matthew Miller
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 22, 2012, at 14:42, Mark Rejhon wrote:
On Wed, Aug 22, 2012 at 2:30 PM, Matthew Miller
wrote:
* Teletypewriter (TTY) and Text Device for the
On Wed, Aug 22, 2012 at 4:46 PM, Matthew Miller
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> On Aug 22, 2012, at 14:42, Mark Rejhon wrote:
>
>> On Wed, Aug 22, 2012 at 2:30 PM, Matthew Miller
>> wrote:
>>> * Teletypewriter (TTY) and Text Device for the Deaf (TDD) telephones
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 22, 2012, at 14:42, Mark Rejhon wrote:
> On Wed, Aug 22, 2012 at 2:30 PM, Matthew Miller
> wrote:
>> * Teletypewriter (TTY) and Text Device for the Deaf (TDD) telephones
>> [citations recommended]
>
> Consulted with some peers.
>
> TTY exp
On Wed, Aug 22, 2012 at 2:30 PM, Matthew Miller
wrote:
> * Teletypewriter (TTY) and Text Device for the Deaf (TDD) telephones
> [citations recommended]
Consulted with some peers.
TTY expansion to Teletypewriter -- OK, good idea.
TDD is actually correctly "Telecommunications Device for the Deaf"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 22, 2012, at 13:35, Mark Rejhon wrote:
> Hello Matthew,
>
> Thanks for your comments!
> I eager await your ongoing comments. Just some brief reply:
>
>
> On Wed, Aug 22, 2012 at 2:30 PM, Matthew Miller
> wrote:
>> * Reword the paragraph 3
On Wed, Aug 22, 2012 at 8:35 PM, Mark Rejhon wrote:
> So, the challenge is, the paragraph needs to be written both
> geek-friendly (people like you and me) and deaf-friendly (one part of
> the audience).
It's worth noting that XEPs are necessarily written for the target
audience of implementers,
Hello Matthew,
Thanks for your comments!
I eager await your ongoing comments. Just some brief reply:
On Wed, Aug 22, 2012 at 2:30 PM, Matthew Miller
wrote:
> * Reword the paragraph 3 in terms of the problems it is solving. One possible
> suggestion:
I like the inclusion of the following: It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'll slowly be commenting mostly on a section-by-section basis.
These are my comments regarding section 1 of XEP-0301: Real-Time Text. There
might be some mention of these earlier, but I've lost track. If already
addressed previously, then please
32 matches
Mail list logo
