This is a public chat log generated from the #semsol IRC channel.
05:43:12
Hi All..
05:44:37
i am trying to subscribe to the mailing list of arc at arc-dev@semsol.org
05:45:07
but i didnt got any confirmation and also not able to see my mail in the public archieve on the website
05:45:21
any issues with it
05:45:23
?
06:50:00
did you check your spam folder?
07:22:28
well, that one got through
09:06:45
i got my subscription going at the 3rd subscribe mail
09:06:46
thanks
09:13:24
I'll have a look, kunal
09:14:08
bengee just returned from day off, it may take some time until I get there
09:16:54
hey bengee
09:18:35
heya
09:44:19
kunal, do you know which ARC revision you are using? There should be no triple_back table any more
09:44:38
triple_back*up*
09:56:23
but I get errors, too. I'll track this one down
09:59:44
ah, it's the literal subject
09:59:56
and the literal predicates
10:46:25
hey bengee.. i took arc version, a month and a half back
10:47:38
so to restrict the subjects and predicts to literals, y this a constraint from the arc side
10:48:05
semantically i can put literals there and retrieve them
10:48:21
if my store doesnt face any conflict
10:48:22
it's an rdf thing
10:48:52
i was using the drupal rdf module, i was able to achieve literals there
10:49:11
even the parsing done by arc parser was not reporting any errors
10:49:12
yeah, but then it's more flexible then usual rdf systems
10:49:34
okies....
10:49:54
sparql allows literal s/p/o, but rdf/xml or turtle don't
10:50:31
I think n3 even allows blank predicates
10:50:38
yaa
10:50:49
but turtle allows it
10:51:04
i am parsing the turtle with literals using arc parsers
10:51:29
they dont make the literals to uri as they do it for rdf+xml
10:52:25
one more thing where i can find the map for o_type and s_type columns in _triple table
10:52:43
yeah, that's because ARC's Turtle parser is derived from the SPARQl grammar
10:52:55
hmmm....
10:53:15
ARC's turtle parser will allow ?var, too
10:53:44
okiess.....
10:53:46
but it's invalid turtle
10:53:50
yaaa
10:55:09
I was wondering about allowing literals anywhere in the store, but that would have made the value mapings more complicated
10:56:02
re s_type/o_type: 0 = uri / 1 = bnode / 2 = literal
10:56:50
okie... but although we still have the value mapping here
10:57:23
cannt these be used .. say 2 when subject is a literal
10:57:45
and the _s2val can have the liteal value
10:59:16
not as easily as it seems
10:59:28
yaa i can understand...
10:59:46
i saw your trice project briefing
11:00:06
when u plan to release it.. it seems very interesting stuff
11:00:51
trice should have been out already, I'm pretty late there
11:01:54
it would be very nice as we are trying to do some semantic stuff using drupal and contributed modules
11:02:11
ah, cool
11:02:33
thanks for your time bengee....
11:02:48
there'll be some code soon that bundles Trice, e.g. knowee
11:03:08
once that's out, I'll set up a site and stuff
11:03:09
thats cool
11:03:22
will be eagerly waiting for it
11:03:26
:)
11:03:46
thanks for your time ... i will bug u again when i am stuck :)
11:03:56
yeah, np
11:04:32
catch you...
14:11:48
hey bengee - just a thought, what about allowing something like LOAD ?link WHERE { ?s ?p ?link . FILTER(isURI(?link)) OPTIONAL( ?link ?p2 ?o2 ) FILTER(!bound(?o2)) } ?
14:12:16
nah, actually, overkill
14:12:20
nm
14:13:22
I guess SPARQLScript will enable use cases like this
14:13:39
yeah
14:13:51
what's sparqlscript?
14:13:56
sparqlscript++
14:13:58
the bot brain language?
14:14:37
something I'm trying to generalise. initiated by bot stuff, yeah
14:15:13
bengee did a wiki page somewhere
14:15:16
http://esw.w3.org/topic/SPARQL/Extensions/SPARQLScript
14:15:22
thassawun