Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / protegeproject/protege issues and pull requests
#1174 - java.net.URISyntaxException when have "%" in the invidual name
Issue -
State: open - Opened by yasenstar over 1 year ago
#1173 - Feature request: List open windows in windows menu
Issue -
State: open - Opened by alanruttenberg over 1 year ago
#1172 - Update pom.xml
Pull Request -
State: closed - Opened by mosfet80 over 1 year ago
#1171 - Update pom.xml
Pull Request -
State: closed - Opened by mosfet80 over 1 year ago
#1170 - Prepare 5.6.3 release
Pull Request -
State: closed - Opened by gouttegd over 1 year ago
#1169 - Protege hang when editing in Snap SPARQL tab for querying
Issue -
State: open - Opened by yasenstar over 1 year ago
#1168 - Is there short date supported besides xsd:dateTime
Issue -
State: open - Opened by yasenstar over 1 year ago
- 2 comments
#1167 - Assigning individuals from a CSV file to an ontology in Protégé
Issue -
State: open - Opened by Haythamyounus over 1 year ago
- 5 comments
#1166 - Bump org.eclipse.jgit:org.eclipse.jgit from 4.8.0.201706111038-r to 6.6.1.202309021850-r
Pull Request -
State: closed - Opened by dependabot[bot] over 1 year ago
Labels: dependencies
#1165 - Updated jCraft into pom.xml
Pull Request -
State: closed - Opened by mosfet80 over 1 year ago
#1164 - Problem with serialization in Protégé 5.6: offsets in "genid"
Issue -
State: open - Opened by jpi-seb over 1 year ago
- 1 comment
Labels: Type: Bug, Status: Reproduced
#1163 - How to Implement Annotation Property Enumeration with Error Handling in Protege 5.6
Issue -
State: open - Opened by shah-iq over 1 year ago
#1162 - Protege.exe does not pass arguments to the 'main' method
Issue -
State: closed - Opened by jmkeil over 1 year ago
- 3 comments
Labels: Type: Bug, Status: Reproduced
#1161 - Release Signing Certificate
Issue -
State: open - Opened by aef over 1 year ago
- 1 comment
#1160 - Problem in Data Property inference with swrl in protegé
Issue -
State: open - Opened by andredemori over 1 year ago
- 1 comment
#1159 - pom.xml settings for java code generated by protege
Issue -
State: open - Opened by tinglion over 1 year ago
- 1 comment
#1158 - Missing the OWL Viz tab
Issue -
State: open - Opened by gpadvorac over 1 year ago
- 1 comment
#1157 - Support for untyped IRIs
Issue -
State: open - Opened by alanruttenberg over 1 year ago
#1156 - MakePrimitiveSiblingsDisjoint is not showing on the Edit menu
Issue -
State: open - Opened by matthewhorridge over 1 year ago
Labels: Type: Bug
#1155 - protege 5.6 wont run on windows10 that its regional format is persian
Issue -
State: open - Opened by serkhelesheyi over 1 year ago
#1154 - FMA links in Protégé do not direct to referenced term
Issue -
State: open - Opened by bvarner-ebi over 1 year ago
- 1 comment
Labels: Status: Reproduced
#1153 - Autosuggest window is forced in the background when using the "Entity IRI field" for annotations with instances
Issue -
State: open - Opened by StroemPhi over 1 year ago
- 2 comments
Labels: Type: Bug, Status: Reproduced
#1152 - Editing, re-editing a dcterms:date annotation causes xsd:dateTime datatype to be lost
Issue -
State: open - Opened by ddooley over 1 year ago
Labels: Type: Bug, Status: Reproduced
#1151 - Protege OWLDoc cannot save Chinese classes names correctly
Issue -
State: open - Opened by yasenstar over 1 year ago
- 5 comments
Labels: Type: Bug, Status: Reproduced
#1150 - Strange "ontology already exists" error
Issue -
State: open - Opened by alanruttenberg over 1 year ago
- 2 comments
Labels: Type: Bug, Status: Reproduced
#1149 - Bug: MacOS double clicking ontology to open Protege fails to open ontology
Issue -
State: closed - Opened by alanruttenberg over 1 year ago
- 1 comment
#1148 - Feature request: show a module of the active ontology
Issue -
State: open - Opened by alanruttenberg over 1 year ago
Labels: Type: Enhancement
#1147 - Fallback to OS-independent file-saving dialog on macOS
Pull Request -
State: closed - Opened by gouttegd over 1 year ago
#1146 - For annotation properties, usages are double-counted in Usage tab
Issue -
State: open - Opened by jclerman almost 2 years ago
#1146 - For annotation properties, usages are double-counted in Usage tab
Issue -
State: open - Opened by jclerman almost 2 years ago
#1146 - For annotation properties, usages are double-counted in Usage tab
Issue -
State: open - Opened by jclerman almost 2 years ago
Labels: Type: Bug, Status: Needs Reproducing
#1145 - Protege 4.1 wont run
Issue -
State: open - Opened by IchBinSharky almost 2 years ago
#1145 - Protege 4.1 wont run
Issue -
State: open - Opened by IchBinSharky almost 2 years ago
#1144 - Regular Expression In xsd:pattern not retained after loading RDF file.
Issue -
State: open - Opened by cpmedined almost 2 years ago
#1144 - Regular Expression In xsd:pattern not retained after loading RDF file.
Issue -
State: open - Opened by cpmedined almost 2 years ago
#1144 - Regular Expression In xsd:pattern not retained after loading RDF file.
Issue -
State: open - Opened by cpmedined almost 2 years ago
#1143 - Encode some metadata information related to entities in the ontology metadata
Issue -
State: open - Opened by jonquet almost 2 years ago
- 3 comments
#1142 - Additional modification date and isDefinedBy in "new entities metadata" properties.
Issue -
State: open - Opened by jonquet almost 2 years ago
Labels: Type: Enhancement
#1142 - Additional modification date and isDefinedBy in "new entities metadata" properties.
Issue -
State: open - Opened by jonquet almost 2 years ago
Labels: Type: Enhancement
#1142 - Additional modification date and isDefinedBy in "new entities metadata" properties.
Issue -
State: open - Opened by jonquet almost 2 years ago
Labels: Type: Enhancement
#1141 - Change default "new entities metadata" for date
Issue -
State: open - Opened by jonquet almost 2 years ago
#1140 - Can we encode "New entities metadata" as a metadata of the ontology?
Issue -
State: open - Opened by jonquet almost 2 years ago
- 1 comment
Labels: Type: Enhancement
#1140 - Can we encode "New entities metadata" as a metadata of the ontology?
Issue -
State: open - Opened by jonquet almost 2 years ago
Labels: Type: Enhancement
#1140 - Can we encode "New entities metadata" as a metadata of the ontology?
Issue -
State: open - Opened by jonquet almost 2 years ago
Labels: Type: Enhancement
#1139 - https prefixes changed to http
Issue -
State: open - Opened by henrietteharmse almost 2 years ago
Labels: Type: Bug, Status: Reproduced
#1139 - https prefixes changed to http
Issue -
State: open - Opened by henrietteharmse almost 2 years ago
Labels: Type: Bug, Status: Reproduced
#1139 - https prefixes changed to http
Issue -
State: open - Opened by henrietteharmse almost 2 years ago
Labels: Type: Bug, Status: Reproduced
#1138 - Protege 5.6.* on Mac OS continues to ask permission to access Document (and possibly other) folder.
Issue -
State: open - Opened by samsontu almost 2 years ago
#1138 - Protege 5.6.* on Mac OS continues to ask permission to access Document (and possibly other) folder.
Issue -
State: open - Opened by samsontu almost 2 years ago
- 3 comments
#1138 - Protege 5.6.* on Mac OS continues to ask permission to access Document (and possibly other) folder.
Issue -
State: open - Opened by samsontu almost 2 years ago
#1137 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1137 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1136 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1136 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1136 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1135 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1135 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1134 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1134 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1134 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1133 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1133 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1132 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1132 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1131 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1131 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1131 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1130 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1130 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1130 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1129 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1128 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1127 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1127 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1126 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1125 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1125 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1124 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1124 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1123 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1123 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1122 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1122 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1122 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1121 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1121 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1121 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1120 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
- 1 comment
#1120 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
- 1 comment
#1119 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1119 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1119 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1118 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1117 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1116 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1116 - Unify the way new versions of plugins are reference
Issue -
State: closed - Opened by dsadasdasd54 almost 2 years ago
#1115 - Problem with Git folder: Caused by: org.eclipse.jgit.errors.CorruptObjectException: Unknown DIRC version 4
Issue -
State: open - Opened by SimonBin almost 2 years ago
- 1 comment
Labels: Type: Bug, Status: Reproduced
#1114 - UI on Windows: Tabs have lost their boundaries? Release 5.6.1
Issue -
State: closed - Opened by dlutz2 almost 2 years ago
- 2 comments
#1114 - UI on Windows: Tabs have lost their boundaries? Release 5.6.1
Issue -
State: open - Opened by dlutz2 almost 2 years ago
#1113 - please reopen #910 (found in 5.6.1)
Issue -
State: closed - Opened by rwynne almost 2 years ago
- 1 comment