Ideal components: Difference between revisions
Jump to navigation
Jump to search
| Line 31: | Line 31: | ||
* uses standard libraries | * uses standard libraries | ||
* fluid development (no restarting) | * fluid development (no restarting) | ||
* easy to populate with data and export | |||
== nice to have == | == nice to have == | ||
Revision as of 16:01, 18 September 2009
essential
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
Data
- rdfa
- micro licenses
- ccREL
- polymorphic data
- REST (JSON), SPARQL queryable
- strict validation
- JSR 303
Execution
- runs nearly anywhere
- scalable
- fine grained security
- sso
Construction
- uses standard libraries
- fluid development (no restarting)
- easy to populate with data and export
nice to have
- polyglot - jvm, ruby, python, php, etc
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
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