| | |
| has_part |
adds value to existing content |
| has_part |
could be used as a directory service inside existing intranet/extranet |
| has_part |
could be used to store research or experimental results, see Lab_book |
| has_part |
could provide a structure to store Xml for programmatic access |
| has_part |
deskilling of website maintenance, simple data entry as triples |
| has_part |
directory structure allows cross referencing between Ontologies |
| has_part |
fast web page generation, easy maintenance, no html coding |
| has_part |
integrates well with existing content |
| has_part |
more efficient management of large websites/knowledge bases, provides metadata, potential usage metrics |
| has_part |
potential to store multimedia, images, movies, PDF, Powerpoint, Word |
| has_part |
separation of presentation and content, template for site style |
| has_part |
simple underlying database structure, stores content |
| has_part |
software used is industry standard, mySql, Java, Html |
| is_part_of |
Ontology. |
| Use |
Departmental_website. |
| Use |
Find available processes |
| Use |
Find available work flows |
| Use |
Find data resources |
| Use |
Find styles of representation |
| Use |
Find transformation tools |
| Use |
Lab_book. |
| Use |
Lexicon of terms |
| Uses |
http://www.coolheads.com/egov/opensource/topicmap/s167/img8.html#N1 |