search

lonniev / com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties

A plugin for Cameo to provide Derived Property logic
0 stars 1 forks source link

There is not a table from which restrictions may be reported on #9

Open MikeHypercube opened 11 years ago

MikeHypercube commented 11 years ago

As well as classes and properties, we need a table report (with the same column structure) for restrictions. The detailed requirements for this are in the v4 spreadsheet (and may require some interpretation / exploration when the time comes).

lonniev commented 11 years ago

"Exploration" with suitable sample inputs would be enlightening. I gather that it is the "Reusable Properties Logic" that is supposed to suggest what is sought.

I will look at and see if it suggests solutions.

MikeHypercube commented 11 years ago

That’s the thing, yes.

The concept of property re-use was the nearest thing I could think of to saying what an OWL restriction is in plain English.

Though to be honest since even I struggle with them, they are not a very business friendly thing to begin with.

If possible, we should try and add these as Errata items in the document we bring with us to New Brunswick.

Cheers,

Mike (PS where do email replies to issue comments go?)

Mike Bennett Head of Semantics and Standards EDM Council Tel: +44 20 7917 9522 Cell: +44 7721 420 730 www.edmcouncil.orghttp://www.edmcouncil.org Semantics Repository: www.hypercube.co.uk/edmcouncilhttp://www.hypercube.co.uk/edmcouncil

