Ideal components

From ZooidWiki

Contents 1 essential 1.1 Front end 1.2 Data 1.3 Execution 1.4 Construction 2 nice to have 2.1 Other info 3 Ontologies

[edit] essential

[edit] Front end

• designer control on front end
• fluid (ajaxy) without going overboard (URLs to every location)
• accessible
• RESTy URLs
• in place editing
• embedded wiki parser or other way of creating composite documents

[edit] Data

• rdfa
• micro licenses
  • ccREL
• polymorphic data
• REST (JSON), SPARQL queryable
• strict validation
  • JSR 303

[edit] Execution

• runs nearly anywhere
• scalable
• fine grained security
• sso

[edit] Construction

• uses standard libraries
• fluid development (no restarting) including site structure and objects
• easy to populate with data and export

[edit] nice to have

• polyglot - jvm, ruby, python, php, etc

[edit] Other info

reciprocal content

http://openlayers.org/ - free maps (using openstreetmaps)

http://semanticweb.org/wiki/SemFS - webdav access to smw tagged content (java)

microformats - http://microformats.org/

http://en.wikipedia.org/wiki/Mulgara_(software) - scalable rdf store

mulgara - scalable rdf (java) - http://docs.mulgara.org/overview/links.html links to lots of orientation

[edit] Ontologies

http://ontologyonline.org/ - meta directory

http://www.schemaweb.info/default.aspx - RDF schemas

http://www5.umweltbundesamt.at/ALTERNet/index.php?title=Ont:ALTER-Net_Ontology - social field ontologies

http://typewriter.freebaseapps.com/ cc typed information

Ideal systems

Scala Lift ?