Bug 1099908

Summary: Add support for exclusive classifiers
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Anton Giertli <agiertli>
Component: DT GovernanceAssignee: Thomas Heute <theute>
Status: NEW --- QA Contact: Matej Melko <mmelko>
Severity: unspecified Docs Contact:
Priority: low    
Version: 6.0.0 GACC: agiertli, soa-p-jira
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Anton Giertli 2014-05-21 13:33:09 UTC
Description of problem:

The requested feature talks about possibility to make some Classifiers exclusive. Imagine class Gender and two subclasses Male and Female, defined in the ontology.
If it was possible to make these classifiers exclusive, it would be possible, via S-RAMP UI to set only one of those.
i.e. user can't set Male if Female is set.
i.e. user can't set Female is Male is set.
OWL Language should be capable of creating such constructs by using owl:disjointWith attribute
http://www.w3.org/TR/owl-guide/#owl_disjointWith
However, this attribute is part of OWL DL and not OWL Lite which is currently used internally.

Version-Release number of selected component (if applicable):

FSW 6.0.0
How reproducible:

always
Steps to Reproduce:
1. Define ontology, one class, two subclasses
2. Upload it to UI and try apply these classifiers on some artifact
3. It is possible to apply them all - parent class, first sub class, second sub class. The desired behavior would to possibility only to apply ONE or ANOTHER sub class.

Actual results:
It is not possible to create exclusive classifiers

Expected results:

it is possible to create exclusive classifiers
Additional info:

Comment 1 Gary Brown 2014-06-18 14:10:14 UTC
The customer portal issue status is Closed - is this still a requirement?