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

Add Restriction Property as ConceptType choice to OWL Restriction Dictionary Table #24

Closed MikeHypercube closed 11 years ago

MikeHypercube commented 11 years ago

If it's possible, please change the content of the "conceptType" field in the Restrictions table, to reflect the following:

<> reported as "Property Restriction" <> reported as "Type Restriction"

If Logical union uses the same table then:

<> reported as "Logical Union"

(if UnionClass is reported in the Classes table instead, which is fine, then the above change should be implemented in that table, for union classes).

lonniev commented 11 years ago

Under development. There are actually 3 requests here. OWL Restriction will come first.

lonniev commented 11 years ago

owlRestriction maps to "Restriction". How do I disambiguate between Property and Type Restriction?

I sense that I'll have to do something contextual to choose between the two.

lonniev commented 11 years ago

ConceptType for owlRestriction is checked in.

image

lonniev commented 11 years ago

Refactoring the issue into 3 separate ones. Aggregate requirements take a long time to close out and are harder to track.

MikeHypercube commented 11 years ago

There is only one property restriction, and it has the stereotype of <> which is how you can tell them apart.

It is in BusinessFacingTypes.

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: Wednesday, August 28, 2013 6:34 PM To: lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties Cc: Mike Bennett Subject: Re: [com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties] Report concept types for restrictions and unions on the Concept Type column in tables (#24)

owlRestriction maps to "Restriction". How do I disambiguate between Property and Type Restriction?

I sense that I'll have to do something contextual to choose between the two.

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

MikeHypercube commented 11 years ago

I know, but I am raising issues at the level of the business functionality I am requesting, not at the level of the architecture of the solution, since this would involve me understanding the details of your design, and would lead to mistakes on my part.

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: Wednesday, August 28, 2013 6:45 PM To: lonniev/com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties Cc: Mike Bennett Subject: Re: [com.nomagic.cameo.partners.omg.fibo.plugins.derivedproperties] Add Restriction Property to OWL Restriction Dictionary Table (#24)

Refactoring the issue into 3 separate ones. Aggregate requirements take a long time to close out and are harder to track.

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