Search Mailing List Archives

Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-owl] Database backend back to OWL/RDF

Bo De Lange bodelange at
Mon Feb 9 05:35:01 PST 2009

Silence from the Protege community....
Tania/Timothy, could you please look into this briefly, since we need a
local RDF/OWL file project to release a build of our own software project,
soon-ish. I've worked around it for now by maintaining two versions of the
.pprj file a database version and a local version, in which I have to
maintain identical changes to forms, multi slot browser display patterns



On Tue, Feb 3, 2009 at 1:17 PM, Bo De Lange <bodelange at> wrote:

> Hi there,
> we are running a database backend Server-Client setup (3.4 beta, build
> 519). Regularly, we require a local copy of the ontology. Clients can easily
> obtain the latest .owl file by File:Export to Format: OWL. However, they
> also require the latest .pprj to see all the forms and multislot browser
> patterns correctly in the local copy.
> For the database backend version, we have a Project-dba.pprj file, which
> will not work on local machines without access to the SQL database. So we
> need to convert the whole dba project on the server machine to an RDF/OWL
> file project that we can copy and use elsewhere. To do this, I've started
> the dba project locally on the server machine, and chose File:Convert
> project to Format:OWL/RDF Files. However, and this will be a familiar
> problem for Tania, the conversion crashes on the Jena writer. Somehow we
> require the Protege Native writer, which I cannot invoke from this menu
> option.
> Is there a quick solution?
> Ideally, we would like for it to be possible to do the export to OWL/RDF
> files from the client side in the server setup.
> Thanks,
> Bo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the protege-owl mailing list