Extracting a document from an ontology

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Extracting a document from an ontology

ocratato
This is, perhaps, not entirely on topic for the Protege list, but I
assume that some Protege users might be the best people to ask.

I am considering the possibilities of using ontologies to store the
architecture and design of large software systems. I am aware of a few
papers on this subject, but creating the ontologies is not the issue I
am concerned about. My concern is with presenting the knowledge in a
format that is familiar to those that would have to use it - such as
database designers, network engineers, project managers, etc.

I have tried using Google to look for any work in creating text
documents from an ontology, but the results are flooded with things that
are trying to populate an ontology from text - the reverse of what I am
after.

Does anyone have any pointers to anything that can be used to create
easily readable reports from ontologies?

Thanks in advance
Brenton

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: Extracting a document from an ontology

Rafael Gonçalves
Hi Brenton,

I suggest looking into the OntoVerbal tool [1], which has a plugin for Protege 4.x. Another possibility is the OWLDoc plugin (already available for Protege 5), which produces HTML pages from your ontology [2], but I’m not sure this fits in with your requirements.

Cheers,
Rafael

[1] http://ceur-ws.org/Vol-897/demo_5.pdf (there is more associated literature, but this short text should be enough for you to figure out if it’s useful for you)

On Jul 16, 2016, at 21:53, Brenton Ross <[hidden email]> wrote:

This is, perhaps, not entirely on topic for the Protege list, but I
assume that some Protege users might be the best people to ask.

I am considering the possibilities of using ontologies to store the
architecture and design of large software systems. I am aware of a few
papers on this subject, but creating the ontologies is not the issue I
am concerned about. My concern is with presenting the knowledge in a
format that is familiar to those that would have to use it - such as
database designers, network engineers, project managers, etc.

I have tried using Google to look for any work in creating text
documents from an ontology, but the results are flooded with things that
are trying to populate an ontology from text - the reverse of what I am
after.

Does anyone have any pointers to anything that can be used to create
easily readable reports from ontologies?

Thanks in advance
Brenton

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user


_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: Extracting a document from an ontology

ocratato
Rafael,

Thanks for those links. OntoVerbal looks like a small step in the
direction I want to go.

Cheers
Brenton

On Mon, 2016-07-18 at 10:41 -0700, Rafael Gonçalves wrote:

> Hi Brenton,
>
>
> I suggest looking into the OntoVerbal tool [1], which has a plugin for
> Protege 4.x. Another possibility is the OWLDoc plugin (already
> available for Protege 5), which produces HTML pages from your ontology
> [2], but I’m not sure this fits in with your requirements.
>
>
> Cheers,
> Rafael
>
>
> [1] http://ceur-ws.org/Vol-897/demo_5.pdf (there is more associated
> literature, but this short text should be enough for you to figure out
> if it’s useful for you)
> [2] http://protegewiki.stanford.edu/wiki/OWLDoc
>
> > On Jul 16, 2016, at 21:53, Brenton Ross <[hidden email]> wrote:
> >
> > This is, perhaps, not entirely on topic for the Protege list, but I
> > assume that some Protege users might be the best people to ask.
> >
> > I am considering the possibilities of using ontologies to store the
> > architecture and design of large software systems. I am aware of a
> > few
> > papers on this subject, but creating the ontologies is not the issue
> > I
> > am concerned about. My concern is with presenting the knowledge in a
> > format that is familiar to those that would have to use it - such as
> > database designers, network engineers, project managers, etc.
> >
> > I have tried using Google to look for any work in creating text
> > documents from an ontology, but the results are flooded with things
> > that
> > are trying to populate an ontology from text - the reverse of what I
> > am
> > after.
> >
> > Does anyone have any pointers to anything that can be used to create
> > easily readable reports from ontologies?
> >
> > Thanks in advance
> > Brenton
> >
> > _______________________________________________
> > protege-user mailing list
> > [hidden email]
> > https://mailman.stanford.edu/mailman/listinfo/protege-user
> >
>
>
> _______________________________________________
> protege-user mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-user


_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: Extracting a document from an ontology

carter01
In reply to this post by ocratato
Brenton,

I have had the same problem for several years. The problem is further complicated by the language ontologists use vs what software engineers use as well.

While not a complete solution, I have found two tools that can assist, robustly and a one that is ok.

