Built on best-of-breed technologies

TME 5 is scalable, extendable and plays well with other technologies

Here's a look at some of the technology powering TME 5:

RESTful Distribution

Representational State Transfer is a style of software architecture that is well-suited to distributed hypermedia systems such as the Web. Contrary to popular belief, it is not just another Web services protocol such as SOAP, nor is its scope of application limited to HTTP and the Web.

Derived from existing network-centric architecture styles and principles, REST was originally conceived to meet the constraints of the Web. Due to the importance it attaches to such issues as software reliability, efficiency, and scalability, REST is becoming increasingly popular in distributed software architectures in general.

• Client-server separation: Allows for separation of concerns (distribution of components), which improves UI portability and server scalability
• Stateless interaction: Improves visibility of interactions (requests are self-contained), reliability (requests are atomic in nature), scalability (resource state is not tied down to one particular server)
• Cacheable resources: Resources are potentially cacheable, thus improving network efficiency
• A uniform interface: Simplifies overall system architecture, improves visibility of interactions
• Layered components: Reduces overall system complexity (a layer cannot see beyond the one it interacts with), improves scalability (introduction of intermediates between layers), enables full load-balancing
• Optional code on demand: Simplifies client implementation and improves system extensibility, but reduces visibility of interactions

REST APIs

TME 5 provides an access to several semantic resources through various REST APIs.

• Interfaces: Enables varied operations on TME resources like: search, management and maintenance tasks. This allows users to search authority files, change configuration files, consult log files, and more.
• Easy Integration: Provides a layer of abstraction that speeds up the integration cycle of TME into new or existing applications and workflows.

Ready for the Semantic Web

Until recently, there were few standards for the description and the interlinking of metadata on the web. The World Wide Web Consortium, an organization devoted to developing web standards and guidelines, recently proposed a set of standards in order to solve this issue.

These standards are based on well-known formats such as RDF and OWL, and they are intended to describe, aggregate and link web data.

The development of those standards has been inspired by a vision : create links between data, in a manner analogous to what the HTTP protocol did for web pages 20 years ago.

This vision is called the Semantic Web (or Web 3.0) and was initially proposed by Tim-Berners Lee who is the president of the W3C and the inventor of the World Wide Web, he states :

Like the web of hypertext, the web of data is constructed with documents on the web. However, unlike the web of hypertext, where links are relationships anchors in hypertext documents written in HTML, for data they links between arbitrary things described by RDF. The URIs identify any kind of object or concept.
But for HTML or RDF, the same expectations apply to make the web grow :

1. Use URIs as names for things.
2. Use HTTP URIs so that people can look up those names.
3. When someone looks up a URI, provide useful information.
4. Include links to other URIs. so that they can discover more things.