A key factor for successfully applying OTTR templates in an industrial context, is the ability to share templates, both within an organization, and, of course, between organizations. Within an organization, you would want a single source (or a set of sources, each for a distinct topic) from which to retrieve template definitions whenever you need them in various applications. The same applies to cross-organizational template definitions; it is then even more important to have a single-source-of-truth for shared templates.

For various reasons, it is often impractical to adhere to the requirement that each template must be retrievable from the IRI that identifies it ('resolvable IRIs'). In order to still be able to serve templates from a single, authorative source, it is desirable to implement a Template Library service; a REST-ful web service from which template definitions can be retrieved, and docttr documentation for templates is served, regardless of the namespaces of the template IRIs. And even if a template is served from its identifier IRI, it is not clear which syntax to use when returning a template definition to a client, or even when to instead return the docttr html. As of now, there is no OTTR specification covering these topics. In my talk, I will argue for the need for such a specification, and outline some ideas for what it should contain.

The Norwegian Maritime Authority (NMA) maintain several coding systems in Excel sheets. These coding systems contain valuable information about classes and individuals in NMA's ontology. We use OTTR for graph enrichment through tabOTTR to enrich our graph with information found in the coding systems.

Ontology engineering with OTTR: benefits & challenges derived from practical experience

We report our experience gained in the development of the DiProMag Ontology using OTTR.

The DiProMag ontology models experiments with magnetocaloric alloys in the material science domain. Exposing domain experts to OTTR templates instead of RDF helps to simplify the communication and helps to clarify the responsibilities of the involved parties in the ontology development. In a bottom-up (data driven) ontology engineering approach, OTTR template signatures have turned out to be a good basis for communication as they allow the domain experts to take an active role in the ontology development. Furthermore, we show how we involve the OTTR Semantic MediaWiki extension to store template definitions and instantiations in a Wiki as a tool for project internal collaboration.

As a result, we outline the benefits and challenges we observed, explain the design decision we had to make, and propose a starting point for a new methodology that uses OTTR.

Grundfos is building a source table editing platform that will be tailored for OTTR templates. Information engineers should be able to log in and create/update data for a large product ontology.

Ontologies following a pattern-based design are likely to contain repetitive structures. Such structures may be used to bootstrap rewritings of ontologies with OTTR templates. In this talk, I will present first ideas about reverse-engineering ontologies for the purpose of encoding repetitive structures with OTTR templates. I will show how such rewritings can be (semi-)automated and how they can provide useful insights into an ontology's design.

Topic: Template libraries for modular ontologies. I'd like to raise this issue for discussion: how online template libraries that support specific ontologies should be built, made available, and maintained.