>>> [Jochem Berends wrote:] >>> As said, I am very excited for this project and I am eager to help out >>> where neccessary! >> >> I'm happy that a KBE expert join this list. My field is rather product >> data management and interoperability. I especially focuses on PDM/ERP >> interoperability (as a PhD candidate too) and the STEP standard as a way > to overcome the related issues. Our approaches are quite complentary. >> No doubt this mix will lead to rich exchanges and realizations. > >I also welcome a KBE expert to the list! I am also very interested >in this area. I have an application I am working on to create Python >class definitions from OWL ontologies. I also have code to create >the Python objects as Storm objects (<https://storm.canonical.com/>), >and I have some sql-generation code for the back end (a separable >issue, of course, but I include it in my app). All of this is in >a partially broken state at the moment, because I am doing some >refactoring and adding more unit tests, but I will be happy to share >any of this as soon as it is working well enough to demonstrate >the concept. My goal (which probably fits well with KBE) is to >have engineering application objects defined by ontologies, so that >they can be reasoned about using first-order logic engines, rules, etc.
I completely agree with you. I cannot imagine a modern knowledge based app that would not *intensively* be based on an ontology description. Do you know about Python-Seth to parse OWL files (http://seth-scripting.sourceforge.net/)? It seems to be the same thing you're working on. Such a knowledge framework could be achieved with pythonOCC; your work could also, I think, easily be merged. One solution could be to build a kind of 'super-object' that would embeds a geometrical/topological description (pythonOCC) and a pointer to the related ontology (for instance a UID or an URI to an ontology SOA based server). This last point is closely related to my research work and the specialization of the STEP AP239 (or ISO 15926) generic data model. Once this global architecture is defined, the difficult work begins: how to model the knowledge in terms of an ontology? At his point, we fall in the well-known separation dealing with the technical and semantic issues related to a software implementation. While the first one is generally easy to solve, the KBE specialists are welcome to comment the second one! > >Cheers, >Steve Cheers, Thomas _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
