Dear LODers,
we are currently working on a project for the United Nations Office
for the Coordination of Humanitarian Affairs (OCHA) in Geneva to
develop a Humanitarian Exchange Language (HXL). Some information about
the project is available at https://sites.google.com/site/hxlproject/.
One of
Hi all
I've been lurking to this conversation for a while, and since Kerstin has
put my name on the table, I thought I could just drop in.
Seems to me that what Peter tries to achieve regarding linking to OBO
ontologies is a real challenge. The logic (please read : logic in a loose
sense here,
Hi Carsten,
On 2/22/2012 12:02 PM, Carsten Keßler wrote:
Dear LODers,
we are currently working on a project for the United Nations Office
for the Coordination of Humanitarian Affairs (OCHA) in Geneva to
develop a Humanitarian Exchange Language (HXL). Some information about
the project is
On Wed, Feb 22, 2012 at 2:55 AM, Peter DeVries pete.devr...@gmail.comwrote:
Hi Alan,
Here is an example from the Hymenoptera Anatomy Ontology
http://obofoundry.org/cgi-bin/detail.cgi?id=hymenoptera_anatomy
Example via my endpoint
Hi Alan,
*We use OWL and the Virtuoso endpoint you are using doesn't understand it.
*
Isn't it more accurate to say that OBO is not the same as the OWL
standards? i.e. *OBO does not equal OWL.*
- Pete
On Wed, Feb 22, 2012 at 9:15 AM, Alan Ruttenberg
alanruttenb...@gmail.comwrote:
On Wed,
Hi Carsten,
I agree with the comments below. I think what Bob is suggesting is that you
include a non-ontology Core (DCMI for example).
Three critical classes are Language, Jurisdiction and (not included in DCMI)
Currency (or portable value). That would be ISO 639-2, ISO 3166 and ISO 4217.
Hi Bob,
At a first glance, your ontology looks very interesting and well designed.
thanks, we are doing our best ;)
So there might be the (rather old) need for
statement identifiers, i.e., a URI (or maybe also a bnode) for identifying a
single triple and to be able to describe external
Hi Gannon,
I agree with the comments below. I think what Bob is suggesting is that you
include a non-ontology Core (DCMI for example).
I am not sure whether I get that correctly, but it is pretty clear to
use that we need something like this. We are already using some of the
DCMI properties
Hi Carsten,
On 2/22/2012 5:51 PM, Carsten Keßler wrote:
Hi Bob,
At a first glance, your ontology looks very interesting and well designed.
thanks, we are doing our best ;)
So there might be the (rather old) need for
statement identifiers, i.e., a URI (or maybe also a bnode) for
On 22/02/2012 17:21, Bob Ferris wrote:
[...] Named Graphs unnecessary fragment complex descriptions into
(very) small piece due to their provenance descriptions*. So when you
would like to query this complex description at once you may have to
include many Named Graphs. This makes the SPARQL
On 2/22/12 9:15 AM, Alan Ruttenberg wrote:
On Wed, Feb 22, 2012 at 2:55 AM, Peter DeVries pete.devr...@gmail.com
mailto:pete.devr...@gmail.com wrote:
Hi Alan,
Here is an example from the Hymenoptera Anatomy Ontology
On 2/22/12 12:30 PM, Barry Norton wrote:
On 22/02/2012 17:21, Bob Ferris wrote:
[...] Named Graphs unnecessary fragment complex descriptions into
(very) small piece due to their provenance descriptions*. So when you
would like to query this complex description at once you may have to
include
Carsten,
On Wed, 2012-02-22 at 12:02 +0100, Carsten Keßler wrote:
[ . . . ]
The aspect we are currently working on is a metadata section that will
include classes and properties to state who has reported a certain
piece of information, when it was reported, whether it was approved
(and at
On 22/02/2012 18:18, Kingsley Idehen wrote:
On 2/22/12 12:30 PM, Barry Norton wrote:
On 22/02/2012 17:21, Bob Ferris wrote:
[...] Named Graphs unnecessary fragment complex descriptions into
(very) small piece due to their provenance descriptions*. So when
you would like to query this complex
On 2/22/12 1:58 PM, Barry Norton wrote:
On 22/02/2012 18:18, Kingsley Idehen wrote:
On 2/22/12 12:30 PM, Barry Norton wrote:
On 22/02/2012 17:21, Bob Ferris wrote:
[...] Named Graphs unnecessary fragment complex descriptions into
(very) small piece due to their provenance descriptions*. So
re: Languages urn:lang:xxx: or urn:lang:xx:
I'm not sure what the official UN Languages are. The US Library of Congress is
the maintainer of ISO 639 (1- 2alpha,2- 3 alpha,5- 3 alpha groups)). They have
an ID server which responds to URI's made from the Standard and the code. The
ISO 639-5
16 matches
Mail list logo
