On Thu, 2016-05-26 at 22:44 +0000, Van Ulden, Joost (NRCan/RNCan) wrote: > I approached a couple of folks at ApacheCon in Vancouver about some > work that I am involved with that would benefit from an httpd module. > I am sending this message to the list to provide more information, and > to seek advice on how we should proceed. > > We are developing a format we call “Map Markup Language”, or MapML. > The objective of this format is to describe Web map semantics – that > is scale / zoom, projection, extent, features, styles, licenses, > legends in the context of a hypermedia media type that can be > manipulated / interacted with through the uniform interface alone. We > would like to eventually register the format as text/mapml.
This is seriously interesting. I need to take a look, and will be well pleased if I can find time to take an active interest. > A Java servlet prototype for this functionality is available: I have yet to look at that. Would you plan the module and servlet to grow in parallel as alternative implementations, or each to take its own path? Presumably there is something to be gained with the two alternative implementations? > We would like some advice on how to proceed with the development of a > module. For instance should we pursue this as a third-party module? > Can we tap into the community for development assistance if we don’t > have the required skills in-house? Any advice would be appreciated. You've had a couple of suggestions from Bill: I would agree that either github or the apache incubator make sense and are options worth considering (the latter could lead to it eventually becoming a sub-project of httpd itself). I would think, let the servlet be your guide. If it's thriving then you have a good model. If not, you learn lessons from it. Either way, thanks for posting to tell us about your project! As Jacob points out, the modules-dev list is a good resource for technical help. It's low-traffic, but still populated by a fair few people willing and able to help. -- Nick Kew
