>I think it's better to use a free-form text instead of trying to come up >with a strict syntax to communicate when the capsule should be online. >I'm not convinced it is worth for robots to know these schedules, given >all the complex schedule one can have (and the rabbit hole for the >"perfect" syntax that covers all possible situations is pretty deep.) Right, the <schedule> and <contact details> in my example were simply meant to be placeholders for a natural language description of both of those things, not some formal specification that'd be machine readable. While being machine readable might be nice, I think the least effort for the most reward implementation is just a natural language message the capsule host can stick in their DNS and clients can fetch and display as is.
---
Previous in thread (22 of 37): 🗣️ Jonathan McHugh (indieterminacy (a) libre.brussels)
Next in thread (24 of 37): 🗣️ Oliver Simmons (oliversimmo (a) gmail.com)