Marcos Caceres wrote:
On Tue, Dec 2, 2008 at 12:22 AM, Jonas Sicking <[EMAIL PROTECTED]> wrote:
Marcos Caceres wrote:
On Mon, Dec 1, 2008 at 11:48 PM, Jonas Sicking <[EMAIL PROTECTED]> wrote:
Marcos Caceres wrote:
Ok, hearing no objections, then I propose we bake in the following
file extens
On Tue, Dec 2, 2008 at 12:22 AM, Jonas Sicking <[EMAIL PROTECTED]> wrote:
> Marcos Caceres wrote:
>>
>> On Mon, Dec 1, 2008 at 11:48 PM, Jonas Sicking <[EMAIL PROTECTED]> wrote:
>>>
>>> Marcos Caceres wrote:
Ok, hearing no objections, then I propose we bake in the following
file ext
Marcos Caceres wrote:
On Mon, Dec 1, 2008 at 11:48 PM, Jonas Sicking <[EMAIL PROTECTED]> wrote:
Marcos Caceres wrote:
Ok, hearing no objections, then I propose we bake in the following
file extensions into the spec (we can debate which MIME types to use
after we settle on the extensions!):
.h
On Mon, Dec 1, 2008 at 11:48 PM, Jonas Sicking <[EMAIL PROTECTED]> wrote:
> Marcos Caceres wrote:
>>
>> Ok, hearing no objections, then I propose we bake in the following
>> file extensions into the spec (we can debate which MIME types to use
>> after we settle on the extensions!):
>>
>> .html
>>
Hi Ian,
I think this is an interesting and important discussion, but I realize that
we've moved from discussing ZIP packages and URI references into them to a
deeper discussion of the role of architecture and orthogonality, language
specifications vs. implementation guidelines, the handling of
On Tue, Dec 2, 2008 at 1:42 AM, Marcos Caceres <[EMAIL PROTECTED]> wrote:
> Ok, hearing no objections, then I propose we bake in the following
> file extensions into the spec (we can debate which MIME types to use
> after we settle on the extensions!):
> .jpeg
you're missing .jpg which is fairly
Marcos Caceres wrote:
Ok, hearing no objections, then I propose we bake in the following
file extensions into the spec (we can debate which MIME types to use
after we settle on the extensions!):
.html
.htm
.css
.gif
.jpeg
.png
.js
.json
.xml
.txt
The following we should probably bake in too:
.
Ok, hearing no objections, then I propose we bake in the following
file extensions into the spec (we can debate which MIME types to use
after we settle on the extensions!):
.html
.htm
.css
.gif
.jpeg
.png
.js
.json
.xml
.txt
The following we should probably bake in too:
.mp3
.swf
.wav
.svg
.ico
Below is the draft agenda for the November 20 Widgets Voice
Conference (VC).
Two notes on this agenda:
1. NOTE the TIME CHANGE!
2. It is highly unlikely we will cover the Widgets DigSig spec or the
API and Events spec. Please review the related ACTIONs and respond
accordingly.
Inputs
Hi Dan,
On Mon, Dec 1, 2008 at 6:20 PM, Dan Brickley <[EMAIL PROTECTED]> wrote:
> Marcos Caceres wrote:
>>
>> On Mon, Dec 1, 2008 at 5:31 PM, Dan Brickley <[EMAIL PROTECTED]> wrote:
>>>
>>> Williams, Stuart (HP Labs, Bristol) wrote:
>>>
>> Well there are ways around that, add a package descri
Kartikaya Gupta:
> The example in the java-modules section has a
> typo; it says "org.foo.ext.FooDocument" instead of
> "org.foo.ext.ExtendedFooDocument".
Thanks, fixed.
> Also, I'm not sure if this matters, but while implementing I
> realized that having both [TheExtendedAttribute=identifier] a
Marcos Caceres wrote:
On Mon, Dec 1, 2008 at 5:31 PM, Dan Brickley <[EMAIL PROTECTED]> wrote:
Williams, Stuart (HP Labs, Bristol) wrote:
Well there are ways around that, add a package description
or meta-data file either at the root of the package or at
each directory level and have it carry
Hi Stuart,
On Mon, Dec 1, 2008 at 4:37 PM, Williams, Stuart (HP Labs, Bristol)
<[EMAIL PROTECTED]> wrote:
>
>> -Original Message-
>> From: Marcos Caceres [mailto:[EMAIL PROTECTED]
>> Sent: 01 December 2008 15:28
>> To: Williams, Stuart (HP Labs, Bristol)
>> Cc: [EMAIL PROTECTED]; public-w
On Mon, Dec 1, 2008 at 5:31 PM, Dan Brickley <[EMAIL PROTECTED]> wrote:
> Williams, Stuart (HP Labs, Bristol) wrote:
>
Well there are ways around that, add a package description
or meta-data file either at the root of the package or at
each directory level and have it carry media-ty
Williams, Stuart (HP Labs, Bristol) wrote:
Well there are ways around that, add a package description
or meta-data file either at the root of the package or at
each directory level and have it carry media-type information
- or use 'magic numbers' or (if you really must - in the
absense of other
Stuart,
ext Williams, Stuart (HP Labs, Bristol) wrote:
...
Anyway - that zip files don't intrinically maintain such info is not
a show stopper - though I would have thought that carrying media-type
information is a natural requirement for a packaging format for the
web.
Is it not the case th
Hello John,
> -Original Message-
> From: John Kemp [mailto:[EMAIL PROTECTED]
> Sent: 01 December 2008 15:35
> To: Williams, Stuart (HP Labs, Bristol)
> Cc: Marcos Caceres; [EMAIL PROTECTED]; public-webapps
> Subject: Re: Sketch of an idea to address widget/package
> addressing with fragID
Hello Art,
> -Original Message-
> From: Arthur Barstow [mailto:[EMAIL PROTECTED]
> Sent: 01 December 2008 15:10
> To: Williams, Stuart (HP Labs, Bristol); Marcos Caceres
> Cc: [EMAIL PROTECTED]; public-webapps
> Subject: Re: Sketch of an idea to address widget/package
> addressing with fr
> -Original Message-
> From: Marcos Caceres [mailto:[EMAIL PROTECTED]
> Sent: 01 December 2008 15:28
> To: Williams, Stuart (HP Labs, Bristol)
> Cc: [EMAIL PROTECTED]; public-webapps
> Subject: Re: Sketch of an idea to address widget/package
> addressing with fragID syntax and media-type
On Mon, 1 Dec 2008 11:12:13 +1100, Cameron McCormack <[EMAIL PROTECTED]> wrote:
> Done:
>
> http://dev.w3.org/2006/webapi/WebIDL/#idl-modules
> http://dev.w3.org/2006/webapi/WebIDL/#Prefix
> http://dev.w3.org/2006/webapi/WebIDL/#java-modules
>
>
The example in the java-modules section ha
On Mon, Dec 1, 2008 at 5:35 PM, John Kemp <[EMAIL PROTECTED]> wrote:
> Is it not the case that a zip file containing widgets is a representation of
> an HTTP resource in its own right?
no. it is not the case.
a widget is a widget in its own right, there may or often may not be a
similar object a
ext Williams, Stuart (HP Labs, Bristol) wrote:
The assumption here is that the package format also maintains
media-type information for each of the things that it contains
that all the packages, "outer", "innerpkg", "moreNestedPkg" and
"mypkg" are marked with a media-type that defines a f
Hi Stuart,
On Mon, Dec 1, 2008 at 10:29 AM, Williams, Stuart (HP Labs, Bristol)
<[EMAIL PROTECTED]> wrote:
>>
>> Unfortunately, widgets/zip do not maintain media-type information.
>> That information is derived from content-type sniffing heuristics as
>> defined in HTML5 [1].
>
> [Aside: Hmmm pr
Marcos, Stuart,
On Dec 1, 2008, at 5:29 AM, ext Williams, Stuart (HP Labs, Bristol)
wrote:
From: Marcos Caceres [mailto:[EMAIL PROTECTED]
Unfortunately, widgets/zip do not maintain media-type information.
That information is derived from content-type sniffing heuristics as
defined in HTML5 [
Hello Marcos,
> -Original Message-
> From: Marcos Caceres [mailto:[EMAIL PROTECTED]
> Sent: 28 November 2008 20:12
> To: Williams, Stuart (HP Labs, Bristol)
> Cc: [EMAIL PROTECTED]; public-webapps
> Subject: Re: Sketch of an idea to address widget/package
> addressing with fragID syntax a
25 matches
Mail list logo