========================================= Projects: http://janastu.org/technoscience/index.php/JSoC ----------- Projects focus on: Participatorily creating, annotating, linking the Web data. Curation and presentation for the emergent needs. ------------------------------------------------------------------------- SWeeT Web http://janastu.org/technoscience/index.php/JSoC#SWeeT_Web ----------------- ____________ #Task S0313a SWeeTing Platform Brief description: Architect a platform for sweeting - should work across all browsers and mobile devices (mobile browsers essentially). Sweeting can happen in web pages or specialised apps to sweet about specific things. Sweets can be about annotations, renarrations, comments, interlinking data or anything as long as user provides an ontology/descriptor for that type. This platform should have the capabilities to record audio/video, take an image, take geo-location etc from the user's device, as well as the user can link any media/resource on the Web and publish it as a sweet. What we expect to see in your proposal: Javascript library development experience and a command on the DOM and the media elements' APIs. Expected results: A set of tools that can be deployed on the Web so that visitors can SWeeT, or as those that can be used in an app on an Android to aid the SWeeTing process. Knowledge prerequisite: Javascript, Android app development, jQuery and media APIs Mentor: SWeeT Web team ____________ #Task S03013b SWeeT store Brief description: Architect a platform for parsing and storing SWeeTs using Semantic Web technologies - a storage server to store and manage SWeeTs and the media mentioned in the SWeeTs. --The storage server does housekeeping for pre-defined media types and presents them in the way asked for. E.g An image must be available in all standard sizes and also an original. A video uploaded must be converted to WebM or other free formats. Clips of the video or the image need to be made available. - a RDF store to refer to when the types have to be validated. Users can contribute/load extended types to the rdf store, to get the data the way they want. - a parser will know what to "pick up" from the data at runtime or for caching needs. What we expect to see in your proposal: That you are conversant in semantic web technologies and have ideas about managing media fragments. That you are able to generate smart test data with million SWeeTs. Expected results: A responsive store that works with Alipi and other ongoing services. Knowledge prerequisite: Python, Mongodb, SPARQL and a command on data structures Mentor: SWeeT Web team ____________ #Task S03013c Scalable SWeeT Re-treats Brief description: SWeeTs are identified as aggregatable self-describing messages. A SWeeT can be used by many applications on the Web. These applications will need to filter and tune the SWeeTs for their needs. SWeeT Re-treat helps apply treatments to these SWeeT sources. A typical treatment can include curation, recommendation and workflow rules that can be used in contextual searches. What we expect to see in your proposal: A background in mining, analysing and utilizing twitter like feeds. Database data type specific optimisation that has been effectively utilized in a Web context. Familiarity with Semantic Web technologies. Expected results: A deployable feed server that can be queried by web-apis, given a specific treatment. Knowledge prerequisite: Python, Mongodb, SPARQL and a command on data structures Mentor: SWeeT Web team ____________ #Task S03013d Configurable SWeeTing plugins and apps Brief description: SWeeT Web is about making messaging about something simple. The possibility of a one-click in context. To build an app and a browser plugin that takes configuration info and extends the app to different contexts. For example, to message about a bio-diversity find, one need to point to an image drag and enter details or to report an incident or to annotate a relatedness of objects on the Web. Imagine a boilerplate structure that can help configure the interaction defined by structure of other SWeeTs that can be reused/copied. We need to study the SWeeT self-description and map it to interaction on a device. What we expect to see in your proposal: That you understand this by relating it to work you have done or have thought about related issues. That you have a penchant of writing generic applications that can be configured to a context. Expected results: A plugin and an app on android that can work for the case of re-narration and heritage annotation (see below) Knowledge prerequisite: Developed plugins for recent browsers or have developed native Android apps. Javascript, Parsing, HTML5. Mentor: SWeeT Web team, Alipi team, Cultual Heritage Tools team ____________ #Task S0313e SWeeTer Indentity Brief description: A significant part of a SWeeT is the identity of the person SWeeTing. There are many ways to ask the user to identify oneself. There could be a need to do a Sign-up and Sign-in process or to take the persona.org approach or to ask a user to authenticate using their web presence elsewhere among the popular social networking sites. Part of the Identity is also one's presence in their society or friend circles. What we expect to see in your proposal: Clarity of Identity management on the Web and a strong interest in creating social networking platforms. Expected results: Identity management service with provision for "anonymous" identities (identity disguise). Knowledge prerequisite: persona.org, openid, PGP/GPG and familiarity with cross service signin. Mentor: SWeeT team ____________ #Task S0313f SWeeT Cache Brief description: A service that assists by providing a cache of objects referenced in a SWeeT. This cache helps in direct fecthing of the objects instead of real time fetching the object from the Web. When several objects need to be fetched in a given context, the retriving then in real time can slowdown a rendition based on SWeeTs. These objects are typically referenced using a combination of XPaths and URLs. Caching would involve pre-fetching and keepin a copy of the element or a part of an image or a map or a video. What we expect to see in your proposal: Experience with grabbing parts of a Web page or an element on a page or part of an image. Expected results: A deployable cache that can be tuned for a specific rendering context Knowledge prerequisite: CSS3, DOM, Javascript, Image, Audio and Video APIs knowledge Mentor: SWeeT Web team ____________ #Task S0313g SWeeT Swagger Brief description: Architect a platform which can query according to user/other profile or preference to bring together SWeeTs from related types (annotations, renarrations, comments) to be presented to the user. The content in these SWeeTs are presented with the original/reference object in an accessible way. Different presentation style (e.g., virtual walk or re-narration) should render these accessible. - the querying platform can connect to various service providers who gather (and parse) sweets; query them and get sweets based on user input preferences. - Implement an architecture to support various presentation algorithms that can be applied to present a mash up of the requested data. - Implement an algorithm to come up with a way of suggesting a mash up (e.g., currently the latest re-narration wins) What we expect to see in your proposal: That you have experience and maturity in concieving game-like dynamic user interaction spaces. That you can conceptualize a virtual heritage walk, with audio, video and images that a user can walk by like when you walk in a museum with audio-visuals that are tuned to your profile. Expected results: A virtul walk rendition for context of Hampi (we have a large collection of media and SWeeTs). Knowledge prerequisite: Serverside Python, CSS3, DOM, Javascript, Image, Audio and Video APIs knowledge Mentor: SWeeT Web team ------------------------------------------------------------------------- Alipi - Re-narration Web http://janastu.org/technoscience/index.php/JSoC#Alipi_-_Renarration_Web --------------------------------- What we already have - client side JS library for renarration and publishing alternative narratives. Authoring of narratives now only has adding text, refering text from some other page, and refering to other images on the web or local disk. Publishing can be done on user's personal blog or the service provider's blog. - API endpoints to query for re-narrations. - Annotation tools using OpenLayers and SWeeTing the annotation. - Renarration service (see htttp://alipi.us) that renders alternative narratives ____________ #Task A0313a Publishing and SWeeTing Brief description: A platform for SWeeTing often depends on dynamically creating multi media content that can be posted on the Web by the author which can then be referenced in a SWeeT attribute. For example, when re-narrating a page, one would want to also create alternative narratives (and not just assume the alternative narratives exist already). Should work across all browsers and mobile devices (mobile browsers essentially). Sweeting can happen in web pages or specialised apps to sweet about specific things. Sweets can be of type annotations, renarrations, comments or anything as long as user provides an ontology/descriptor for that type. This platform should have the capabilities to record audio/video, take an image, take geo-location etc from the user's device, as well as letting the user link any media orresource on the Web and publish it as a SWeeT. Posting of the content authored in the SWeeTing process needs to be done in user prefered location and the resulting references mentioned in the SWeeT. What we expect to see in your proposal: An appreciation of the renarration web by relating it to a real need you have observed. And comfort with browser technologies and familiarity with issues related to posting content on the web, including blogs and social networking sites. Expected results: An exhanced authoring tool compared to the one that exists now for renarration. Knowledge prerequisite: Javascript, jQuery, HTML5 Mentor: Alipi team _________ #Task A0313b' Renarrating talkenglish.com and other english learning content Brief description: Tools to renarrate english teaching sites for the kannada (or another) community with a visual directory of re-narrated work that is tunable for an individual user. Curation of narratives with tools to ease curation. What we expect to see in your proposal: Experience with content retargeting; text to visual storytelling Expected results: Deliver tools with english learners renarration directory Knowledge prerequisite: Javascript, HTML5, CSS3, Python Mentor: Alipi team ___________ #Task A0313c * Renarration games ------------------------------------------------------------------------- Cultural Heritage - digital tools http://janastu.org/technoscience/index.php/JSoC#Cultural_Heritage_Tools ----------------------------------------- ___________ #Task H0313a Traditional Storytelling in the future Probir and patachitra ___________ #Task H0313b Tools for 3D Walks Brief Description: walk with your friends or walk with expert narrators ------------------------------------------------------------------------- Follow the sheep http://janastu.org/technoscience/index.php/JSoC#Follow_the_Sheep ----------------------- ___________ #Task F0313a Cartography tools for shepherd tracks Brief description: Shepherd details like tracks, photographs, audio, video and documents detailing socio-economic data are collected into a repository: http://mitan.in/followsheep/socionity/ We parse spreadsheets from the repository and extract the Lat-Long information. We also use various tools like qgis to extract shapefiles, tilemill to beautify the map, and map warper to overlay drawings, images on the map to generate a narrative. The task is to create tools that help us going from the spreadsheet to the generated narrative. This would include not only the presentation of the narrative, but also loosely-coupling the tools used in the toolchain, possibly using SWeeTs. What we expect to see in your proposal: Familiarity with cartography/mapping using various tools; and also ability to conceptualize a toolchain. Expected results: To deliver a browser presentation of the narrative using the data in the repository using spreadsheet as the guideline. Knowledge prerequisite: Javascript, HTML5, CSS3, TileMill, Node.JS, MapWarper etc. Mentor: Socionity Team ------------------------------------------------------------------------- Pantoto http://janastu.org/technoscience/index.php/JSoC#Pantoto ----------- _________ #Task P13a Frontend themes Pantoto - Mouchak Brief description: Mouchak provides a simple way to develop web app content and some javascript apis. Some of the media types are videos, images, maps, charts, text and rich text that need to be styled to put together a complete web presentation. To develop a set themes and the necessary style hooks using the community radio site as a reference. What we expect to see in your proposal: Experience with web development, browser Expected results: Deliver one complete site presentation using a theme with documentation on how you have tested your components Knowledge prerequisite: Javascript, HTML5, CSS3 and have some understanding of frameworks such as jquery and boilerplate Mentor: Pantoto team ------------------------------------------------------------------------- ------------------------------------------------------------------------- -------------------------------------------------------------------------