Ideal components

From zooid Wiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

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) including site structure and objects
  • 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

Ideal systems

Scala Lift ?

Retrieved from "https://wiki.zooid.org/index.php?title=Ideal_components&oldid=2380"