The Maps in HTML Community Group seeks to establish at least one hypermedia type which can be considered to be consumed by a (new) "map" element for HTML. Follow-on from Bar Camp at #lgd14. The objective will be to define a hypermedia type which can be linked to from a hypothetical (but prototyped in Web Components) "map" or (geo-map for Web Components) element which will provide simple mashup capabilities and user interface.
As an active developer of the OpenLayers mapping library, I have been working a lot on performance improvements in the rendering pipeline. Performance is usually good, but there are corner cases where the user experience is negatively affected by an unresponsive user interface. There is a new browser technology, OffscreenCanvas, which allows rendering in web workers that run in parallel to the main thread. Unfortunately it is not widely supported in mainstream browsers. In this post, I am going to show how rendering performance in OpenLayers could benefit from OffscreenCanvas.
New post today about the GeoWeb here. The topic is the intersection of interests of the Web and Web mapping communities, and so can be a bit hard to think about because you have to put yourself (in most cases) in the other person’s shoes.
There is a new Maps4HTML organization on GitHub, dedicated to the use of the Maps For HTML Community Group. Every member of this Community Group has received an invitation to join the members team on that organization. Members can create repos associated to the organization.
A key factor in the success of any Web standard is community. To that end, if you accept the invitation to join the Maps4HTML community on GitHub, please consider making that fact public. Your presence on the front page of the organization will help drive other interested people and companies to join us.
The objective of the Maps4HTML organization on Github is to help us collaborate not just on ideas, but on actual specification and implementations of those ideas. You will find a few repos already there which may help stimulate more ideas and prototyping. Go for(k) it!
Standards are hard. Just ask anyone who has been in the trenches of standards organizations working for the Web. Getting agreement on technical subjects requires a lot of effort, on the part of individuals and organizations. The broader in scope the intended standard, the greater is the requirement for simple, clear language, meaning and function. Importantly, the greater is the requirement for diverse community input, if not agreement.