[MOBY-dev] RFC #1863 Error Handling in MOBY-S -- Vote Called

[David González Pisano]

Frank,

Probably the main problem with the PIB is its location, inside the 
Object structure. One of the initial options we considered was to report 
exceptions inside mobyData, but mixing "data" with "what happened while 
computing the data" information didn't look like the best idea. Using 
the PIB also brings up again the problem of what is an empty object: can 
we report back a "not so empty object", ie, an object with no data but 
PIB data? What about an object with no data but CrossReferences? Is not 
really clear to me. Given the examples about the PIB in the 
specification, I always thought it was a good place to fill with static 
data associated to my results (like software version, database release, 
etc..), not really about why the service didn't work.

The last proposal  we uploaded includes a possible solution to avoid 
XML-mixed elements, basically permiting serviceNotes to have two 
elements: mobyException and Notes. This solution allows to extend the 
servicNotes element with other uses/schemas in the future.

David

Gibbons, Francis escribió:

>   4) The proposal is not clear how to integrate new XML tags in
>serviceNotes with the current usage of serviceNotes. The current usage is
>a free text: should this free text be expected before, or after the
>exception code? Should it be there either exception tags or classic notes
>text? This would be the only place in Biomoby API with XML-mixed element,
>so it needs to be clarified, an example showing all possibilities would be
>beneficial.
>
>
>Martin, I wonder if the Provision Information Block (PIB) would make a more appropriate home for this XML content. As I understand if (from very brief conversation with Mark) it is not used right now (at least in the Perl API, though perhaps it's used in the Java version).  The current API has this to say about PIB: http://www.biomoby.org/twiki/bin//view/Moby/MobySAPI#Provision
> 
>Specifially PIB was intended to provide XML-encoded metadata about the service, and maybe there's a good reason to restrict it to that. I do agree that mixing free text with XML (or having the content be ambiguous) would be tricky, and should be avoided if possible. Perhaps this is a way around that particular issue.
> 
>-Frank
>
>_______________________________________________
>MOBY-dev mailing list
>MOBY-dev at biomoby.org
>http://www.biomoby.org/mailman/listinfo/moby-dev
>
>
>
>  
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dgpisano.vcf
Type: text/x-vcard
Size: 349 bytes
Desc: not available
URL: <http://lists.open-bio.org/pipermail/moby-dev/attachments/20050928/31f7573e/attachment-0001.vcf>