Available formats: content-negotiated html turtle (see SIOC for the vocabulary)
Back to channel and daily index: content-negotiated html turtle
These logs are provided as an experiment in indexing discussions using IRCHub.py, Irc2RDF.hs, and SIOC.
| 00:49:10 | <chimezie> | A:[http://python-dlp.googlecode.com/files/GALEN-CABG-Segment.txt|Example] rendering of a large extract from GALEN's GRAIL ontology (focused around coronary artery graft taxonomies) into OWL and serialized to Manchester OWL via InfixOwl |
| 00:49:36 | <chimezie> | http://python-dlp.googlecode.com/files/GALEN-CABG-Segment.txt |
| 00:50:12 | <chimezie> | A:|Large extract from GALEN ontology (focused around coronary artery anatomy) |
| 00:50:50 | <chimezie> | A:Extracted to OWL RDF/XML, parsed and serialized to Manchester OWL syntax (using InfixOwl) |
| 00:52:32 | <chimezie> | A:Extracted to OWL-DL RDF/XML using implementation of [http://www.co-ode.org/resources/papers/seidenberg-www2006.pdf|Web Ontology Segmentation: Analysis Segmentation and Use] |
| 00:55:37 | <ericP> | chimezie, if i have an RDF resource <http://langtest.example/日本語>, what is its string representation |
| 00:55:40 | <ericP> | ? |
| 00:56:15 | <ericP> | (picking on chimezie as he showed life while i was thinking about it) |
| 00:56:26 | <chimezie> | depends on (at least) if it is an IR, or a concept, I'd think |
| 00:56:36 | <chimezie> | i.e., httprange-14 |
| 00:57:38 | <ericP> | SPARQL ORDER BY sorts IRIs by the codepoint representation, by which we meant "http://langtest.example/日本語" |
| 00:57:53 | <ericP> | i'm trying to figure out how to write that down |
| 00:58:14 | <ericP> | current text: "IRIs are ordered by comparing their codepoint representations with the "<" operator." |
| 00:58:14 | <chimezie> | log:uri? |
| 00:58:56 | <ericP> | i think i need something more like what i would find in the documentation for log:uri |
| 00:59:43 | <ericP> | specs haven't gotten to a point where the definitions are in RDF, not even the SPARQL spec |
| 00:59:51 | <chimezie> | "This allows one to look at the actual string of the URI which identifies this. (Cwm can get the URI of a resource or get the resource from the URI.) This is a level breaker, breaking the rule of not looking inside a URI. Use (eg with string:match) to replace RDF's old "aboutEach" functionality. Use to implement the URI spec and protocol specs, etc." |
| 01:00:47 | <ericP> | "actual string" is the closest i see there |
| 01:01:06 | <ericP> | ACTION checks URI spec... |
| 01:01:07 | <chimezie> | rdf-concepts talks of "A URI reference or literal used as a node identifies what that node represents." |
| 01:02:07 | <ericP> | hmm, close-ish |
| 01:03:07 | <ericP> | ACTION poking through http://rfc.net/rfc3986.html |
| 01:03:15 | <chimezie> | re:specs and defs in RDF. I look forward to those days :) |
| 01:05:23 | <ericP> | whee! |
| 01:05:56 | <ericP> | i don't think they'd really *be* in RDF |
| 01:06:34 | <ericP> | they'd be in some type-checking modeling language, whose data structures could be encoded in RDF |
| 01:07:50 | <chimezie> | RIF? |
| 01:09:08 | <ericP> | string-compare(log:iri(A), log:iri(B)) |
| 01:10:13 | <ericP> | or [ :function [ :name less-than ; :parm0 :IRI ; parm1 :IRI ; comparitor [ ... funny RDF binary tree for "[ :function [ :name less-than ; :parm0 :IRI ; parm1 :IRI ; comparitor " ] ] ] |
| 01:10:27 | <ericP> | ]] |
| 12:35:18 | <scanf> | Hi. What does this mean? |
| 12:35:31 | <scanf> | error: `SWIG_Python_ConvertPtr' cannot be used as a function' |
| 12:35:44 | <scanf> | when build something for python from swig 1.3. I am getting A LOT of these errors scrolling down the screen... |
| 12:37:42 | <JibberJim> | wrong swig scanf :( |
| 12:37:57 | <JibberJim> | see the topic |
| 12:38:06 | <scanf> | what the... |
| 12:38:23 | <scanf> | AFAIK there's only one :) |
| 12:38:26 | <scanf> | orry |
| 12:38:29 | <scanf> | sorry |
| 12:39:06 | <scanf> | ...you probably get a few folks in here looking for the wrap generator |
Back to channel and daily index: content-negotiated html turtle