Sorry, I've overlooked nuclear spin data, it's already present in isotopes.xml 
:)

But it's representation (values like "1/2+") is not good for parsing. Maybe 
it's worth to convert them into conventional floating-point numbers?

Also, elements.xml lacks information about most abundant isotope, so it's seems 
like I need to parse all of them and compare relativeAbundance values to get 
nuclear spin for the most abundant isotope. Is there any workaround?


17.06.10, 12:43, "Egon Willighagen" <[email protected]>:

> On Thu, Jun 17, 2010 at 10:35 AM, Egon Willighagen
>   wrote:
>  > Hi Daniel,
>  >
>  > On Thu, Jun 17, 2010 at 10:20 AM, Daniel Leidert
>  >  wrote:
>  >> Further please note, that only one CCO (at least I
>  >> guess you mean the Creative Commons license series) license qualifies
>  >> for Debian main and I would like to leave bodr in the main section of
>  >> Debian without stripping stuff.
>  >
>  > No. CC Zero (CC0) is not in the CC license series you refer to. It is
>  > also not mentioned on that Debian page.
>  
>  See:
>  
>  
> http://lists.debian.org/cgi-bin/search?query=cc0&DEFAULTOP=and&author=&sort=relevance&HITSPERPAGE=10&language=en
>  
>  It seems all agree that CC0 is DFSG compatible, though some complain a
>  bit about the length formulation.
>  
>  You also might want to read this bug report, where CC0 is stated as
>  DSFG-compatible:
>  
>  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572648#4
>  
>  Which is about the unifdef package in main.
>  
>  I hope this addresses your worries...
>  
>  Egon
>  
>  

-- 
Regards,
Konstantin

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Blueobelisk-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/blueobelisk-discuss

Reply via email to