[PyWrapper-devel] MOBY service

[Javier de la T. <ja...@gm...>]

Hi Milko,

I have to watch out the refresh issue in moby. Adding the possibility  
to choose a moby central should not be complicate with an important  
consideration. Should we allow users to have services registered in  
different MOBY registries? If so, the configuration files must be  
changed to use as a service identifier the serviceName, authURI and  
THE REGISTRY were it was registered. This is important to know from  
where to register and deregister the services.

If a pywrapper installation can work only with one single MOBY  
registry then it is easier, I can just add an input field in the  
configtool to allow users to write the endpoint of the registry they  
wanna use.

I believe that the correct solution is to be "multiple registries  
aware" in pywrapper, but this will take a little bit more of time,  
meanwhile this weekend I can add you the simple solution...

Cheers.


On 17/11/2006, at 13:44, Skofic A. Milko (IPGRI) wrote:

> Javier, I finally made my first MOBy service, getTaxaOfBoundingBox,  
> if you are interested in adding it to the examples I send you the  
> files, remember to change the links in the files, they point to the  
> eurisco site.
>
> There is a problem when you register a new MOBY service: TAPIR  
> takes a while before recognising that the service is up and  
> running; when testing one must manually delete the cache files to  
> test it with Dashboard.
>
> Do you think we can get a way to set the MOBY central?
>
> Ciao!
>
> Milko
>
> <getTaxaOfBoundingBox.bmtts.xml>
> This is the BMTTS section.
>
> <getTaxaOfBoundingBox.bmtts.xml>
> This is the output model.
>
> <BoundingBox.xslt>
> This is the input transformation stylesheet.
>
> <TaxonScientificName.xsd>
> This is the schema for the MOBY taxon name.
>
>