W3C home > Mailing lists > Public > public-perma-id@w3.org > April 2019

Re: Using w3id.org URIs in OWL imports?

From: Marijane White <whimar@ohsu.edu>
Date: Tue, 2 Apr 2019 15:40:37 +0000
To: Stian Soiland-Reyes <soiland-reyes@manchester.ac.uk>, "public-perma-id@w3.org" <public-perma-id@w3.org>
Message-ID: <FA4A15FC-F76F-49D7-B0B8-09B1AE849298@ohsu.edu>
Ok, Protégé 5.5 works fine for me too.  Thank you!


On 2019/04/02, 8:29 AM, "Marijane White" <whimar@ohsu.edu> wrote:

    In Protégé 5.2 on OS X El Capitan it still gives me an empty Confirm imports screen for https://w3id.org/credit/ontology.  I hadn't considered the possibility that Protégé might be the problem. I'll try upgrading and see if that fixes it.  Or perhaps my ancient OS is at fault, but that's more complicated to fix due to my employer's IT policies.
    The purl.org imports are not the problem because they were only added yesterday; they're actually a workaround for the issues I'm having with the w3id URI.  I am in the middle of a development sprint and I needed to get unblocked; I hadn't realized it might take a week to get a response on this list.  I maintain purls for other ontologies there and despite all the various issues with purl.org (which is why I initially chose w3id.org in the first place), I at least knew that they work in Protégé. 
    I can look into providing a file with a .rdf extension.  The ontology is implemented with the Ontology Development Kit which defaults to building .owl and .obo files.
    On 2019/04/02, 1:58 AM, "Stian Soiland-Reyes" <soiland-reyes@manchester.ac.uk> wrote:
        https://w3id.org/credit/ontology loads for me in Protege 5.5.0 on Ubuntu 18.04.
        It might be because http://purl.org/ was misbehaving last week and you also import some ontologies from there?
        Or just a guess, but it might be because the redirected 

        is returned by GitHub as 
        Content-Type: text/plain
        What if you have a *.rdf extension on GitHub side so it is sent as application/rdf+xml then it might help other consumers of your ontology.
        It should however not have affected Protege as it's OWLAPI tends to try every possible RDF de-serialization as a fallback.
        Stian Soiland-Reyes
        The University of Manchester


        On Wed, 2019-03-27 at 01:11 +0000, Marijane White wrote:
        > Greetings,
        > Last fall, with assistance from David Lehn (for which I am extremely
        > grateful), I set up the credit redirects: 
        > https://github.com/perma-id/w3id.org/tree/master/credit

        > I’ve since identified an issue with the 
        > https://w3id.org/credit/ontology URI -- if I try to use it in an
        > owl:import statement, Protégé says it cannot locate the ontology, and
        > it’s not clear to me why.  Would anyone be able to assist me in
        > resolving this issue?
        > Thank you,
        > Marijane White, M.S.L.I.S.
        > Data Librarian, Assistant Professor
        > Oregon Health & Science University Library
        > Phone: 503.494.3484
        > Email: whimar@ohsu.edu
        > ORCiD: https://orcid.org/0000-0001-5059-4132


Received on Tuesday, 2 April 2019 15:41:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 2 April 2019 15:41:11 UTC