Re: RWW Community Group General Scope & Book Keeping

Heya,

andrei - great paper and congratulations ;) 

notes and ideas

ps; lots of activity over at https://github.com/stample - i.e. https://github.com/stample/react-foaf

Got a query about the standards; metadata support and ‘app deployment’. 

Theory is that standard files can be referenced (or queried) via .meta files; so therein, the creation of those .meta files.

Media files are a good example; image, video, audio.  (i’m thinking partly about heritage data storage / access and http://www.openarchives.org/pmh/ 

so; i envisage imagemagick could be used to parse files and create a .meta file that stores the metadata for rww / sparql targeting; but then, two issues; master / derivatives and maintaining the metadata in the file when exported. 

I imagine apps might want a standard way to target the .meta files with similar expectations for the file outcome? then there may be a ‘losslessly digitised’ 300MB TIFF file, that has a bunch of derivatives attached to it (colour corrected by community, print ready, browser ready, thumbnails, etc.); so that brings about a question of ‘hypermedia’ management and standardised interfaces i guess...

Second thing is ‘app deployment’. 

Perhaps creating a method to integrate with github could be one method (or app method?); but overall, the idea of app deployment.  Obviously there’s a few different rww-servers at the moment; i’m envisaging they’ll have different functionality at different versions, etc. however may need different app branches to work with different rww-servers?  I know there’s demo.rww.io as well as some newer apps like https://github.com/stample/react-foaf (which is tested currently for rww-play). 

i’m currently having a look at https://github.com/oerpub/github-bookeditor/  inc; https://github.com/philschatz/epub.js and https://github.com/hypothesis (or other annotation method); which has also come across two new considerations 

1. Maintaining or registering a unique ‘username’ - simply use a standard userid; or can / should it be a multi-faceted username?  how can one tell between one ‘smith’ and another. 
2. with regard for services (like the media thing) the use of RSS and IRC for messaging? 

i think there was a function or concept of .known/ ?? is there a standard .js or .rdf ? 

i imagine in part the storage / services need to be capable of being distributed; for example, transcoding or storage on multiple servers with rules - might have big tiff’s stored on amazon glacier and smaller jpgs. stored on shared hosting somewhere else.  perhaps that brings about a data-storage app; that might consider rules around archiving larger files… 

perhaps overall; there’s a basic set of tools that seem to be needed; a bit like the old dos disks, not just command.com.  so, how is the scope for these tools defined and how do we ensure that work done is compatible across different raw-server implementations.  Secondly; as it’s online, the 'app deployment’ methods are important too.

Finally; on those aspects; i realised that the ‘user’ world has cut/copy/paste, whereas developers use ‘branch’, ‘fork’, ‘pull’ etc. the latter makes more sense for the world of rww users, copy seems a bit old-hat.

timh.

On 30 Jan 2014, at 9:29 am, Melvin Carvalho <melvincarvalho@gmail.com> wrote:

> Hi All
> 
> As co-chair of this group, every so often, I send out a post asking if the group is everything the members want it to be.  If we can be doing more of some things, or less of other things.
> 
> Firstly, for everyone new that has joined, welcome!
> 
> The group is based on like minded individuals using web standards to read and write.  We are currently one of the top 10 biggest Community groups at the W3C.  We dont currently have a charter, but the current scope, written about a year ago, of our work is outlined here:
> 
> http://www.w3.org/community/rww/wiki/Scope
> 
> Let us know if there's anything we can add or remove, or if items are out of date.  I will be happy to update this page based on feedback.  I think the work on ACLs and with LDP will get to more advanced stages this year.
> 
> I've been doing a "Monthly Open Thread" for a couple of years, the idea was that people post there news, but it's sort of turned more into a "status update", so I may change the name as appropriate.  I'd like to try sending this out quarterly, rather than monthly, as it may be easier to aggregate good content.  However, if activity picks I'll revert back to monthly.
> 
> For those interested in translating existing apps to the read write web, I've started a group "Webize Everything" [1]
> 
> Lastly, I'd like to congratulation our co-chair Andrei in his new position working at MIT, in Tim Berners-Lee's Team, in Boston.
> 
> Please dont hesitate to contact Andrei or myself, on list or privately if there's anything you'd like to ask, or feel that we could be doing.  
> 
> Looking forward to working with you all, and a productive next year!
> 
> Best
> Melvin
> 
> [1] http://www.w3.org/community/webize/