From the webpage:
TM2O is a generic tool to provide information stored within a topic map as an OData service. This OData services uses majortom as local topic maps backend or a remote majortom server. The implementation bases on odata4j and heavily uses the TMQL engine TMQL4J.
We have prepared a getting started guideline for you. Here you will learn to set-up the TM2O service, and to create and use OData service out of your topic maps.
Stop me if I get off into the ditch but as interesting as this sounds, isn’t that going in the wrong direction?
Going in the opposite direction, an OData -> TM tool that views content served as OData as topics, associations, etc., would be more interesting. You can hang more information off subjects and relationships in a topic map, which is a form of value-add.
If nothing else, just think about the amount of content available as topic maps versus available as OData.
Do I need to say more?