Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Annotation Editor should provide less hostile behaviour when xsd:boolean types are selected #691

Closed
matthewhorridge opened this issue Aug 21, 2017 · 0 comments
Assignees
Labels
Type: Enhancement A request for a change that is an enhancement

Comments

@matthewhorridge
Copy link
Contributor

From the mailing list:

Right now when you edit a data or annotation property value the default is for the datatype to be the same as it was the last time you edited one of them. This can cause loss of an edit. Yesterday I added a long comment annotation but forgot to check the datatype which was set to xsd:boolean from the last annotation (owl:deprecated) I had edited. When I committed the change it just showed up as "false" I'm guessing because anything other than "true" for a boolean is interpreted as false. It would be nice if the datatype could default to whatever the datatype for that specific annotation or data property is rather than just whatever it was the last time. It would also be nice to get a warning when you put something in a boolean other than "true" or "false" so that you know what you entered is interpreted as false. Previously I entered "True" for a boolean but that ends up as "false" also.

@matthewhorridge matthewhorridge added this to the Protégé 5.6.0 milestone Jan 15, 2019
@matthewhorridge matthewhorridge added the Type: Enhancement A request for a change that is an enhancement label Jan 15, 2019
@matthewhorridge matthewhorridge self-assigned this Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement A request for a change that is an enhancement
Projects
None yet
Development

No branches or pull requests

1 participant