Re: Directories of Projects to Webize

On 28 Jan 2014, at 3:31 pm, carmen <_@whats-your.name> wrote:

>> data.fm given it’s simple (php) based nature
> 
> especially like that it's simple enough to read without digging 12-directories-deep or spending 3 days just to get through the codebase. one could argue that it satisfies many of the <http://suckless.org/philosophy> principles (as did, arguably HTTP/HTML v1990 vs architecturally-astronomic competing hypertext/info-systems)
> 
> on fork/push and other workflows, there's been some w/ that as offshoots of provenance and UI projects
> 
> <http://www.w3.org/2005/01/wf/flow>
> 
> are you sure you couldn't do something similar with ldphp.datafm.rwwio (Whatever it's called this week - ie whose fork on github?) where fork = GET originating server -> PUT your server, make edits, provenance pointing back to original (with some kind of POST contrib/ or incoming/ notify to source server to alert of derivatives)

Agreed.  Reviewing https://github.com/stample/react-foaf - it’s described an “LDP Server”, however when reviewing the stample raw-play wiki https://github.com/stample/rww-play/wiki it’s more than simply ldp.  

We do need a name we can stick to. ;)  The other note is that perhaps we need a branch method / system for different “webize servers” (whatever they’re called).  

found https://github.com/annotorious/annotorious-semantic-tagging-plugin and https://github.com/okfn/annotator which looks really promising - the latter having different ‘hooks’ for store / auth. 


> Agreed - Rev