CHBEIR Richard | 2 Jun 16:02 2008
Picon

CSTST 2008 : Submission deadline on June 15th 2008


****************************************************************************************************************

   The Fifth International Conference on Soft Computing as Transdisciplinary
Science and Technology (CSTST'08)
                                  October 27-31, 2008
                                  Cergy-Pontoise/Paris, FRANCE
                      Hosted by the "University of Cergy Pontoise"
                              http://sigappfr.acm.org/cstst08/

****************************************************************************************************************

Sponsorships:
    IEEE Systems, Man, and Cybernetics Society (Technically Co-sponsored)
    IEEE France (Technically Co-sponsored)
    ACM SIGAPP.fr (In Cooperation with)
    European Neural Network Society (ENNS)
    European Society for Fuzzy Logic and Technology (EUSFLAT)

Description
**********************

The International Conference on Soft Computing as Transdisciplinary Science and
Technology (CSTST'08) brings together international soft computational
intelligence researchers, developers, practitioners, and users.
The aim of CSTST (previously called WSTST) is to serve as a forum to present
current and future work as well as to exchange research ideas in this field.
CSTST'08 invites authors to submit their original and unpublished work that
demonstrates current research in all areas of soft computing, as well as
proposals
(Continue reading)

[widgets] User agent conformance


   According to the latest editor's draft (20 may 2008), a conforming 
widget user agent needs to support zip/deflate, png, gif, xml, xmlns and 
DOM3CORE. However, a conforming widget resource can also include other 
kinds of contents (eg. SVG, SMIL, etc.) Thus there is no way in the 
current draft for a user agent to check beforehand if it will actually 
be able to run the widget. A solution could be to add in config.xml the 
list of additional mime types a user agent must process for a given 
resource :
<widget xmlns="http://www.w3.org/ns/widgets"
         id="http://datadriven.com.au/exampleWidget"
         version="2.0 Beta" height="200" width="200">
   <name>The example widget!</name>
   ...
   <requires mime="image/svg+xml"/>
   <requires mime="application/smil"/>
</widget>

Also, in §5.2 [1] it is said that support for text/html is required. 
Should this be added to §3 [2] ?

	Fabrice

[1] http://dev.w3.org/2006/waf/widgets/#default
[2] http://dev.w3.org/2006/waf/widgets/#widget
--

-- 
Fabrice Desré
France Télécom R&D/MAPS/AMS
Tél: +(33) (0)2 96 05 31 43
Fax: +(33) (0)2 96 05 39 45
(Continue reading)

Arthur Barstow | 5 Jun 14:02 2008
Picon

[widgets] Minutes from 5 June 2008 Voice Conference


The minutes from the WAF WG's June 5 Widgets voice conference are  
available at the following and copied below:

  <http://www.w3.org/2008/06/05-waf-minutes.html>

WG Members - if you have any comments, corrections, etc., please send  
them to the public-appformats mail list before June 12; otherwise the  
minutes will be considered approved.

-Regards, Art Barstow

    [1]W3C

       [1] http://www.w3.org/

                                - DRAFT -

                        Widgets Voice Conference

05 Jun 2008

    [2]Agenda

       [2] http://lists.w3.org/Archives/Member/member-appformats/ 
2008Jun/0000.html

    See also: [3]IRC log

       [3] http://www.w3.org/2008/06/05-waf-irc
(Continue reading)

Charles McCathieNevile | 5 Jun 17:21 2008
Picon

Re: Geolocation ideas


Cc+ appformats, since it seems that we will be merged with them soon and  
they should get a chance to comment too (although there is a large overlap  
I don't think it is 100%).

On Tue, 03 Jun 2008 17:33:53 -0300, Ian Hickson <ian <at> hixie.ch> wrote:

> Hey Chaals,
>
> Could you please confirm that it is acceptable for us to begin
> unofficially discussing geolocation API requirements on the
> public-webapi <at> w3.org mailing list and for us to start noodling on ideas  
> in CVS in the http://dev.w3.org/cvsweb/2006/webapi/ directory? We would
> like to start today.

I cannot stop you doing it. On the other hand, given that there is an  
existing mailing list and that you have been explicitly asked to use it  
for the topic it was set up for, it seems a bit small-minded not to do so.  
Is there any obvious reason for continuing the discussion here that has  
escaped my attention? I am concerned about the effect one can observe in  
HTML, where effective transparency is destroyed by the fact that there are  
an large set of different discussion fora one needs to track in order to  
discover where relevant information is, making it very difficult to  
determine what is being proposed, let aone decided, unless one works  
full-time on HTML. I don't see that as conducive to good, informed open  
development.

I would therefore request that you keep discussion on this topic to the  
mailing list designed to gather it in one place.

(Continue reading)

Doug Schepers | 5 Jun 22:09 2008
Picon

Re: Geolocation ideas


Hi, Chaals-

Charles McCathieNevile wrote (on 6/5/08 11:21 AM):
> 
> If there is no apparent movement in the time between now 
> and our face to face meeting, that may be time to take it up again. In 
> the meantime why not give the W3C Team a little credit for acting in 
> good faith, and the time to do their work at a reasonable rate?

Thanks for the support.  I am conscious of the potential delay, and I'm 
trying to mitigate it as much as possible.

> Since the webspace at dev.w3.org/2006/webapi is just a set of addresses 
> for convenience, and since we are discussing something that is clearly 
> some kind of WebAPI, unless there is some process reason I don't know of 
> or you do something blatantly stupid like trying to make a document look 
> like it has more W3C support than it does through inappropriate use of 
> stylesheets, missing or misleading status statements and so on, I don't 
> see that it is impossible to put a proposal for a spec into that space. 
> Indeed, there is no reason I can see that a geolocation group could not 
> continue using a chunk of that space, given that there is trust between 
> the members of the two groups not to step on each other's work.

Matt Womer set up a (temporary?) playground to submit geolocation API 
documents for discussion:
     http://dev.w3.org/geo/
and
     http://dev.w3.org/geo/api

(Continue reading)

Ian Hickson | 5 Jun 23:01 2008
Picon

Re: Geolocation ideas


On Thu, 5 Jun 2008, Charles McCathieNevile wrote:
> > 
> > Could you please confirm that it is acceptable for us to begin 
> > unofficially discussing geolocation API requirements on the 
> > public-webapi <at> w3.org mailing list and for us to start noodling on 
> > ideas in CVS in the http://dev.w3.org/cvsweb/2006/webapi/ directory? 
> > We would like to start today.
> 
> I cannot stop you doing it. On the other hand, given that there is an 
> existing mailing list and that you have been explicitly asked to use it 
> for the topic it was set up for, it seems a bit small-minded not to do 
> so.

Okie dokie. We'll use the public-geolocation list. Happy birthday, btw. :-)

On Thu, 5 Jun 2008, Doug Schepers wrote:
> 
> Matt Womer set up a (temporary?) playground to submit geolocation API
> documents for discussion:
>     http://dev.w3.org/geo/
> and
>     http://dev.w3.org/geo/api

Cool, we'll use that.

Cheers,
--

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
(Continue reading)

Charles McCathieNevile | 6 Jun 01:56 2008
Picon

Re: Geolocation ideas


On Thu, 05 Jun 2008 23:01:28 +0200, Ian Hickson <ian <at> hixie.ch> wrote:

> On Thu, 5 Jun 2008, Charles McCathieNevile wrote:
>> >
>> > Could you please confirm that it is acceptable for us to begin
>> > unofficially discussing geolocation API requirements on the
>> > public-webapi <at> w3.org mailing list and for us to start noodling on
>> > ideas in CVS in the http://dev.w3.org/cvsweb/2006/webapi/ directory?
>> > We would like to start today.
>>
>> I cannot stop you doing it. On the other hand, given that there is an
>> existing mailing list and that you have been explicitly asked to use it
>> for the topic it was set up for, it seems a bit small-minded not to do
>> so.
>
> Okie dokie. We'll use the public-geolocation list. Happy birthday, btw.  
> :-)

Thanks and thanks :)

cheers

Chaals-the-slightly-more-connected

> On Thu, 5 Jun 2008, Doug Schepers wrote:
>>
>> Matt Womer set up a (temporary?) playground to submit geolocation API
>> documents for discussion:
>>     http://dev.w3.org/geo/
(Continue reading)

Charles McCathieNevile | 6 Jun 02:01 2008
Picon

Re: Geolocation ideas


On Thu, 05 Jun 2008 22:09:30 +0200, Doug Schepers <schepers <at> w3.org> wrote:

> Matt Womer set up a (temporary?) playground to submit geolocation API  
> documents for discussion:
>      http://dev.w3.org/geo/
> and
>      http://dev.w3.org/geo/api
>
> All of Chaals' caveats above apply to the new repo, too, of course... as  
> do any IPR issues you can think of.  And any documents can be sent to  
> the public-geolocation email list as attachments, too, if that is more  
> convenient.

Although there is a W3C policy on what kind of attachments are acceptable.  
In short, please use HTML if you have to do this. (Having versioned  
documents is far better than attachments IMHO)

>> Well, the reply gets out according to the vagaries of net access and my  
>> time, which is the same rule that always applies. You just picked the  
>> moment I finished work and went to celebrate my birthday as the time to  
>> send mail, which was perhaps an unluckily sub-optimal choice.
>
> Happy birthday!

Thanks ;)

