IRC log of dig on 2010-12-04
Timestamps are in UTC.
- 00:50:21 [oshani]
- oshani has quit (Quit: Mama nidi!)
- 01:58:02 [samuelsw]
- samuelsw has quit (Quit: samuelsw)
- 02:07:08 [melvster]
- melvster has quit (Ping timeout: 250 seconds)
- 04:01:01 [lkagal]
- lkagal has quit (Quit: lkagal)
- 04:11:01 [lkagal]
- lkagal (~lkagal@pool-96-237-240-136.bstnma.fios.verizon.net) has joined #dig
- 04:14:04 [fuming]
- fuming (~fuming@18.111.101.98) has joined #dig
- 05:22:19 [fuming]
- fuming has quit (Quit: fuming)
- 05:23:36 [lkagal]
- lkagal has quit (Quit: lkagal)
- 05:57:37 [melvster]
- melvster (~melvster@p579F9431.dip.t-dialin.net) has joined #dig
- 07:35:29 [melvster]
- melvster has quit (Ping timeout: 240 seconds)
- 09:17:01 [mhausenblas]
- mhausenblas (~mhausenbl@wg1-nat.fwgal01.deri.ie) has joined #dig
- 10:14:04 [mhausenblas_]
- mhausenblas_ (~mhausenbl@wlan-nat.fwgal01.deri.ie) has joined #dig
- 10:17:23 [mhausenblas]
- mhausenblas has quit (Ping timeout: 255 seconds)
- 10:17:23 [mhausenblas_]
- mhausenblas_ is now known as mhausenblas
- 13:26:11 [timbl]
- timbl (~timbl@pool-96-237-236-230.bstnma.fios.verizon.net) has joined #dig
- 13:57:03 [danbri]
- danbri has quit (Remote host closed the connection)
- 13:57:28 [danbri]
- danbri (~danbri@ip176-48-210-87.adsl2.static.versatel.nl) has joined #dig
- 14:08:13 [fuming]
- fuming (~fuming@18.111.101.98) has joined #dig
- 14:20:25 [timbl]
- timbl has quit (Quit: timbl)
- 14:38:03 [fuming]
- fuming has quit (Quit: fuming)
- 15:32:29 [melvster]
- melvster (~melvster@p5797F40D.dip.t-dialin.net) has joined #dig
- 16:14:17 [lkagal]
- lkagal (~lkagal@pool-96-237-240-136.bstnma.fios.verizon.net) has joined #dig
- 16:29:24 [scor]
- scor (~scor@drupal.org/user/52142/view) has joined #dig
- 16:43:57 [fuming]
- fuming (~fuming@18.111.101.98) has joined #dig
- 16:51:03 [timbl]
- timbl (~timbl@pool-96-237-236-230.bstnma.fios.verizon.net) has joined #dig
- 16:51:30 [fuming]
- fuming has quit (Quit: fuming)
- 16:54:55 [webr3]
- timbl, there's one note I can't read, on "Note: IRIs are compatible with RDF URI references as defined by RDF Concepts" - you circled "compatible" in that sentence and wrote "******** way?" - can you enlighten?
- 16:56:05 [scor]
- scor has quit (Quit: scor)
- 16:56:55 [timbl]
- There is a confusion in the document between an IRI, which is a string, and and RDF node which is named with the IRI.
- 16:57:19 [webr3]
- cool I'm changing that to Symbol in the draft atm
- 16:57:33 [webr3]
- also, if we go with a single Literal interface, then should it have two different attributes .lang and .datatype, or just one which can have a value of say "en" or "xsd:type" - or even "lang:en"/"xsd:type" (and if one, any proposals on the name for it?)
- 17:09:52 [timbl]
- timbl has quit (Quit: timbl)
- 17:10:48 [timbl]
- timbl (~timbl@pool-96-237-236-230.bstnma.fios.verizon.net) has joined #dig
- 17:10:48 [timbl]
- timbl has quit (Remote host closed the connection)
- 17:11:00 [timbl]
- timbl (~timbl@pool-96-237-236-230.bstnma.fios.verizon.net) has joined #dig
- 17:14:05 [timbl]
- In the cwm and tabulator it is known as symbol because danc pointed out IIRC that it is a symbol when you think of ttl as a langauge.
- 17:14:35 [timbl]
- Other people might prefer other things g course, but you can't confuse it with IRI.
- 17:15:04 [timbl]
- Oh, don't overlaod the land and dt on the same slot
- 17:15:52 [timbl]
- Very diff meanin -- and we might move to a place where thing s which have a language return a data type like plainLiterl or String.
- 17:17:23 [webr3]
- okay, thinking it may be wise to have a Literal interface which PlainLiteral and TypedLiteral both extend then, so that no node can have both a .lang and a .datatype
- 17:19:15 [webr3]
- ahh, missed your last comment, if we move to a place where things with a lang also have a datatype then they need to be on the same interface - follow now
- 17:34:40 [mhausenblas]
- mhausenblas has quit (Quit: brb)
- 17:50:33 [webr3]
- timbl, triple.property should be (NamedNode|BlankNode|Literal) or (NamedNode|BlankNode) - as in allow literal properties or constrain to only named/blank nodes?
- 17:54:52 [lkagal]
- lkagal has quit (Quit: lkagal)
- 18:12:15 [lkagal]
- lkagal (~lkagal@pool-96-237-240-136.bstnma.fios.verizon.net) has joined #dig
- 18:25:30 [ericP]
- webr3, i'd say that the current winds blow in the direction of being rigorous
- 18:26:27 [ericP]
- of an API, that's probably a good idea. it's always possible to liberalize the RDF model, but we probably don't want to nudge it with what would currently be user disappointment
- 18:26:47 [ericP]
- imo
- 18:49:40 [webr3]
- ty ericp :)
- 19:07:09 [timbl]
- webr3, on the other hand I would think the APi should be defined so as to be able to deal with a literal subject so that it doesn't have to be changed if/when the model is relaxed, which I'd expect the WG to d.
- 19:19:11 [ericP]
- heretic
- 19:19:52 [webr3]
- iirc there were some specific notes on the draft wg chater saying they won't be covering even literal subjects or blanknode properties, let alone literal properties
- 19:20:44 [webr3]
- however I'm happiest if the API doesn't have to change and is N3 compatible, it doesn't break bc in an way to have literal properties as blank/named nodes are still allowed
- 19:25:09 [webr3]
- "3. Out of Scope ... Removing current restrictions in the RDF model (e.g., literals not allowed as subjects, or blank nodes as predicates)" - from: http://www.w3.org/2010/09/rdf-wg-charter.html
- 19:31:11 [ericP]
- i think the most comfortable path for these sorts of revolution is if a few vendors decide to make their implementations symmetically liberal
- 19:31:41 [ericP]
- yes, that's the job of standards, but standards can't tell the world what to do, just define current practice
- 19:36:33 [webr3]
- I can see this is going to be an interesting conversation tomorrow, liberal for future and n3 compatibility vs constrained to current and previous specs
- 19:38:34 [ericP]
- it's an age-old coin-flip
- 19:53:21 [webr3]
- is tabulator's Formula.prototype.the() supposed to be an existential check, or supposed to confirm that there is only one match?
- 20:51:19 [fuming]
- fuming (~fuming@18.111.101.98) has joined #dig
- 21:34:42 [fuming]
- fuming has quit (Quit: fuming)
- 21:44:51 [timbl_]
- timbl_ (~timbl@pool-96-237-236-230.bstnma.fios.verizon.net) has joined #dig
- 21:48:10 [timbl]
- timbl has quit (Ping timeout: 245 seconds)
- 21:48:10 [timbl_]
- timbl_ is now known as timbl
- 22:33:50 [timbl]
- webr3, currently if there is >1 match that is an error not caught.
- 22:34:06 [timbl]
- So thowing an exception is optional.
- 23:22:46 [lkagal]
- lkagal has quit (Quit: lkagal)
- 23:28:38 [timbl]
- timbl has quit (Quit: timbl)
- 23:43:27 [kennyluck]
- kennyluck has quit (Ping timeout: 272 seconds)
- 23:51:19 [lkagal]
- lkagal (~lkagal@pool-96-237-240-136.bstnma.fios.verizon.net) has joined #dig