[MOBY-dev] [moby] Re: Suggestion for newtag in Parameter(Secondary Input specification)

[Pieter Neerincx]

Sounds like a good plan to me...

Cheers,

Pi

On  28Feb2006, at 13:14, José María Fernández González wrote:

> I think we should choose the corresponding XML Schema types for each
> primitive object. For instance:
>
> moby:String -> xsd:string (it would not allow XML content) or
> xsd:anyType (any content)
>
> moby:Integer -> xsd:int [-2147483648,2147483647] or xsd:integer (*any*
> integer)
>
> moby:Float -> xsd:double (IEEE double-precision 64-bit floating point
> type), xsd:float (IEEE single-precision 32-bit floating point type) or
> xsd:decimal (*any* real number with a finite number of decimal digits)
>
> moby:DateTime -> xsd:dateTime
>
> moby:Boolean -> xsd:boolean or an enumerated xsd:string
> {'0','1','false','true'}
>
> 	Best Regards,
> 		José María
>
> Paul Gordon wrote:
>> The main problem:
>>
>> If somebody specifies a float, can I legally submit a e-value cutoff
>> like "1.0e-180" (i.e. are we going to assume bit capacity, such as
>> 2^-149 for 16-byte IEEE floating point, or are we supporting  
>> arbitrary
>> precision)? Underflow and overflow can cause problems on many
>> systems...  same thing for integers > 2^32...
>>
>> Actually, do we support scientific notation?  That isn't mentioned  
>> either.
>>
>> Cheers,
>> Paul
>>
>> P.S. Yes, you are right Pieter.  You could enumerate integers, or  
>> even
>> floats for that matter: this distinction matters for a server with
>> strong types, but not for the client.  I've been too client centric
>> lately :-)
>>
>>> On Mon, 2006-02-27 at 23:44 +0100, Pieter Neerincx wrote:
>>>
>>>
>>>
>>>> Hmmm I use enum for some integers as well. I think it's perfectly
>>>> normal to say for example: enum [1,2,4,8].
>>>>
>>>>
>>> Perhaps Paul can clarify what problem he is trying to solve.  My
>>> instincts tell me that maybe he is having difficulty with casting  
>>> un-
>>> typed XML blocks as either Integer or String, as appropriate...  
>>> is that
>>> a correct interpretation of the problem Paul?
>>>
>>> I think the combination of the <datatype> block and the <enum> block
>>> should be able to indicate whether the ENUM is of type String or  
>>> of type
>>> Integer (or Float, or whatever).  Is that not sufficient?  Or am I
>>> misunderstanding what the root of the problem is?
>>>
>>> M
>>>
>>>
>>>
>>> _______________________________________________
>>> MOBY-dev mailing list
>>> MOBY-dev at biomoby.org
>>> http://biomoby.org/mailman/listinfo/moby-dev
>>>
>>>
>>
>> _______________________________________________
>> MOBY-dev mailing list
>> MOBY-dev at biomoby.org
>> http://biomoby.org/mailman/listinfo/moby-dev
>>
>>
>
> -- 
> José María Fernández González		e-mail: jmfernandez at cnb.uam.es
> Tlfn:	(+34) 91 585 54 50		Fax:	(+34) 91 585 45 06
> Grupo de Diseño de Proteinas		Protein Design Group
> Centro Nacional de Biotecnología	National Center of Biotechnology
> C.P.: 28049				Zip Code: 28049
> C/. Darwin nº 3 (Campus Cantoblanco, U. Autónoma), Madrid (Spain)
> _______________________________________________
> MOBY-dev mailing list
> MOBY-dev at biomoby.org
> http://biomoby.org/mailman/listinfo/moby-dev

Wageningen University and Research centre (WUR)
Laboratory of Bioinformatics
Transitorium (building 312) room 1038
Dreijenlaan 3
6703 HA Wageningen
phone: 0317-484 706
fax: 0317-483 584
mobile: 06-143 66 783
pieter.neerincx at wur.nl