WikiReaders: Difference between revisions
Line 35: | Line 35: | ||
'''Agenda''' |
'''Agenda''' |
||
* introductions and updates: |
|||
** wikipedia 0.7 status/pages/algorithms/team |
|||
** [[wikiBrowse]] status and algorithms, language support |
|||
* compiling a main page |
* compiling a main page |
||
* selecting images |
* selecting images |
Revision as of 19:06, 29 August 2008
As part of the OLPC philosophy of providing the tools to manipulate and change their environment, our preferred text reader will be something that supports collaborative annotation and editing of books -- something we refer to as a wikibook reader rather than a traditional ebook reader.
This reader and editor should support many features (see sections below) for reading and annotating and editing various wikislices, books of various formats, and for creating new wikireaders from raw collections of pages and media.
Participants
Interested participants who are working on related projects, be they offline readers, static content projects, wikislice generators, or del.icio.us style annotators:
- --Sj talk
- renaud gaudin
- ffm
- zvi bosh
- cjb
- emmanuel e
- othman laraki
- walkerma
- andrew cates
- tom haukap
- erik zachte
- chris fabian, mepemepe
- pascal martin
- zdenekBroz
- andy r
- daniel m
- mchua
- Jim Tittsler
Meetings
Friday August 29, 1900 UTC
An IRC meeting will be held on #kiwix on freenode, at 1500 EST / 1900 UTC, for those who can make it : to discuss making a main page for an English Wikipedia wikireader (based on the WP 0.7 selection).
Attending
Agenda
- introductions and updates:
- wikipedia 0.7 status/pages/algorithms/team
- wikiBrowse status and algorithms, language support
- compiling a main page
- selecting images
- accessing/downloading the current articlelist
- white and blacklists, if any, on top of the ~30,000 articles in the current selection
Features
Viewing
- A comfortable way to read and page through long documents
- The ability to display formatted text, including images and tables; see the crossmark specifications for details.
- Support for viewing comments and annotations made on works, in a way not too far removed from the source of the notation; this could be through footnotes, endnotes, margin notation, or well-linked separate discussion pages
- Searching and ways to find content by sectional headers or tags
- Support for extended character alphabets
Optional
- Support for basic filtering; perhaps filtering a page to show only summaries or only material in one language.
- Support for user-customizable skins, per instance or even per book.
- The ability for users to build a customized portal for themselves that links into their favorite works.
Annotation
- A mechamism to comment on entries and sections, and on other comments, that shows up in some way for other readers of a document who choose to see annotations.
- User profiles to attribute annotations.
- The ability to export and import annotations associated with a given document.
- A way to synchronize annotations between mostly-offline clusters or meshes and a global web of online users and other such offline clusters.
- Statistics about annotations and user contributions.
- A way to deep-link to sections of longer documents, and to refer specifically to sections, pages, and annotations of long texts.
- Support for a constellation of categories, labels, and cross-references.
Synchronization
- Annontations should aggregate up to local and global servers. Ideally there would be content-based IDs to make it possible to find related annotations even when parentage is lost
Editing
- Support for text, photos, and other media included in a textual work.
- A tool to create a snapshot of a set of pages and take them offline; or to send such a request upstream for machines that are never directly online.
- A way to package a set of pages into a package that can be synchronized between online and offline wikis, which preserves metadata about edits and automatically merges changes/updates where possible.
Synchronization
- Edits should aggregate up to local and global servers, at least for a single wiki backend.
- There should be some tracking of parentage and attribution and other metadata when local changes are saved up the tree; and some way to bundle many changes into atomic commits.
Optional
- Support for synchronization across multiple wiki backends
- Support for edits and updates via email
- Ways to group users and pages together by category, editors, or context, to improve on a global view of "recent changes"
Hosting
- A global host [or hosts] for a library of collected annotations.
- No special installation on client machines needed -- make a specialized client available, but have this information viewable for people connected to the Web through a standard browser (Firefox)
- Find methods and incentives for other collections of materials and creators to work together in a way that keeps all host sites in synch with one another's updates.
Synchronization, LOCSS
- Materials at every level but the global level should be archived up the tree.
- There should be multiple copies of each page, perhaps as mirrors of the global material.