W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2010

RE: changes to sysinfo (was Fwd: Agenda - Distributed Meeting 2010-06-23)

From: SULLIVAN, BRYAN L (ATTCINW) <BS3131@att.com>
Date: Mon, 28 Jun 2010 22:27:00 -0700
Message-ID: <8080D5B5C113E940BA8A461A91BFFFCD12A9E56B@BD01MSXMB015.US.Cingular.Net>
To: <jsalsman@gmail.com>, "James Salsman" <jsalsman@talknicer.com>
Cc: <public-device-apis@w3.org>, "Tran, Dzung D" <dzung.d.tran@intel.com>
James,
Making the changes now. I will upload it tomorrow. Had to find and learn an SVG editor tool (Inkscape).

Re "An active network connection is connected. Data sent over an active network connection is expected to be delivered in accordance with carrier-independent, end-to-end principles of internet datagram delivery. Connections which do not conform to carrier-independent, end-to-end principles with reasonable round trip times should not be considered active when other connections are available.  Disconnected and otherwise unavailable connections must not be considered active." : 

The statement "Connections which do not conform to carrier-independent, end-to-end principles with reasonable round trip times should not be considered active when other connections are available." raises more questions to me, than it clarifies the meaning of the term. At least I don’t know how a device would distinguish carrier-independence, end-to-end principles, or what is reasonable re delay. Also the qualifier "when other connections are available doesn't seem to help either.

How about: "The device has an active bearer connection to an Internet Protocol compatible network."

Thanks, 
Bryan Sullivan | AT&T

-----Original Message-----
From: jsalsman@gmail.com [mailto:jsalsman@gmail.com] On Behalf Of James Salsman
Sent: Monday, June 28, 2010 7:42 PM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: public-device-apis@w3.org; Tran, Dzung D
Subject: Fwd: changes to sysinfo (was Fwd: Agenda - Distributed Meeting 2010-06-23)

Bryan,

Do you have the source for the graphic that needs to be changed in the
system-info spec, or do we need to get that from Tran, or someone
else?

All,

What do you think of my recommendations to Tran for ACTION-183 below?

Sorry for the top-posting.

--James Salsman


---------- Forwarded message ----------
From: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Wed, Jun 23, 2010 at 10:22 AM
Subject: RE: changes to sysinfo (was Fwd: Agenda - Distributed Meeting
2010-06-23)
To: James Salsman <jsalsman@talknicer.com>, "SULLIVAN, BRYAN L
(ATTCINW)" <BS3131@att.com>

James,

Bryan has volunteered to update the spec as I am out for a couple of weeks.
Would you please work with Bryan on where we are with these changes?

Thanks
Tran

-----Original Message-----
From: jsalsman@gmail.com [mailto:jsalsman@gmail.com] On Behalf Of James Salsman
Sent: Wednesday, June 23, 2010 09:13 AM
To: Tran, Dzung D
Subject: changes to sysinfo (was Fwd: Agenda - Distributed Meeting 2010-06-23)

[Tran,]

I'm happy to say the changes below were approved.  However, it
resulted in another action item for you:
http://www.w3.org/2009/dap/track/actions/202


I noticed there will also be corresponding changes to
http://dev.w3.org/2009/dap/system-info/properties.png Please let me
know if you need help with that.

I noticed you have an earlier action item
http://www.w3.org/2009/dap/track/actions/183 about "Drop connections[]
and activeConnection, move to activeConnections[] and define clearly
what 'active' means".  I wish I could help you with that one.  You
might want to say "An active network connection is connected. Data
sent over an active network connection is expected to be delivered in
accordance with carrier-independent, end-to-end principles of internet
datagram delivery. Connections which do not conform to
carrier-independent, end-to-end principles with reasonable round trip
times should not be considered active when other connections are
available.  Disconnected and otherwise unavailable connections must
not be considered active."  Is that good?

Regards,
James Salsman


---------- Forwarded message ----------
From: James Salsman <jsalsman@talknicer.com>
Date: Wed, Jun 23, 2010 at 3:49 AM
Subject: Re: Agenda - Distributed Meeting 2010-06-23
To: Frederick.Hirsch@nokia.com, public-device-apis@w3.org


On Tue, Jun 22, 2010 at 2:36 PM,  <Frederick.Hirsch@nokia.com> wrote:
> Agenda — Device APIs and Policy Working Group — Distributed Meeting  #33  2010-06-23
>...
> 11) APIs - SysInfo
>
> Status
>
> 12) Capture...

Under items 11 and 12, please add these questions from ACTION-191 to the agenda:

11.A. At http://dev.w3.org/2009/dap/system-info/#widl-AudioCodecAttributes-compFormat

should "compFormat" be "compFormats"?  Accordingly, in interface
AudioCodecAttributes, should "attribute DOMString compFormat;" be
"attribute DOMString[] compFormats;"?

11.B. Should compFormats be a comma- and/or space-separated list of
MIME types instead of free form?

11.C. Should the examples for AudioCodecAttributes' compFormats be
"audio/x-speex;quality=7;bitrate=16000, audio/ogg" instead of
"'G.711', 'MP3', "MIDI'" (which includes encumbered types)?

11.D. In interface VideoCodecAttributes, should "attribute boolean
hwAccel;" be "attribute boolean[] hwAccel;"?

11.E. Should the examples for VideoCodecAttributes' compFormats be
"video/x-webm video/ogg" instead of "'H.264' or 'Theora'"?

11.F. At http://dev.w3.org/2009/dap/system-info/#idl-def-MicrophoneAttributes

(interface MicrophoneAttributes) should "attribute DOMString name;"
and "attribute DOMString types;" be included as the addressable
microphone device name and MIME types available from it, respectively?

11.G. Similarly, at
http://dev.w3.org/2009/dap/system-info/#idl-def-CameraAttributes

(interface CameraAttributes) should "attribute DOMString name;" and
"attribute DOMString types;" be included as the addressable camera
device name and MIME types available from it, respectively?

11.H. Is "image/png video/x-webm ..." a good example set of camera types?

12.A. At http://dev.w3.org/2009/dap/camera/#widl-FormatData-type

should "A valid MIME type for WAV sound file is audio/x-wav." be
changed to "A valid MIME type for speech is audio/x-speex"?

Thank you.  I think these changes have been approved, but I understand
I may have been too terse in ACTION-191.

Sincerely,
James Salsman
Received on Tuesday, 29 June 2010 05:27:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:10 GMT