I am working on an ontology. Suddenly, Protege closes unexpectedly. When I reopen it and open the last ontology I notice that all my classes, individuals and properties are now renamed with the prefix 'owl:'. With this my SPARQL queries no longer work. So far I've worked around it by opening an older version of the same ontology but it's a pain to manually update the old one to the new one because I simply can't find how to remove this prefix. Please help!
I resolved this issue by saving the file as RDF/XML. I was using Turtle format when the issue occurred.
Related
SUMMARY:
I need the most efficient workflow to individually edit over 200 files, and have them automatically disappear from the search results as they are updated.
DETAILS:
I am in the process of adding logging throughout a legacy system, and need to update over 200 files, each with their own custom code. I need to edit them one by one, and would like for the updated files to automatically disappear from my working search results after I have completed each one. The idea is to know how many and which ones still need to be updated as I slowly work through them all.
I already had to do something similar a few months ago, but on a much smaller scale, and I used an old-school HACK to do it. I did a search and replace for my keyword, and intentionally misspelled it. I then used the misspelled keyword for my search, and corrected it when editing each file, hence automatically removing it from the list. It "works", but is obviously a TOTAL HACK.
I recently started using IntelliJ IDEA, and am not yet familiar with the more advanced features like Find in File Scopes, Search Structurally, Search Templates, etc., but I am sure there HAS to be a "correct" way to do this in IntelliJ, and I just don't know how.
I am currently using "Find in Files" to work through the list, and recently found "All Changed Files" in the Scope list, which is actually the EXACT OPPOSITE of what I need. Is there a way to show "All UNCHANGED Files"??? That would work PERFECTLY in a pinch! But really, I would rather learn the CORRECT way to do this in IntelliJ.
Thanks!
I'm using the latest version of OntoRefine and want to add a nested triple to a blank node. I'm following the exact instructions on Ontotext website. In the interface there is supposed to appear an arrow next to the object (in the picture on the right side, just under the waste bucket). But it does not appear when the object is a blank node.
It does appear when I create an IRI, but in my case a blank node would be the way to go. When I import the files that are in the tutorial on the Ontotext website, I still do not see the nested triples that are in the example. However...... when you export as RDF, the correct triples - including the ones with the blank nodes as subject - are created.
So it seems that the functionality works, but the interface does not support it. I was also able to manually change the JSON file for my own data and got the correct RDF triples.
Question is: am I the only one that has a problem with the interface? Am I doing something wrong or is this a bug? Curious to know what your experiences are.
in what version of GraphDB are you facing this issue, as problems with blank nodes in the OntoRefine's RDF Mapper have been addressed in GraphDB version 9.5.
This bug has reappeared, but will be fixed in OntoRefine 1.1.1 to be released next week.
I open the SPARQL Query tab in Protege but the result is this:
How can I write my query?
It happens in version 2.0.1 of Protégé SPARQL Plugin, bundled with
Protege 5.2, after any ontology is loaded.
Update the the "OWLAPI RDF Library" and "Protege SPARQL Plugin" to the latest version with the auto-update mechanism (which appears when starting up Protege or can be activated through the File > Check for plugins… menu):
Source: https://github.com/protegeproject/sparql-query-plugin/issues/10.
For Protege 5.5.0, you may also need to add query view from menu:
Window--> View-> Query View-> SPARQL Query
And drop it into the SPARQL Query tab.
try to enlarge the heap size for Protégé.
I have had the same problem for SPARQL Query and others. Plugin update never worked for me and each time I just delete the new plugins and Protégé works as If nothing happens.
So the solution I have found till now is to not update plugins but to enlarge heap size.
How to do it?
There is a wiki for Protégé 3 and 4 here: https://protegewiki.stanford.edu/wiki/Setting_Heap_Size but not for Protégé 5 so I was supposed to figure it myself.
Well, you should just open the Protege.l4j.ini file and change the heap size limits from {200,500} to {2000,5000} (I am not sure If your computer will stand that, you must read the wiki above to know more about it).
It should be like this:
-Xms2000M
-Xmx5000M
-Xss16M
Hope this can help someone there.
Best regards,
AmelieSpark.
Another way around is downloading the "Snap SPARQL Query" plugin and adding the view on the SPARQL tab.
I've got serious issues with XCode right now and i cant really figure out what to do, or even whats wrong.
The project i'm working on was working perfectly yesterday, but today when i started it i got like 20 "Redefinition of enumerator" errors, and to the point where "Too many errors emitted. Stopping now".
The wierd part is that ALL my backups of the project does this aswell. Even the ones from 2,3 or 4 days ago which hasnt been altered.
No other project seems to be affected by this.
I've tried Cleaning the build, removing Derived data, checking for duplicate files somehow (even though that shouldnt be possible), all linker seems to be in order. Anyone got any tips for me?
Thank you!
you should import
#import "Facebook.h"
instead
#import <FacebookSDK/FacebookSDK.h>
I just had this exact problem about "Redefinition of enumerator" errors coming out of nowhere.
The problem was that accidentally (maybe some unintended drag with the mouse) I had copied one of the project directories into some other, thus duplicating it.
On the other hand I use git and generally was using 'git status -uno' which hides untracked files.
So I was not seeing the untracked duplicated directory that was duplicating enums in the project, from my perspective I had a clean HEAD with weird errors :S
Lesson learned: use .gitignore rather than '-uno' option
This issue still happens in 2019 smh.
If you get this go check File->Workspace Settings and set build system to Legacy Build System. This should fix the issue.
I had the same error and was really stuck. But found that the project folder nam had white spaces. I changed that and the error went off!
Eg: Changed folder name My Project to MyProject
For anyone has the same problem, who pulled out hair for hours/days.
Let's double check and remove redundant Header Search Paths, delete Derived Data if needed.
After that, the issue will be resolved.
I'm seeing a strange build bug a lot. Sometimes after typing some code we receive the following build error.
Class 'clsX' must implement 'Event PropertyChanged(sender As Object, e As PropertyChangedEventArgs)' for interface System.ComponentModel.INotifyPropertyChanged'.
And
'PropertyChanged' cannot implement 'PropertyChanged' because there is no matching event on interface 'System.ComponentModel.INotifyPropertyChanged'.
Those error should never go together! Usually we can just ignore the exception and build the solution but often enough this bug stops our build. (this happens a lot using Edit and Continue which is annoying)
We're using Vb.net and c# mixed in one big solution.
Removing the PropertyChanged event and retyping the same code! sometimes fixes this.
Question:
Has anyone else seen this problem and has some suggestions how to prevent his?
We're using a code generator that causes this error to surface but just editing some files manually triggers this exception too. This error occur's on multiple machines using various setups.
Someone had the same exact issue discussed here. It sounds like there is an issue with this build picking up an old version of a binary. I would try the following in order:
Verify all assembly references use project references where possible within the Visual Studio solution.
Disable build parallelization in case there is some weird file locking issue with concurrent project builds. Go to Tools -> Options, Projects and Solutions -> Build and Run, then set "maximum number of parrellel project builds" to 1. Not the best solution but it may help narrow down the problem.
Disable the Hosting Process in case it's locking some file causing an assembly to not get rebuilt correctly. For C# project go to Project Properties, Debug tab, and uncheck "Enable the Visual Studio hosting process". For VB.NET project you'll need to Unload Project, Edit the project file, and add <UseVSHostingProcess>false</UseVSHostingProcess> to the PropertyGroup of each configuration. Again, not the best solution but you probably won't notice a difference.
Lastly, try doing a Clean + Build to try and resolve the issue when it occurs (I know this is not a fix but it's easy enough to do), also Rebuild may be slightly different than Clean + Build so try the latter if the former doesn't work.
As I can not comment due to lack of appropriate points.
But I would like to share one of my experience:
In an aspx.cs page I was working, used to compile fine and some time gave mysterious error of a variable not defined or function not defined or sometime variable or the function defined two times. I changed possibly each and every variable and function name but there seemed no effect , but after entering a simple space or a new line at any place in the file used to solve the compile error. At one time I tried to save the file (in a different encoding as i am used to experiments) and found that the file was not saving in the correct encoding (i.e. the ansi encoding because the file had a unicode character ), I removed the unicode character and that compile error didn't bothered me again.
This unicode character problem could be (not a hard and fast rule) there so you could check it.
Nuke & restore using source control (TFS instructions here):
Make sure you have everything checked in
Exit Visual Studio
Rename the project directory to .Bak (effectively deleting it)
Reopen Visual Studio and in source control:
Get Specific Version
check 'Overwrite... not checked out' and 'Overwrite ... even if local version matches'
Re-open project
Another problem: Make sure some source files are not newer than the current date (or your date is set back). Often this happens in apps where you are doing logic that requires certain things to happen differently on certain dates. You change your clock to test it, make a revision to the source with the date advanced, set the date back, and viola, rebuild does not rebuild that file.
You say 'typing it in again' - can you try just saving? After 40 years since MULTIX the .net build still decides what has changed by checking the file timestamp.
good luck!
When you get the error, is it always on the VB calling C# side, or vice-versa, or does it work both ways?
If the answer is either of the first two situations, try building the "callee" project within the solution before building the "caller" project to see if it stops the situation.
Also, just in case it may jog something for you to think about, does this error crop up when you change a VB file or a C# file, or is there no correllation?
Oh, and sorry this looks like an answer instead of a comment, I cannot post comments yet (need 50 rep).