DISCLAIMER: I am not financially affiliated with any tool described here.

The most robust for documentation is Enterprise Architect. Problem, if you are creating ontologies in OWL you will have to modify to fit OMGs ODM format. That can be a challenge and add time to ontology development. The capabilities are deep especially the tight integration with UML. Unfortunately, their documentation on implementation is weak. The support responsiveness is as weak as their documentation. So if you are creative and innovative, it is an awesome tool.

The second best is TopBraid Composer. Though optimized for ontologists, its documentation is outstanding as well. It has the ability to port to an online format that is actually better than EA. The system can also produce excellent SKOS taxonomies that are fully evolved. The problem is that you have to purchase an additional module to build sustainable models for all to access.  Its about $8k but if you have the budget it is well worth it.

PoolParty is not bad as well but there documentation capability is a little wonky but that is my opinion.

Does this help?



Mark A. Carter
Primary: (816) 686-2221
Web Site: MCTest

On Sat, Jul 16, 2016 at 11:53 PM, Brenton Ross <[hidden email]> wrote:
This is, perhaps, not entirely on topic for the Protege list, but I
assume that some Protege users might be the best people to ask.

I am considering the possibilities of using ontologies to store the
architecture and design of large software systems. I am aware of a few
papers on this subject, but creating the ontologies is not the issue I
am concerned about. My concern is with presenting the knowledge in a
format that is familiar to those that would have to use it - such as
database designers, network engineers, project managers, etc.

I have tried using Google to look for any work in creating text
documents from an ontology, but the results are flooded with things that
are trying to populate an ontology from text - the reverse of what I am
after.

Does anyone have any pointers to anything that can be used to create
easily readable reports from ontologies?

Thanks in advance
Brenton

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user


_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: Extracting a document from an ontology

Ghislain ATEMEZING
Hi Brenton,

You might also look at the following tools:
 - OWLGRED: http://owlgred.lumii.lv/ 

HTH
Good luck!
Ghislain


El mar., 19 jul. 2016 a las 15:47, Mark Carter (<[hidden email]>) escribió:
Brenton,

I have had the same problem for several years. The problem is further complicated by the language ontologists use vs what software engineers use as well.

While not a complete solution, I have found two tools that can assist, robustly and a one that is ok.

DISCLAIMER: I am not financially affiliated with any tool described here.

The most robust for documentation is Enterprise Architect. Problem, if you are creating ontologies in OWL you will have to modify to fit OMGs ODM format. That can be a challenge and add time to ontology development. The capabilities are deep especially the tight integration with UML. Unfortunately, their documentation on implementation is weak. The support responsiveness is as weak as their documentation. So if you are creative and innovative, it is an awesome tool.

The second best is TopBraid Composer. Though optimized for ontologists, its documentation is outstanding as well. It has the ability to port to an online format that is actually better than EA. The system can also produce excellent SKOS taxonomies that are fully evolved. The problem is that you have to purchase an additional module to build sustainable models for all to access.  Its about $8k but if you have the budget it is well worth it.

PoolParty is not bad as well but there documentation capability is a little wonky but that is my opinion.

Does this help?



Mark A. Carter
Primary: (816) 686-2221
Web Site: MCTest

On Sat, Jul 16, 2016 at 11:53 PM, Brenton Ross <[hidden email]> wrote:
This is, perhaps, not entirely on topic for the Protege list, but I
assume that some Protege users might be the best people to ask.

I am considering the possibilities of using ontologies to store the
architecture and design of large software systems. I am aware of a few
papers on this subject, but creating the ontologies is not the issue I
am concerned about. My concern is with presenting the knowledge in a
format that is familiar to those that would have to use it - such as
database designers, network engineers, project managers, etc.

I have tried using Google to look for any work in creating text
documents from an ontology, but the results are flooded with things that
are trying to populate an ontology from text - the reverse of what I am
after.

Does anyone have any pointers to anything that can be used to create
easily readable reports from ontologies?

Thanks in advance
Brenton

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
--
-------
"Love all, trust a few, do wrong to none" (W. Shakespeare)
Web: http://atemezing.org

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: Extracting a document from an ontology

ocratato
In reply to this post by carter01
Mark,

Thanks for the references. They seem a bit over specialised for what I
have in mind, and generally not something I can build into a
re-distributable system.

