search

ProperNameOntology / proper-name-ontology

Automatically exported from code.google.com/p/proper-name-ontology
1 stars 2 forks source link

Parse error when import PNO directly and/or indirectly #2

Closed GoogleCodeExporter closed 7 years ago

GoogleCodeExporter commented 9 years ago 
When I open OMRSE in Protege 4.2 build 295, I receive a parse error that is 
connected to PNO.  (See attached screen shot).

This error has been duplicated by another user in Protege 4.3 build 304.

If I remove the PNO from d-acts and import the resulting file to OMRSE, 
everything loads as expected. (This is not reflected in the available OMRSE 
code, but was tested with local files on my machine.)

Thanks.

Original issue reported on code.google.com by aellenhi...@gmail.com on 17 Mar 2015 at 7:41

Attachments:

GoogleCodeExporter commented 9 years ago 
The source of the parse error that is related to a BFO1.1 and is not generic to 
PNO (and thus, outside the sphere of influence of PNO developers). BFO has been 
moved from googlecode to github and now uses https: instead of http:. The 
problem only occurs in Protege 4. Protege 5 is not affected.

The BFO community is in the process of fixing that problem (I got an e-mail 
from James Overton that seems to suggest that it is fixed or will be soon).  
I'd suggest you try again later and please report back.

PNO opens without errors in Protege 5.

Best,
Mathias

Original comment by MBrochhausen@gmail.com on 17 Mar 2015 at 8:01