W3C home > Mailing lists > Public > public-semweb-lifesci@w3.org > September 2009

Re: Namespace needed for OWL rendering of Translational Medicine Ontology

From: Eric Prud'hommeaux <eric@w3.org>
Date: Thu, 17 Sep 2009 23:49:58 -0400
To: Colin Batchelor <BatchelorC@rsc.org>
Cc: public-semweb-lifesci <public-semweb-lifesci@w3.org>
Message-ID: <20090918034958.GD15122@w3.org>
* Colin Batchelor <BatchelorC@rsc.org> [2009-09-17 14:28+0100]
> Hello,
> The Translational Medicine Ontology activity of HCLS:
> http://esw.w3.org/topic/HCLSIG/PharmaOntology/
> is putting together an ontology.  Now, if we're to do this in OWL we need a namespace.
> Is it going to be possible for the W3C to provide one for us?

http://www.w3.org/ns/ is allocated for namespaces. There is a defined
policy for using that area to back documents which are being published
as W3C technical reports. (If we don't publish a TR, we can almost
definitely use it anyways, but there's no precedent.)

We can also write put a namespace document (which would probably
include a schema and some promises about the stability) under
e.g. http://www.w3.org/2001/sw/hcls/ (or e.g. /2009/trans/). Since
namespaces and schemas are effectively social contracts about
stability, we may want to start development someplace and once we have
a sense that it will be stable, move to /ns. That will mean that
everyone who has existing code will have to fix it to use the new
namespace (the cost), but the development data won't leave misleading
statements around for production software to trip over later on.

Do these options sound like they meet our needs?

> Best wishes,
> Colin.
> --
> Dr Colin Batchelor MChem MRSC, Senior Informatics Analyst, Informatics R&D
> Informatics Department,
> Royal Society of Chemistry, Thomas Graham House, Cambridge UK CB4 0WF
> batchelorc@rsc.org t: +44 1223 432280
> This communication (including any attachments) is intended for the use of the addressee only and may contain confidential, privileged or copyright material. It may not be relied upon or disclosed to any other person without the consent of the RSC. If you have received it in error, please contact us immediately. Any advice given by the RSC has been carefully formulated but is necessarily based on the information available, and the RSC cannot be held responsible for accuracy or completeness. In this respect, the RSC owes no duty of care and shall not be liable for any resulting damage or loss. The RSC acknowledges that a disclaimer cannot restrict liability at law for personal injury or death arising through a finding of negligence. The RSC does not warrant that its emails or attachments are Virus-free: Please rely on your own screening.


office: +1.617.258.5741 32-G528, MIT, Cambridge, MA 02144 USA
mobile: +1.617.599.3509

Feel free to forward this message to any list for any purpose other than
email address distribution.

There are subtle nuances encoded in font variation and clever layout
which can only be seen by printing this message on high-clay paper.
Received on Friday, 18 September 2009 03:50:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:20:45 UTC