I will next have a look at it from the Natural Language Generation point
of view.

Cheers
Brenton

On Tue, 2016-07-19 at 08:47 -0500, Mark Carter wrote:

> Brenton,
>
>
> I have had the same problem for several years. The problem is further
> complicated by the language ontologists use vs what software engineers
> use as well.
>
>
> While not a complete solution, I have found two tools that can assist,
> robustly and a one that is ok.
>
>
> DISCLAIMER: I am not financially affiliated with any tool described
> here.
>
>
> The most robust for documentation is Enterprise Architect. Problem, if
> you are creating ontologies in OWL you will have to modify to fit OMGs
> ODM format. That can be a challenge and add time to ontology
> development. The capabilities are deep especially the tight
> integration with UML. Unfortunately, their documentation on
> implementation is weak. The support responsiveness is as weak as their
> documentation. So if you are creative and innovative, it is an awesome
> tool.
>
>
> The second best is TopBraid Composer. Though optimized for
> ontologists, its documentation is outstanding as well. It has the
> ability to port to an online format that is actually better than EA.
> The system can also produce excellent SKOS taxonomies that are fully
> evolved. The problem is that you have to purchase an additional module
> to build sustainable models for all to access.  Its about $8k but if
> you have the budget it is well worth it.
>
>
> PoolParty is not bad as well but there documentation capability is a
> little wonky but that is my opinion.
>
>
> Does this help?
>
>
>
>
>
> Mark A. Carter
> Primary: (816) 686-2221
> Email: [hidden email]
> Web Site: MCTest
>
> On Sat, Jul 16, 2016 at 11:53 PM, Brenton Ross <[hidden email]>
> wrote:
>         This is, perhaps, not entirely on topic for the Protege list,
>         but I
>         assume that some Protege users might be the best people to
>         ask.
>        
>         I am considering the possibilities of using ontologies to
>         store the
>         architecture and design of large software systems. I am aware
>         of a few
>         papers on this subject, but creating the ontologies is not the
>         issue I
>         am concerned about. My concern is with presenting the
>         knowledge in a
>         format that is familiar to those that would have to use it -
>         such as
>         database designers, network engineers, project managers, etc.
>        
>         I have tried using Google to look for any work in creating
>         text
>         documents from an ontology, but the results are flooded with
>         things that
>         are trying to populate an ontology from text - the reverse of
>         what I am
>         after.
>        
>         Does anyone have any pointers to anything that can be used to
>         create
>         easily readable reports from ontologies?
>        
>         Thanks in advance
>         Brenton
>        
>         _______________________________________________
>         protege-user mailing list
>         [hidden email]
>         https://mailman.stanford.edu/mailman/listinfo/protege-user
>
>
> _______________________________________________
> protege-user mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-user


_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: Extracting a document from an ontology

ocratato
In reply to this post by Ghislain ATEMEZING
Ghislain,

Thanks for the links.
However I am looking for something that is a lot more textual in its
output.

Cheers
Brenton

On Tue, 2016-07-19 at 13:57 +0000, Ghislain ATEMEZING wrote:

> Hi Brenton,
>
>
> You might also look at the following tools:
>  - LODE: http://www.essepuntato.it/lode 
>  - Parrot: http://ontorule-project.eu/parrot/parrot 
>  - OWLGRED: http://owlgred.lumii.lv/ 
>
>
> HTH
> Good luck!
> Ghislain
>
>

>        
>         On Sat, Jul 16, 2016 at 11:53 PM, Brenton Ross
>         <[hidden email]> wrote:
>                 This is, perhaps, not entirely on topic for the
>                 Protege list, but I
>                 assume that some Protege users might be the best
>                 people to ask.
>                
>                 I am considering the possibilities of using ontologies
>                 to store the
>                 architecture and design of large software systems. I
>                 am aware of a few
>                 papers on this subject, but creating the ontologies is
>                 not the issue I
>                 am concerned about. My concern is with presenting the
>                 knowledge in a
>                 format that is familiar to those that would have to
>                 use it - such as
>                 database designers, network engineers, project
>                 managers, etc.
>                
>                 I have tried using Google to look for any work in
>                 creating text
>                 documents from an ontology, but the results are
>                 flooded with things that
>                 are trying to populate an ontology from text - the
>                 reverse of what I am
>                 after.
>                
>                 Does anyone have any pointers to anything that can be
>                 used to create
>                 easily readable reports from ontologies?
>                
>                 Thanks in advance
>                 Brenton
>                
>                 _______________________________________________
>                 protege-user mailing list
>                 [hidden email]
>                 https://mailman.stanford.edu/mailman/listinfo/protege-user
>        
>        
>         _______________________________________________
>         protege-user mailing list
>         [hidden email]
>         https://mailman.stanford.edu/mailman/listinfo/protege-user
> --
>
> -------
> "Love all, trust a few, do wrong to none" (W. Shakespeare)
> Web: http://atemezing.org
> _______________________________________________
> protege-user mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-user


