Re: [Blueobelisk-discuss] Blue Obelisk Identifiers and resources and images

2007-09-24 Thread peter murray-rust
At 21:50 22/09/2007, Martin A. Walker wrote: >I think the new InChIKey (or "hashed InChI) should meet this need, without >us having to create a BO identifier: >http://www.iupac.org/inchi/release102.html >Do you think this would work? Yes. And I think it should probably be used. >ACD and JChemPai

Re: [Blueobelisk-discuss] Blue Obelisk Identifiers and resources and images

2007-09-24 Thread Rajarshi Guha
On Sep 24, 2007, at 7:40 AM, Egon Willighagen wrote: > Funny you mention this... last week in Ulm, someone suggested (forgot > who) during the CIC-CINF session that one reason against open access > chemistry is the (increased) risk of chemical terrorism :) Shouldn't the gene sequence community b

Re: [Blueobelisk-discuss] Blue Obelisk Identifiers and resources and images

2007-09-24 Thread Egon Willighagen
Hi Peter, On 9/22/07, peter murray-rust <[EMAIL PROTECTED]> wrote: > The discussion on InChIs raises the question as to who creates and > manages communal resources and metadata. InChIs work as they are > algorithmic but they fail for inorganics (especially mineral > polymorphs) and substances ("g

Re: [Blueobelisk-discuss] Blue Obelisk Identifiers and resources and images

2007-09-22 Thread Martin A. Walker
I think the new InChIKey (or "hashed InChI) should meet this need, without us having to create a BO identifier: http://www.iupac.org/inchi/release102.html Do you think this would work? ACD and JChemPaint have already done versions that generate "Wikipedia-ready" PNG files with embedded InChIs. Th

[Blueobelisk-discuss] Blue Obelisk Identifiers and resources and images

2007-09-22 Thread peter murray-rust
The discussion on InChIs raises the question as to who creates and manages communal resources and metadata. InChIs work as they are algorithmic but they fail for inorganics (especially mineral polymorphs) and substances ("glucose", "glutamate"), etc. where conventional human-assigned identifier