Hi Fred, when doing Generate all for the ontologies, I'm getting the normal "getIronJSONSchema for ontology: file://localhost/data/ontologies/files/wsf.owl" (2 times!) and than php error:

Strict warning: Only variables should be passed by reference in osf_ontology_main() (line 798 of /[...]/public_html/sites/all/modules/osf/modules/osf_ontology/osf_ontology.module).

(the brackets are my addition, it is the path).

Actually getting two pages of similar warnings, also for lines 749, 751 and 800. Seems something not working with XPath query. Couldn't debug, last thing I thought could be the cause is an empty/wrongly formated Dom...

Hope you can help, my php is version 5.4.35
Thanks again,
Roen

CommentFileSizeAuthor
#1 error_ontology_import.txt28.3 KBroeneman
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

roeneman’s picture

FileSize
28.3 KB

Hi Fred, further on the ontology's, I reset my Drupal site and now followed your manual.
Getting stuck at uploading the muni.owl. Please see debug info attached.

Thanks again for your help, I hope this system will start to work sometime soon.
Cheers,
Roen

fgiasson’s picture

Hi,

It is the OWLAPI complaining that it couldn't load/resolve the ontology file "file://localhostpublic://osf/tmp/Muni.owl". Are you use this file is locally available given that URL? Don't think this is a valid, is it?

roeneman’s picture

Hi, the part public://osf/tmp/ is the directory for the ontology files set at "admin/config/osf/osf_ontology".

So now I tested full path names, including slashes at start and end. Now either OSF doesn't find it or Drupal gives a can't move the file, directory unknown message. Suppose something is not alligned with the usages of thes full path names or slashes? Good that be?

Cheers,
Roen

EDIT: The owl (although not correct uploaded) is now showing up in under "Datasets" in Drupal. Not so in DMT, but it is in Drupal. Is this supposed to happen?

fgiasson’s picture

Hi,

What I can see in the debug file you provided is that all default ontologies (probably imported via the OMT?) have been successful because the URI used by the OWLAPI was accessible. Here is an example of such a URI:

  • file://localhost/data/ontologies/files/aggr.owl

However, what the subsequent Ontology: Create endpoint receive is the following kind of URIs:

  • file://localhostpublic://osf/tmp/Muni.owl

This URI appears to be generated by OSF for Drupal, somehow. Some more debugging on your side will be required to see why this URI is being generated. Try using Drush to see what is in this variable: "osf_OntologySettings_ontologies_files_folder" that may be the issue.

Thanks,

Fred

roeneman’s picture

Status: Active » Closed (works as designed)

The "public" part of "file://localhostpublic://osf/tmp/Muni.owl" is a reference of the Drupal file system,
so I suppose I should use full path's only.
Thanks Fred.