cheers

Chaals
(Continue reading)

Picon

ISSUE-25: IIS and Access-Control-Policy-Path [Access Control]


ISSUE-25: IIS and Access-Control-Policy-Path [Access Control]

http://www.w3.org/2005/06/tracker/waf/issues/

Raised by: Anne van Kesteren
On product: Access Control

IIS servers have an issue in that resources can be addressed by several distinct URIs as explained in this e-mail:

http://lists.w3.org/Archives/Public/public-appformats/2008May/0039.html

This impacts the design of Access-Control-Policy-Path to some extent. Two proposals have been put
forward by members of the WG to address this issue:

A. If a URI (also one given during redirects, etc.) contains the "\.." sequence (or the escaped form) apply
the generic network error steps.

B. Warn against using the Access-Control-Policy-Path feature in servers that exhibit this behavior.

Picon

ISSUE-26: Opting into cookies [Access Control]


ISSUE-26: Opting into cookies [Access Control]

http://www.w3.org/2005/06/tracker/waf/issues/

Raised by: Anne van Kesteren
On product: Access Control

It has been suggested that because Access-Control also allows read access and not just making the request
explicit optin into cookies specifically is desired.

The benefit would be that servers can more safely enable Access Control functionality.

The drawback would be that the model becomes more complicated and therefore more prone to errors and
implementation bugs.


Gmane