gRegorLove, Soopaman, eschnou and KartikPrabhu joined the channel
#tantekone big challenge for h-entry is - how do we allow/encourage innovation with / on top of it, without it just becoming a dumping ground for dozens of new properties?
#aaronpkto avoid needing to add new properties for different kinds of objects, you'd have to have a way for h-entry to have a place to put unknown/new objects
#aaronpkfor example, I want to publish my bike rides, which have a set of properties like "duration" and "average speed" not to mention the actual route data with all the location points.
#aaronpkI could define a new object, h-x-route and say that this object has all these properties
#tantekall microformats allow arbitrary new objects - they just go into the children collection
#tantekthere is no need for new properties for new nested objects
#aaronpkaha there is children! I kind of forgot about that!
#tantekchildren is the trivial modularity extension mechanism built-into all microformats
#tantekthus leaving you to "just" come up with figuring out what your new object needs (if you even need one), and then marking up your content as such
#aaronpksince it would need to look at what is in the children
#tantekit would when such things become a practice
#aaronpkconsumers of an h-feed that know how to render routes would just need to look for whether there is an h-x-route object as one of the children of the h-entry
#aaronpkthen a reader could show a little map and stuff
#tantekwhich then begs the question - does post type discovery itself need to have a core and have modularity for others to extend it?
#aaronpkright now i'm storing the route object on a property called "route" internally. when I want to use it, I check "is there a value for the route property" and then use it
#aaronpkif I switch, the "is there a route" would have to change to iterate over the children and look for an "h-route" object there
#aaronpkthis may be a problem if I want to store more than one object of the same type that mean different things, like a start and end location (contrived example)
#tantekthe duration is presumably *actual* instead of *estimated*
#tantekthe method of transport (bike vs walk vs car) is also typically published in directions (e.g. google maps)
#aaronpkit's not really directions summary since it's actual location traveled rather than planned, and i would also never describe the route in words used to describe directions
#tantekseems like the text equivalent for the image could describe the route in words similar to those used in directions
#tantekand would be useful for accessibility, search indexing etc.
#aaronpkeven if there were a good API for that, there's still the problem of describing the route as I run through the park where there are no street names and the path wanders around
#tommorristantek: OSM has Nominatim for reverse geocoding and there are open source routing engines on top of OSM data (have seen them support cars, cycles, walking, even horse riding)
#tommorrisIf the GPX is too large, run a simplification algorithm over it
#aaronpki just think a route doesn't make sense to have timing information necessarily, nor does it convey that it is a thing that happened at a single point in the past
#tommorrisClass object distinction between the route and the individual run/walk/cycle through it?
#tantekyou can brainstorm the name / bikeshed later too - ok to have a page like route-examples and then come up with h-somethingelse later
#tantektommorris: hence why I thought of directions