[esip-semantictech] Importing SWEET into Protege

[brandon whitehead]

Hi Carlos,

Many thanks for the reply.  More below.

On 15/07/19 10:05 PM, Carlos Rueda wrote:
>      [Fatal Error] :1:50: White spaces are required between publicID and
>      systemID.
> 
>      I've been digging around in my protege log file, but it doesn't
>      actually show up there (the previous output is from the command line).
> 
>      For further context, the page successfully redirects if I hit it in a
>      browser.  If I try to load one of the ontology files, for example
>      http://sweetontology.net/humanAgriculture, in a browser it pushes me to
>      the COR page as expected.  I can curl the URL and get a valid response
>      (full turtle file), but if I try the same thing via Protege (loading
>      that specific ttl file via URL instead of a local copy) I get a 403
>      error --- the same issue Lewis described.
> 
> 
> Same here.  I just did a few tests using HTTPie with variations of the
> basic http://sweetontology.net/sweetAll request, and all responded as
> expected, except when trying the relevant ones in Protege (resulting in
> 403), eg:
> 
> http://sweetontology.net/sweetAll  --Protege should prefer an RDF
> representation via content negotiation)
> 
> http://sweetontology.net/sweetAll.rdf  -- explicit preference for RDF
> via filename extension
> 
> My HTTPie based tests suggest that the 403 error is not being generated
> from the sweetontology.net proxy-pass nor from the COR service.  So
> perhaps worth re-trying all of this with a newer Protege version(?).

Interesting.  Protege 5.5 is the newest stable version.  I've not tried
buidling from source via git and testing.  However, the response/error
is the same in TopBraid Composer (5.3) as was described in Protege so
it's a bigger issue.  Perhaps OWLAPI?

Cheers,
/Brandon

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.esipfed.org/pipermail/esip-semanticweb/attachments/20190715/be1066b1/attachment-0001.sig>