The TF pyramid is not necessarily cuneiform in reality, it can be more of an amoeba. It is drawn with a triangle here just because there are many more special concepts than general ones, and many more people working at the lower rungs than at the top. The divisions of the cone depict both the composite structure of the content and the division of work between experts of different things.
A TF term, an instance of TF class term:Term , is an association (ordered pair) of language independent concept with a natural language designation. (This accords with terminology standard DIN 2342-1 and de Saussure's definition of a linguistic sign.).
| Subset | gloss |
|---|---|
| TFS.owl | contains just enough to support day-to-day business with validated TF terms. |
| TFTop.owl | extends TFS.owl for general language vocabulary, in particular, |
| TFwn.owl | bridges Princeton Wordnet to TFTop.owl |
| TFSem.owl | extends TFS.owl for NL semantics, in particular, semantic role frames. |
| TFProp.owl | contains a taxonomy of TF properties for querying and conversion. |
| TFL10n.owl | and its language specific subsets TFL10n-??.owl localize TF vocabulary. |
| TFLang.owl | contain ISO language codes in TF format. |
| TFCtry.owl | contains ISO country codes in TF format. |
| TFDom.owl | contains the TF subject field classification for querying and browsing. |
| TFStrict.owl | contains integrity constraints for validating a TF term ontology. |
| DictionaryStrict.owl | separates terms from expressions. |
| LegacyStrict.owl | separates terms from concepts. |
Caching
- Cache query result sets and edits in TF repository databases
- Cache ontology documents in repository directories
- Cache entry html pages on a content management system
TF tool workflows
This slide shows how the different tools play together. Retry locates entries and documents in the TF cloud. Rewrite converts between formats and does refactoring of names. Pellet4TF is the query engine and reasoner. Edit4TF supports ontology editing. Index4TF handles uploading of entries and documents to TermFactory repositories. A clockwise roundtrip on the perimeter of the figure traces the revisioning cycle of an ontology/entry through TF.
An early mockup of TermFactory specific web front end interfaces is shown below.
The current notion is that TF provides plugins and services for third party platforms.
MediaWiki and Drupal are being used as testbeds.
Query form
With parameter form=true , The TF QueryForm servlet provides a standalone query form. Option lang=fi produces a Finnish version. The TF query form exemplifies the use of the TF QueryService in a web application.
){kind=link}
Editor
With parameter form=true , The TF EditForm serves a standalone editor. Option lang=fi produces a Finnish version.
){kind=link}
This figure shows the component types of a TermFactory system graph. Each type of component is exemplified with a concrete instance (one actually used in the reference implementation).
Molto Translation Tools
The overall design of the MOLTO WP3 Translation Tools prototype is shown here. The core is a client side MOLTO translation editor embeddable to a third party translation management platform like GlobalSight, supported by web service APIs that take care of document, grammar and term management, GF translation, and ontology services.
){kind=link}
