Avoiding premature standardisation: balancing innovation and conformity

Abstract

Overview <ul class="ak-ul" data-indent-level="1"><li><p data-renderer-start-pos="411">Currently work in a niche area:</p><ul class="ak-ul" data-indent-level="2"><li><p data-renderer-start-pos="446">ontologies for operational system semantic interoperability – integration</p></li><li><p data-renderer-start-pos="523">think integrating enterprise SAP and Maximo operationally<br>have been working here for a while (since late 1980s)</p></li><li><p data-renderer-start-pos="638">not many (any?) other people working here</p></li></ul></li><li><p data-renderer-start-pos="685">Believe that:</p><ul class="ak-ul" data-indent-level="2"><li><p data-renderer-start-pos="702">there are opportunities for architectural (radical and disruptive) innovation in this and other ontology area</p></li><li><p data-renderer-start-pos="815">at this stage, the approach in my area needs to be agile</p></li><li><p data-renderer-start-pos="875">that premature standardisation could stifle the innovation</p></li></ul></li><li><p data-renderer-start-pos="939">Want to suggest that:</p><ul class="ak-ul" data-indent-level="2"><li><p data-renderer-start-pos="964">there is a need to balance the conformity (of standards) with the agility needed to produce innovation</p></li><li><p data-renderer-start-pos="1070">the balancing involves recognising when to standardise,</p></li><li><p data-renderer-start-pos="1129">so, recognising when there is premature standardisation</p></li><li><p data-renderer-start-pos="1188">it is not yet time to standardise in my area</p></li></ul></li></ul>

Downloads

• Presentation Fileapplication/vnd.openxmlformats-officedocument.presentationml.slideshow