Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mapping in HTML – A Proposal for a New Element

shkspr.mobi

Post reply on HN
Print view View original

11–20 of 59 posts

Re: Mapping in HTML – A Proposal for a New Element

#11

Post by j4ybee »

shabbyrobe wrote: post #8
j4ybee wrote: post #5

A long time ago, in a galaxy far, far away, I worked with some guys who put together an incredible proposal to ICANN for a new .geo TLD: http://www.ai.sri.com/dotgeo/ The proposal was not accepted, but .aero and .museum were, and we all now how those have since utterly revolutionized the internet.

Neat! Speaking of galaxy far, far away, the executive summary only mentions other planets in passing. I couldn't quite grok from scanning how you might access cells from the moon with this TLD. .aero may be questionable, but surely the boundless usefulness of .ninja or .moe isn't in dispute?

yeah, those came a little later, but 2000 was the first year ICANN was ready to accept proposals for TLDs beyond the original 7. They made a call for innovative new uses of the domain system. My colleagues proposed .geo, ICANN went with .biz, .info, .name, .pro, .aero, .coop, and .museum.

Full list of proposals that year here: http://archive.icann.org/en/tlds/app-index.htm

Re: Mapping in HTML – A Proposal for a New Element

#12

Post by ravenstine »

maxerickson wrote: post #10
betenoire wrote: post #7

If this is just "contact us" style maps, I couldn't agree more. But what good is a map that I can't customize to my use cases, to make it useful in my web app? How would I say, suggest restaurants nearby?

Presumably by dynamically adding (and styling) markers.

Possibly, but how often are markers useful unless the zoom factor is close enough to show streets or landmarks? Browsers could come shipped with basic country maps, but anything more granular than maybe state/province level is subject to frequent change.

Re: Mapping in HTML – A Proposal for a New Element

#13

Post by Sheepzez »

j4ybee wrote: post #5

A long time ago, in a galaxy far, far away, I worked with some guys who put together an incredible proposal to ICANN for a new .geo TLD: http://www.ai.sri.com/dotgeo/ The proposal was not accepted, but .aero and .museum were, and we all now how those have since utterly revolutionized the internet.

I may be being naive, but how is that different than including Google Maps JS lib on your page? I assume that component is just a wrapper around the GMaps JS lib?

Re: Mapping in HTML – A Proposal for a New Element

#14

Post by Sheepzez »

Sheepzez wrote: post #13
j4ybee wrote: post #5

A long time ago, in a galaxy far, far away, I worked with some guys who put together an incredible proposal to ICANN for a new .geo TLD: http://www.ai.sri.com/dotgeo/ The proposal was not accepted, but .aero and .museum were, and we all now how those have since utterly revolutionized the internet.

I may be being naive, but how is that different than including Google Maps JS lib on your page? I assume that component is just a wrapper around the GMaps JS lib?

Damn, wrong thread and I can't figure out how to delete from my app :P

Re: Mapping in HTML – A Proposal for a New Element

#15

Post by Sheepzez »

ricardobeat wrote: post #3

This is the exact use case for web components, except it doesn’t require browsers shipping their own implementation and updates - it’s all in userland. Example: https://www.webcomponents.org/element/keanulee/good-map

I may be being naive, but how is that different than including Google Maps JS lib on your page? I assume that component is just a wrapper around the GMaps JS lib?

Re: Mapping in HTML – A Proposal for a New Element

#16

Post by ArchReaper »

Is this suggesting that this would rely on browser implementation?

... Is this serious?

What motivation do browser-creators have to implement this? Google wants the javascript widget so they can properly track everything, among other reasons. Who would back this? Who would develop this?

This isn't like playing a media file, this is a highly interactive piece of content, with a metric shitload of complexity behind it. I don't think the author really understands the scope of what he is asking.

Although if you feel I'm mistaken, please enlighten me.

Re: Mapping in HTML – A Proposal for a New Element

#17

Post by betenoire »

maxerickson wrote: post #10
betenoire wrote: post #7

If this is just "contact us" style maps, I couldn't agree more. But what good is a map that I can't customize to my use cases, to make it useful in my web app? How would I say, suggest restaurants nearby?

Presumably by dynamically adding (and styling) markers.

How would you know where to add them if you can't see where they are and what is around them?

That's a big crux of the article, the browser shouldn't have/get to know where you are.

Re: Mapping in HTML – A Proposal for a New Element

#18

Post by [deleted] »

ArchReaper wrote: post #16

Is this suggesting that this would rely on browser implementation? ... Is this serious? What motivation do browser-creators have to implement this? Google wants the javascript widget so they can properly track everything, among other reasons. Who would back this? Who would develop this? This isn't like playing a media file, this is a highly interactive piece of content, with a metric shitload of complexity behind it.…

[deleted]

Re: Mapping in HTML – A Proposal for a New Element

#19

Post by shabbyrobe »

j4ybee wrote: post #11
shabbyrobe wrote: post #8

Earlier quoted context omitted.

Neat! Speaking of galaxy far, far away, the executive summary only mentions other planets in passing. I couldn't quite grok from scanning how you might access cells from the moon with this TLD. .aero may be questionable, but surely the boundless usefulness of .ninja or .moe isn't in dispute?

yeah, those came a little later, but 2000 was the first year ICANN was ready to accept proposals for TLDs beyond the original 7. They made a call for innovative new uses of the domain system. My colleagues proposed .geo, ICANN went with .biz, .info, .name, .pro, .aero, .coop, and .museum. Full list of proposals that year here: http://archive.icann.org/en/tlds/app-index.htm

Oh, I was joking about .moe, etc - I reckon .geo would be far more useful!

But my main question about the moon was quite serious - how would you access the moon with this? I couldn't quite understand how this part from the executive summary would translate to an actual DNS request:

"One special GeoRegistry must have a server assigned to every cell on the planet. This GeoRegistry will be called the default GeoRegistry named "earth." (The names of the other planets will be reserved for interplanetary geodata.) The default GeoRegistry will be used when client queries do not specify a GeoRegistry name, or when the specified GeoRegistry does not have an assigned cell server."

Kinda cool that .geo predates Google Maps by about 4 or 5 years!

Re: Mapping in HTML – A Proposal for a New Element

#20

Post by flukus »

Why not something more like RSS that can be opened in a real app instead of a browser widget? I believe google earth has something similar already. Then we get to choose the best map application (or have several) and we don't have to say "well I like firefox but the maps aren't as good as chrome".
Post reply on HN