Service Validation Error

[Nicholas Del Rio]

Hello,

So I have a python sadi service up and running here: http://visko.cybershare.utep.edu/lifemapperService

I have tested it via curl and all works as expected.

Next step is to register with our local sadi registry so that it may be consumed by our local share client.  Upon running the validator, I get an error:

"RDF model at http://visko.cybershare.utep.edu/lifemapperService does not contain any statements about http://visko.cybershare.utep.edu/lifemapperService"

I have the following fields set:

    label = "LifemapperService"

    serviceDescriptionText = 'Lifemapper Species Modeling Service'

    comment = 'Lifemapper Species Modeling Service'

    serviceNameText = "LifemapperService"

    name = "lifemapperService"

Thanks again,

Nick

[Jim McCusker]

Does the service validate relative URLs? If I shouldn't be able to expect that, I can make an endpoint URI available for configuration on the service.

Jim

--
You received this message because you are subscribed to the Google Groups "sadi-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sadi-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Jim McCusker

Data Scientist

5AM Solutions

jmcc...@5amsolutions.com

http://5amsolutions.com

PhD Student
Tetherless World Constellation
Rensselaer Polytechnic Institute
mcc...@cs.rpi.edu
http://tw.rpi.edu

[Luke McCarthy]

It looks like this is because Jena differentiates between the URLs http://visko.cybershare.utep.edu/lifemapperService# and http://visko.cybershare.utep.edu/lifemapperService. So a workaround would be to register http://visko.cybershare.utep.edu/lifemapperService# (with the octothorpe).

Alternatively, change the <#> subjects in the output to <>.

[Nicholas Del Rio]

Thanks, was able to register the service by appending #.

It complained a bit about not specifying a contact email, although it still let me register.  Looks like in the Java versions, the creator email is a literal and in the python version it is a resource.

Thanks,

Nick

[Luke McCarthy]

The creator email is a literal for legacy reasons: the mygrid-moby service ontology that we're using specified it that way. So even though that's probably not correct, that's what the parser looks for.

[Nicholas Del Rio]

I am now wondering if the share client requires that services include an email, similarly to how it requires the descriptions?  I'll test in a bit and see if my new python service is invoked by share.

[Luke McCarthy]

The SHARE client shouldn't require anything. The only validation is done by the registry. Once the service is registered, there shouldn't be any other hurdles to clear.