From: Lonnie VanZandt [mailto:notifications@github.com] Sent: Monday, August 26, 2013 6:23 PM To: lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties Cc: Mike Bennett Subject: Re: [com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties] There is not a table from which restrictions may be reported on (#9)

"Exploration" with suitable sample inputs would be enlightening. I gather that it is the "Reusable Properties Logic" that is supposed to suggest what is sought.

I will look at owl:Restriction and see if it suggests solutions.

— Reply to this email directly or view it on GitHubhttps://github.com/lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties/issues/9#issuecomment-23299975.

lonniev commented 11 years ago

Because owlRestriction is an extension of Class like owlClass is an extension of Class, I may be able to get you a "OWL Restriction Dictionary" in a matter of hours. (Sadly, copy-n-paste doesn't work too well for custom tables. MD wants to be involved in the steps of the creation of the table and so deletes a lot of content when I switch the element type selection to a new target. Otherwise, it would be a 5-minute exercise.)

lonniev commented 11 years ago

Email replies use that ugly URL email address and apparently stuff the email remark into the body of an issue's comments. I think.

MikeHypercube commented 11 years ago

It does. I thought it didn’t but that was a test and it does.

M

Mike Bennett Head of Semantics and Standards EDM Council Tel: +44 20 7917 9522 Cell: +44 7721 420 730 www.edmcouncil.orghttp://www.edmcouncil.org Semantics Repository: www.hypercube.co.uk/edmcouncilhttp://www.hypercube.co.uk/edmcouncil

From: Lonnie VanZandt [mailto:notifications@github.com] Sent: Monday, August 26, 2013 6:32 PM To: lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties Cc: Mike Bennett Subject: Re: [com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties] There is not a table from which restrictions may be reported on (#9)

Email replies use that ugly URL email address and apparently stuff the email remark into the body of an issue's comments. I think.

— Reply to this email directly or view it on GitHubhttps://github.com/lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties/issues/9#issuecomment-23300519.

MikeHypercube commented 11 years ago

That is VERY good news.

I am almost tempted to “not spoil the ship for a ha’p’orth of tar” and get this in tomorrow about this time, and see if anyone screams at us. Theoretically RFCs are not subject to the 4 week deadline…

However, I think it will take a while to get all the logic we want on these. A first cut in the formal document would be a good starting point though.

Having the restrictions in will really be worth losing a day for.

Mike

Mike Bennett Head of Semantics and Standards EDM Council Tel: +44 20 7917 9522 Cell: +44 7721 420 730 www.edmcouncil.orghttp://www.edmcouncil.org Semantics Repository: www.hypercube.co.uk/edmcouncilhttp://www.hypercube.co.uk/edmcouncil

From: Lonnie VanZandt [mailto:notifications@github.com] Sent: Monday, August 26, 2013 6:31 PM To: lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties Cc: Mike Bennett Subject: Re: [com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties] There is not a table from which restrictions may be reported on (#9)

Because owlRestriction is an extension of Class like owlClass is an extension of Class, I may be able to get you a "OWL Restriction Dictionary" in a matter of hours. (Sadly, copy-n-paste doesn't work too well for custom tables. MD wants to be involved in the steps of the creation of the table and so deletes a lot of content when I switch the element type selection to a new target. Otherwise, it would be a 5-minute exercise.)

— Reply to this email directly or view it on GitHubhttps://github.com/lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties/issues/9#issuecomment-23300473.

lonniev commented 11 years ago

With commit ff60050e01fe6ecaff43fb7bf7fd76dee3cc61b8 the table for owl Restrictions is provided. But, for now, it is pretty raw. I haven't worked through the code to handle the restriction cases properly or innovatively.

MikeHypercube commented 11 years ago

That was quick! How would the change be installed – does the additional table simply appear next time you open an ontology which has that module loaded, or does one have to invoke it somehow?

That is, what are the time related implications to being able to use this right away, given how long each opening and closing of Cameo takes?

Cheers,

Mike

Mike Bennett Head of Semantics and Standards EDM Council Tel: +44 20 7917 9522 Cell: +44 7721 420 730 www.edmcouncil.orghttp://www.edmcouncil.org Semantics Repository: www.hypercube.co.uk/edmcouncilhttp://www.hypercube.co.uk/edmcouncil

From: Lonnie VanZandt [mailto:notifications@github.com] Sent: Monday, August 26, 2013 8:01 PM To: lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties Cc: Mike Bennett Subject: Re: [com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties] There is not a table from which restrictions may be reported on (#9)

With commit ff60050https://github.com/lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties/commit/ff60050e01fe6ecaff43fb7bf7fd76dee3cc61b8 the table for owl Restrictions is provided. But, for now, it is pretty raw. I haven't worked through the code to handle the restriction cases properly or innovatively.

— Reply to this email directly or view it on GitHubhttps://github.com/lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties/issues/9#issuecomment-23304461.

MikeHypercube commented 11 years ago

If Cameo is taking a long time to open, have you checked your mduml.properties file to assure that you have allocated adequate memory to the JVM? (By default, mduml.properties starves an MD session of memory.)

I run MD on a 24G 64-bit machine and allocate 9G to the MD session.

If you import the plugin zip, it will auto-update the FIBO Profile and you'll gain the table template the next time you open your project.

Lonnie VanZandt Chief Architect No Magic, Inc. Mailstop: 700 Central Expressway S, Suite 110, Allen, TX 75013 Office: 637 Witter Gulch Rd, Suite 425, Evergreen, CO 80439 Direct: 303-900-3048 Email: lvanzandt@nomagic.com Skype: lonnie.vanzandt

On 8/26/2013 6:02 PM, Mike Bennett wrote:

That was quick! How would the change be installed – does the additional table simply appear next time you open an ontology which has that module loaded, or does one have to invoke it somehow?

That is, what are the time related implications to being able to use this right away, given how long each opening and closing of Cameo takes?

Cheers,

Mike

Mike Bennett

Head of Semantics and Standards

EDM Council

Tel: +44 20 7917 9522

Cell: +44 7721 420 730

www.edmcouncil.org http://www.edmcouncil.org

Semantics Repository: www.hypercube.co.uk/edmcouncil http://www.hypercube.co.uk/edmcouncil

_From:_Lonnie VanZandt [mailto:notifications@github.com] Sent: Monday, August 26, 2013 8:01 PM To: lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties Cc: Mike Bennett Subject: Re: [com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties] There is not a table from which restrictions may be reported on (#9)

With commit ff60050 https://github.com/lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties/commit/ff60050e01fe6ecaff43fb7bf7fd76dee3cc61b8 the table for owl Restrictions is provided. But, for now, it is pretty raw. I haven't worked through the code to handle the restriction cases properly or innovatively.

— Reply to this email directly or view it on GitHub https://github.com/lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties/issues/9#issuecomment-23304461.

MikeHypercube commented 11 years ago

I must be doing something wrong. I’ve installed the plugin version 20130826-1715 (in place of 1454) but I still get blank domain entries for object properties.

Also I don’t see a third table in the place where the tables live. Nor can I select restrictions from either of the existing tables.

What am I doing wrong?

Cheers,

Mike

Mike Bennett Head of Semantics and Standards EDM Council Tel: +44 20 7917 9522 Cell: +44 7721 420 730 www.edmcouncil.orghttp://www.edmcouncil.org Semantics Repository: www.hypercube.co.uk/edmcouncilhttp://www.hypercube.co.uk/edmcouncil

From: Lonnie VanZandt [mailto:lvanzandt@nomagic.com] Sent: Monday, August 26, 2013 8:17 PM To: Mike Bennett Cc: lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties Subject: Re: [com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties] There is not a table from which restrictions may be reported on (#9)

If Cameo is taking a long time to open, have you checked your mduml.properties file to assure that you have allocated adequate memory to the JVM? (By default, mduml.properties starves an MD session of memory.)

I run MD on a 24G 64-bit machine and allocate 9G to the MD session.

If you import the plugin zip, it will auto-update the FIBO Profile and you'll gain the table template the next time you open your project.

Lonnie VanZandt

Chief Architect

No Magic, Inc.

Mailstop: 700 Central Expressway S, Suite 110, Allen, TX 75013

Office: 637 Witter Gulch Rd, Suite 425, Evergreen, CO 80439

Direct: 303-900-3048

Email: lvanzandt@nomagic.commailto:lvanzandt@nomagic.com Skype: lonnie.vanzandt On 8/26/2013 6:02 PM, Mike Bennett wrote: That was quick! How would the change be installed – does the additional table simply appear next time you open an ontology which has that module loaded, or does one have to invoke it somehow?

That is, what are the time related implications to being able to use this right away, given how long each opening and closing of Cameo takes?

Cheers,

Mike

Mike Bennett Head of Semantics and Standards EDM Council Tel: +44 20 7917 9522 Cell: +44 7721 420 730 www.edmcouncil.orghttp://www.edmcouncil.org Semantics Repository: www.hypercube.co.uk/edmcouncilhttp://www.hypercube.co.uk/edmcouncil

From: Lonnie VanZandt [mailto:notifications@github.com] Sent: Monday, August 26, 2013 8:01 PM To: lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties Cc: Mike Bennett Subject: Re: [com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties] There is not a table from which restrictions may be reported on (#9)

With commit ff60050https://github.com/lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties/commit/ff60050e01fe6ecaff43fb7bf7fd76dee3cc61b8 the table for owl Restrictions is provided. But, for now, it is pretty raw. I haven't worked through the code to handle the restriction cases properly or innovatively.

— Reply to this email directly or view it on GitHubhttps://github.com/lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties/issues/9#issuecomment-23304461.

lonniev commented 11 years ago

I suggest we begin to explore the flaws of this OWL Restriction Dictionary table. If you know of particularly good occurrences of OWL Restrictions, suggest those.

Because of the insight these table views offer, they can be very useful--when correct--for helping get the more inscrutable logic of the report script correct.