W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2016

Re: [whatwg] Some Clarification on CML Proposal

From: MegaZone <megazone@megazone.org>
Date: Thu, 6 Oct 2016 08:15:49 -0400
Message-ID: <CAAF-Jg51YrFRazuVPJ3k1kvuPG-N4pQDmPhi5_1yVaCvzuR9-g@mail.gmail.com>
To: Jacob Villarreal <jv1597@yahoo.com>
Cc: whatwg <whatwg@lists.whatwg.org>, "rh_whatwg@skuldwyrm.no" <rh_whatwg@skuldwyrm.no>, Shane Hudson <successcircuit@gmail.com>
On Thu, Oct 6, 2016 at 7:42 AM, Jacob Villarreal <jv1597@yahoo.com> wrote:

> Sorry, correction on the code above:
> <source port:[ticker_port]><destination record:path/ticker_data.rec/+1>or,<destination
> record:path/ticker_data.rec/29>
> Thanks.

How is this any different from PHP, ASP, JSP, .Net, ColdFusion, etc?  You
could implement your CML on the backend and have it 'output'
XML/HTML+JavaScript+CSS for delivery to user agents with compatibility with
everything out there today.

If you want to try to replace HTML, JavaScript, and CSS so that every user
agent needs to understand CML natively - that's just not going to happen.

There are many server-side options and it really sounds like that's where
CML would fit.  Your developers would write in CML, and the 'engine' would
render that into the appropriate content for delivery to UAs.

Personally I don't see value in this proposal.

-MegaZone / Geek, Gweep, Technophile, me. / Hail Eris, All Hail Discordia
Personal: Google+ <https://plus.google.com/111890035512083705389/posts> /
Facebook <https://www.facebook.com/megazone> / Twitter
<https://twitter.com/#!/megazone> / LinkedIn
<http://www.linkedin.com/in/megazone> / LiveJournal
<http://zonereyrie.livejournal.com/> / Web <http://www.megazone.org/> /
Email <megazone@megazone.org>
Editor, Gizmo Lovers: Blog <http://www.gizmolovers.com/> / Google+
<https://plus.google.com/b/101158028647216708758/> / Facebook
<https://www.facebook.com/GizmoLovers> / Twitter
<https://twitter.com/#!/GizmoLovers> / Email <editor@gizmolovers.com>
"A little nonsense now and then, is relished by the wisest men" 432-363-4296
Received on Thursday, 6 October 2016 12:16:44 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:39 UTC