I've no experience of the previous XML manifest files but I must admit
that I find the arguments for HTML quite persuasive.
My default and original position would have been for JSON.
I know that I for one will now be more open toward using HTML as a
data definition format in my own work.
On Tue,
You could in fact even embed JSON in HTML, like JSON-LD suggests:
http://json-ld.org/spec/latest/json-ld/#embedding-json-ld-in-html-documents
On 4 August 2013 22:23, Melvin Carvalho melvincarva...@gmail.com wrote:
On 1 August 2013 18:57, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Thu,
On Thu, 01 Aug 2013 20:24:40 +0400, Dimitri Glazkov
dglaz...@chromium.org wrote:
On Thu, Aug 1, 2013 at 6:17 AM, Marcos Caceres w...@marcosc.com wrote:
Hi Kornel,
Although I have complete empathy about your criticisms regarding JSON,
it is actually quite fit for this purpose. Using HTML in
On Thu, 01 Aug 2013 17:57:20 +0100, Tab Atkins Jr. jackalm...@gmail.com
wrote:
HTML is the Web's serialization format *for HTML, and other text-like
things*. As Kornel's example shows, HTML is *not* well suited to
holding key/value pairs or the like;
The ugly part is current lack of support
On 1 Aug 2013, at 18:29, Kornel Lesiński wrote:
On 1 August 2013 12:44:19 Scott Wilson scott.bradley.wil...@gmail.com wrote:
Or you could perhaps use XML. A bit like, er, this:
http://www.w3.org/TR/widgets/
Hehe ;)
I'm trying to address two things:
1. it's been shown ever and over
On 1 August 2013 18:57, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Thu, Aug 1, 2013 at 9:24 AM, Dimitri Glazkov dglaz...@chromium.org
wrote:
On Thu, Aug 1, 2013 at 6:17 AM, Marcos Caceres w...@marcosc.com wrote:
Hi Kornel,
Although I have complete empathy about your criticisms
Or you could perhaps use XML. A bit like, er, this:
http://www.w3.org/TR/widgets/
On 18 Jul 2013, at 14:57, Kornel Lesiński wrote:
I'd like to propose using HTML as basis of manifest format, similar in spirit
to Web Components imports, e.g.
link rel=manifest import
Hi Kornel,
Although I have complete empathy about your criticisms regarding JSON, it is
actually quite fit for this purpose. Using HTML in the way you describe is
kinda problematic, in that it could include scripts and other resources:
basically, one would need to build a DOM to parse out the
On Thu, Aug 1, 2013 at 6:17 AM, Marcos Caceres w...@marcosc.com wrote:
Hi Kornel,
Although I have complete empathy about your criticisms regarding JSON, it is
actually quite fit for this purpose. Using HTML in the way you describe is
kinda problematic, in that it could include scripts and
On Thu, Aug 1, 2013 at 9:24 AM, Dimitri Glazkov dglaz...@chromium.org wrote:
On Thu, Aug 1, 2013 at 6:17 AM, Marcos Caceres w...@marcosc.com wrote:
Hi Kornel,
Although I have complete empathy about your criticisms regarding JSON, it is
actually quite fit for this purpose. Using HTML in the
On 1 August 2013 12:44:19 Scott Wilson scott.bradley.wil...@gmail.com wrote:
Or you could perhaps use XML. A bit like, er, this:
http://www.w3.org/TR/widgets/
Hehe ;)
I'm trying to address two things:
1. it's been shown ever and over again that developers on the wild web are
really bad at
I'd like to propose using HTML as basis of manifest format, similar in
spirit to Web Components imports, e.g.
link rel=manifest import href=/my-app-definition.html
and then my-app-definition.html could contain link, meta or other
elements.
Rationale:
* while JSON is wonderful for
12 matches
Mail list logo
