BTW: When it comes to some page/web-app instantiating a widget... how does
the
publisher/developer make reference to the widget to be instantiated and/or
the
package from which it is to be instantiated (if those are regarded as
separate
things)?
I'm sorry, I'm not sure I
Hello Marcos,
-Original Message-
From: Marcos Caceres [mailto:marcosscace...@gmail.com]
Sent: 04 December 2008 22:21
To: Williams, Stuart (HP Labs, Bristol)
Cc: www-...@w3.org; public-webapps;
public-pkg-uri-scheme-requ...@w3.org
Subject: Re: Sketch of an idea to address
On Fri, Dec 5, 2008 at 3:42 PM, Jonathan Rees [EMAIL PROTECTED] wrote:
I hate to burst ignorantly into a discussion I know little about... but
that's what I'm going to do. Forgive me.
Regarding the creation of local URIs for use in APIs requiring URIs: I want
to consider, just as a what-if
On Dec 6, 2008, at 9:58 AM, timeless wrote:
On Fri, Dec 5, 2008 at 3:42 PM, Jonathan Rees
[EMAIL PROTECTED] wrote:
I hate to burst ignorantly into a discussion I know little about...
but
that's what I'm going to do. Forgive me.
Regarding the creation of local URIs for use in APIs
Hi Jonathan,
On Sat, Dec 6, 2008 at 3:21 PM, Jonathan Rees [EMAIL PROTECTED] wrote:
On Dec 6, 2008, at 9:58 AM, timeless wrote:
On Fri, Dec 5, 2008 at 3:42 PM, Jonathan Rees [EMAIL PROTECTED]
wrote:
I hate to burst ignorantly into a discussion I know little about... but
that's what I'm
I hate to burst ignorantly into a discussion I know little about...
but that's what I'm going to do. Forgive me.
Regarding the creation of local URIs for use in APIs requiring URIs: I
want to consider, just as a what-if meant for clarification of
requirements, the use of the tag: URI
Marcos,
The TAG suggested that I re-post the idea that I floated at the beginning of
this thread on the new list at [EMAIL PROTECTED] and encourage any continuation
of this thread to take place there - which I have now done [1].
Also, with some irony, I think that I'm beginning to get a
Hi Stuart,
On Thu, Dec 4, 2008 at 8:02 PM, Williams, Stuart (HP Labs, Bristol)
[EMAIL PROTECTED] wrote:
Marcos,
The TAG suggested that I re-post the idea that I floated at the beginning of
this thread on the new list at [EMAIL PROTECTED] and encourage any
continuation of this thread to
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 and
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
Hi Stuart,
On Mon, Dec 1, 2008 at 10:29 AM, Williams, Stuart (HP Labs, Bristol)
[EMAIL PROTECTED] wrote:
snip
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 process
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 fragment
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
-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 defn.
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 fragID
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
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
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-type information
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-webapps
[Resending with minor corrections and to get tracker's attention and include
public-webapps]
I just wanted to float an outline of a not very baked idea for trying to solve
the widget referencing problem with a media-type/fragment identifer approach
- those IMO being the 'right' extension
On Fri, Nov 28, 2008 at 3:52 PM, Williams, Stuart (HP Labs, Bristol)
[EMAIL PROTECTED] wrote:
I just wanted to float an outline of a not very baked idea for trying to
solve the widget referencing problem with a media-type/fragment identifer
approach - those IMO being the 'right' extension
21 matches
Mail list logo
