[MOBY-dev] ServiceProvider URL and Logo

[Edward Kawas]

Another way of doing this would be to modify the RDF metadata for a
particular service. I haven't thought about this too deeply, but as a
service provider, if I wish to augment the information in the RDF with extra
information regarding my service, I am free to do so. So for example,
imagine that we agree on a predicate like 'hasLogoURL'. 

Anybody wishing to show logos would only have to check for existence of that
predicate in the RDF and behave accordingly. This wouldn't change the api.

Having said that, I, being the fence sitter moby java developers know and
love ;-), agree with Andreas and think that this information should be
recorded at registration time.

Eddie

 
> -----Original Message-----
> From: moby-dev-bounces at lists.open-bio.org [mailto:moby-dev-
> bounces at lists.open-bio.org] On Behalf Of Andreas Groscurth
> Sent: Monday, July 30, 2007 7:39 AM
> To: Core developer announcements
> Subject: [MOBY-dev] ServiceProvider URL and Logo
> 
> Hi,
> 
> I would like to address an issue we had discussed a little at the meeting
> in
> Vancouver, namely to enable the possibility for service providers to add
> their url (to their homepage) and a logo.
> This was based on the suggestions from the Tigr workshop, where the people
> wanted to have that, so if one is aggregating their service, is possible
> to
> link to the origin of the service.
> 
> Actually there are two ways to do so (in my opinion):
> 
> 1. Add the url to the homepage and the url to a logo into the service
> notes
> for each service result
> 
> 2. Give the opportunity to enter this information while registering a
> service
> 
> 
> In case of 1. there are no changes needed in the API (neither perl nor
> java),
> if somewant wants to use this information they have to parse it from the
> service notes.
> 
> in case of 2. the api has to change (and also all registration clients and
> probably the database....) to  have methods to access these information
> and
> to enter or store them in the service objects (or however this is done
> with
> perl services)
> 
> Intuitively - from a developer - I would suggest 2. because it sounds much
> more clearer to access and to store this information. Putting it into the
> service notes sounds more like a workaround ('ah... everything else is put
> there') - are there any other information in there ? how it is represented
> there ? and so on.. but I think I can see that point 1 is easier and
> sooner
> to use....
> 
> But I'm open for discussion. I can live with all ways :-)
> 
> Best
> Andreas
> _______________________________________________
> MOBY-dev mailing list
> MOBY-dev at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/moby-dev