_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: Extracting a document from an ontology

Csongor Nyulas
Administrator
In reply to this post by ocratato
I would also take a look at ACE View plugin (you can find it on this
page: http://attempto.ifi.uzh.ch/site/resources/). It is a quite
powerful ontology "verbalizer", but it may or may not be what you need.

Csongor


On 07/19/2016 07:56 AM, Brenton Ross wrote:

> Mark,
>
> Thanks for the references. They seem a bit over specialised for what I
> have in mind, and generally not something I can build into a
> re-distributable system.
>
> I will next have a look at it from the Natural Language Generation point
> of view.
>
> Cheers
> Brenton
>
> On Tue, 2016-07-19 at 08:47 -0500, Mark Carter wrote:
>> Brenton,
>>
>>
>> I have had the same problem for several years. The problem is further
>> complicated by the language ontologists use vs what software engineers
>> use as well.
>>
>>
>> While not a complete solution, I have found two tools that can assist,
>> robustly and a one that is ok.
>>
>>
>> DISCLAIMER: I am not financially affiliated with any tool described
>> here.
>>
>>
>> The most robust for documentation is Enterprise Architect. Problem, if
>> you are creating ontologies in OWL you will have to modify to fit OMGs
>> ODM format. That can be a challenge and add time to ontology
>> development. The capabilities are deep especially the tight
>> integration with UML. Unfortunately, their documentation on
>> implementation is weak. The support responsiveness is as weak as their
>> documentation. So if you are creative and innovative, it is an awesome
>> tool.
>>
>>
>> The second best is TopBraid Composer. Though optimized for
>> ontologists, its documentation is outstanding as well. It has the
>> ability to port to an online format that is actually better than EA.
>> The system can also produce excellent SKOS taxonomies that are fully
>> evolved. The problem is that you have to purchase an additional module
>> to build sustainable models for all to access.  Its about $8k but if
>> you have the budget it is well worth it.
>>
>>
>> PoolParty is not bad as well but there documentation capability is a
>> little wonky but that is my opinion.
>>
>>
>> Does this help?
>>
>>
>>
>>
>>
>> Mark A. Carter
>> Primary: (816) 686-2221
>> Email: [hidden email]
>> Web Site: MCTest
>>
>> On Sat, Jul 16, 2016 at 11:53 PM, Brenton Ross <[hidden email]>
>> wrote:
>>          This is, perhaps, not entirely on topic for the Protege list,
>>          but I
>>          assume that some Protege users might be the best people to
>>          ask.
>>          
>>          I am considering the possibilities of using ontologies to
>>          store the
>>          architecture and design of large software systems. I am aware
>>          of a few
>>          papers on this subject, but creating the ontologies is not the
>>          issue I
>>          am concerned about. My concern is with presenting the
>>          knowledge in a
>>          format that is familiar to those that would have to use it -
>>          such as
>>          database designers, network engineers, project managers, etc.
>>          
>>          I have tried using Google to look for any work in creating
>>          text
>>          documents from an ontology, but the results are flooded with
>>          things that
>>          are trying to populate an ontology from text - the reverse of
>>          what I am
>>          after.
>>          
>>          Does anyone have any pointers to anything that can be used to
>>          create
>>          easily readable reports from ontologies?
>>          
>>          Thanks in advance
>>          Brenton
>>          
>>          _______________________________________________
>>          protege-user mailing list
>>          [hidden email]
>>          https://mailman.stanford.edu/mailman/listinfo/protege-user
>>
>>
>> _______________________________________________
>> protege-user mailing list
>> [hidden email]
>> https://mailman.stanford.edu/mailman/listinfo/protege-user
>
> _______________________________________________
> protege-user mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-user


_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: Extracting a document from an ontology

ocratato
Csongor
Thanks. I will add it to my list of things to investigate some more.

Cheers
Brenton

On Tue, 2016-07-19 at 11:15 -0700, Csongor Nyulas wrote:

> I would also take a look at ACE View plugin (you can find it on this
> page: http://attempto.ifi.uzh.ch/site/resources/). It is a quite
> powerful ontology "verbalizer", but it may or may not be what you need.
>
> Csongor
>
>
> On 07/19/2016 07:56 AM, Brenton Ross wrote:
> > Mark,
> >
> > Thanks for the references. They seem a bit over specialised for what I
> > have in mind, and generally not something I can build into a
> > re-distributable system.
> >
> > I will next have a look at it from the Natural Language Generation point
> > of view.
> >
> > Cheers
> > Brenton
> >
> > On Tue, 2016-07-19 at 08:47 -0500, Mark Carter wrote:
> >> Brenton,
> >>
> >>
> >> I have had the same problem for several years. The problem is further
> >> complicated by the language ontologists use vs what software engineers
> >> use as well.
> >>
> >>
> >> While not a complete solution, I have found two tools that can assist,
> >> robustly and a one that is ok.
> >>
> >>
> >> DISCLAIMER: I am not financially affiliated with any tool described
> >> here.
> >>
> >>
> >> The most robust for documentation is Enterprise Architect. Problem, if
> >> you are creating ontologies in OWL you will have to modify to fit OMGs
> >> ODM format. That can be a challenge and add time to ontology
> >> development. The capabilities are deep especially the tight
> >> integration with UML. Unfortunately, their documentation on
> >> implementation is weak. The support responsiveness is as weak as their
> >> documentation. So if you are creative and innovative, it is an awesome
> >> tool.
> >>
> >>
> >> The second best is TopBraid Composer. Though optimized for
> >> ontologists, its documentation is outstanding as well. It has the
> >> ability to port to an online format that is actually better than EA.
> >> The system can also produce excellent SKOS taxonomies that are fully
> >> evolved. The problem is that you have to purchase an additional module
> >> to build sustainable models for all to access.  Its about $8k but if
> >> you have the budget it is well worth it.
> >>
> >>
> >> PoolParty is not bad as well but there documentation capability is a
> >> little wonky but that is my opinion.
> >>
> >>
> >> Does this help?
> >>
> >>
> >>
> >>
> >>
> >> Mark A. Carter
> >> Primary: (816) 686-2221
> >> Email: [hidden email]
> >> Web Site: MCTest
> >>
> >> On Sat, Jul 16, 2016 at 11:53 PM, Brenton Ross <[hidden email]>
> >> wrote:
> >>          This is, perhaps, not entirely on topic for the Protege list,
> >>          but I
> >>          assume that some Protege users might be the best people to
> >>          ask.
> >>          
> >>          I am considering the possibilities of using ontologies to
> >>          store the
> >>          architecture and design of large software systems. I am aware
> >>          of a few
> >>          papers on this subject, but creating the ontologies is not the
> >>          issue I
> >>          am concerned about. My concern is with presenting the
> >>          knowledge in a
> >>          format that is familiar to those that would have to use it -
> >>          such as
> >>          database designers, network engineers, project managers, etc.
> >>          
> >>          I have tried using Google to look for any work in creating
> >>          text
> >>          documents from an ontology, but the results are flooded with
> >>          things that
> >>          are trying to populate an ontology from text - the reverse of
> >>          what I am
> >>          after.
> >>          
> >>          Does anyone have any pointers to anything that can be used to
> >>          create
> >>          easily readable reports from ontologies?
> >>          
> >>          Thanks in advance
> >>          Brenton
> >>          
> >>          _______________________________________________
> >>          protege-user mailing list
> >>          [hidden email]
> >>          https://mailman.stanford.edu/mailman/listinfo/protege-user
> >>
> >>
> >> _______________________________________________
> >> protege-user mailing list
> >> [hidden email]
> >> https://mailman.stanford.edu/mailman/listinfo/protege-user
> >
> > _______________________________________________
> > protege-user mailing list
> > [hidden email]
> > https://mailman.stanford.edu/mailman/listinfo/protege-user
>
>
> _______________________________________________
> protege-user mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-user


_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user