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] decoupled default namespace and xml:base

Timothy Redmond tredmond at stanford.edu
Wed May 28 20:47:22 PDT 2008


It looks like

      
owlModel 
.getTripleStoreModel().getTopTripleStore().setOriginalXMLBase(xmlBase);

will work.  Maybe there should  be an extra interface to make this  
more convenient.

-Timothy

On May 26, 2008, at 5:43 AM, Olivier Dameron wrote:
> Dear protegeans,
>   The protege-3.4b500 build introduces a decoupled namespace
> management.
>   When I build an ontology using the api, the
> NamespaceManager::setDefaultNamespace(...) works great, but now, the
> value of xml:base is an URI automagically-generated by protege. Is
> there a way to specify its value? Is the only solution to use
> save(file, ontmodel, language, namespace, xmlBase)?
>
> Thank you
> olivier
> _______________________________________________
> protege-owl mailing list
> protege-owl at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03




More information about the protege-owl mailing list