Please include a summary of the discussion, any recommendations or requests that the group had, and any resources the group noted regarding the topic.
Projects people are involved in:
Foodista - Colin
TikiWiki - Marc and ??Cunningham
Wagn - John A, Lewis and Ethan
AboutUs - Ray
Swank - John W
TikiWiki, Swank and Wagn are structured wikis.
Others mentioned include: TWiki, JotSpot, XWiki, DekiWiki
CMSes mentioned: Plone, Xarya
Structured wikis and CMSes are approaching the same space, but from somewhat different perspectives, e.g. structured wikis tend to have a lot more emphasis on people being able to affect the structure of the system through using the system itself.
What about exporting/importing in standard formats?
Semantic web will never cover everything.
And, using standard formats in some well-defined areas can be helpful.
What if someone builds an event system in their strctured wiki, and wants to be able to easily publish their event to upcoming.org, etc.? Just use the hcal microformat and Firefox plug-in Operator - https://addons.mozilla.org/en-US/firefox/addon/4106
John W - Swank
wanted to grow web applications organically
wiki = living document
structuredness = database
what we don't want - fixed structure
should be possible to change schema, field names, data types, etc.
there's been lots of research on semistructured data
around 2000, a lot of data has been stored in XML
Foodista stores in JSON
Philippe suggests CouchDB - JSON is it's native format
Swank stores in XML.
indexed by Lucene
Foodista uses Solr - puts a web interface on Lucene
limitations - hard to search on what doesn't match something; do joins
but simple and easy
Swank does blogs, comments, users & groups, sessions (not indexed), celndar, todo list, class registration system, payment ledger
attachments not in the system yet, would like to have that
Every page has a structure - default is unstructured wiki text field; have op
A page is an object
objects are not instances of classes
Each page has a parent object which is its template page
A value is (also a method)
Templates specify fields
Each field is its own page which specifies view and edit modes, and validation
Actions - viewing pages, saving, history, etc. are actions - methods on page objects
some Actions have aspects that are editable in a page related to that Action
Site wrappers - control look/function for whole site; can also be applied to sections of site
Remember to link to this session from the Session notes.