Closed pfefferle closed 11 years ago
Sorry for the late response. I initially added the implementations sections based on the one in the Pingback spec but I'm not sure about how to handle it, especially given the fact that at some point the spec will be frozen but the list of implementations will need to be edited as more implementations come about. One solution that I'm leaning towards is to externalize it into it's own page and have the spec point to it.
What do you think about a jekyll site like http://activitystrea.ms or http://webfinger.net ... that makes it possible to provide several pages and several spec like http://webmention.org/spec/0.1 or http://webmention.org/spec/0.2 ...
I do that already with git. Each version points to revisions at which previous versions were frozen (See for example how this points to version 0.1: https://github.com/converspace/webmention/tree/v0.2).
I think you misunderstood the problem. IMO, the list of implementations shouldn't be part of the spec but maintained as a separate informational resource.
I know what you mean... I mentioned it, because so it is easier to setup pages you can reference...
I like the concept of webfinger.net (https://github.com/webfinger/webfinger.net). @willnorris used the gh-pages as master and so it is very easy to make changes on the site without the whole branching and merging stuff. We still can use this rep to develop the spec.
Created a separate implementations file.
or have you thought about libs only?