- From: Robin Berjon <robin@w3.org>
- Date: Wed, 05 Feb 2014 10:55:16 +0100
- To: Innovimax W3C <innovimax+w3c@gmail.com>, Neil Jenkins <neilj@fastmail.fm>
- CC: HTML for Email Community Group <public-htmail@w3.org>
On 05/02/2014 10:06 , Innovimax W3C wrote: > The problem here seems like W3C and all other people around are **not** > going in that direction: > > I would say that 99% of the spec today are Javascript APIs Well, except that the actions that Neil is pointing to are built on top of multiple W3C technologies and using vocabularies shepherded through a W3C IG. So it's certainly not all JS — that's just what you hear from some crowds. > I have a (not so?) simple use case: > > I want to add an embedded map of the receiver's neighborhood in an email > I send to tell friends how to get to the party, but I don't want to make > special mail for each. This use case implies that > 1) the receiver agree that the script uses its current location in order > to draw the correct and uptodate map > 2) stores a snapshot of the maps in the mail such that you can use it > offline > 3) be able to pan or zoom in (even offline if it's vector graphics) > > I want this kind of thing being possible without too much hassles: > if we could go declarative in a reasonable time frame (say few months) > I think we can declare victory That's not a complex problem. You can use existing tooling to mark up part of the content of the email as your address. The clients can then turn this into an interactive card that offers the reader the ability to see her directions. It's in fact a lot better than having you generate maps for everyone since you don't know where they may be coming from, you don't know what style of maps they prefer, maybe they need a more accessible variation, etc. -- Robin Berjon - http://berjon.com/ - @robinberjon
Received on Wednesday, 5 February 2014 09:55:28 UTC