Semantic Web Interest Group IRC Chat Logs for 2005-08-02

02:29:53 * DanC would like some nice creative commons music...

02:29:59 <DanC> hmm... maybe I'll try building monopod

02:30:41 <DanC> checking for mono >= 1.1.6... Package mono was not found

02:31:46 * DanC installs mono-devel and mono-gmcs

02:34:20 <DanC> still checking for mono >= 1.1.6... Package mono was not found

02:34:34 <DanC> Perhaps you should add the directory containing `mono.pc'

02:34:40 * DanC tries debian package search...

02:35:34 * DanC installs libmono-dev

02:35:56 <DanC> checking for gtk-sharp-2.0 >= 1.9.5... Package gtk-sharp-2.0 was not found

02:36:58 * DanC install gtk-sharp2

02:37:15 <DanC> ok, ./configure succeeded

02:37:31 <DanC> ./ChannelWindow.cs(144) error CS1501: No overload for method `SetSortFunc' takes `2' arguments

02:42:26 <DanC> sigh... C# doesn't seem to meet the unambiguity requirement either... so I guess I need to install an IDE to teach me how to find SetSortFunc

02:43:21 <DanC> Loading error, please reinstall :

02:43:21 <DanC> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not find file "/usr/lib/monodoc/monodoc.xml". : /usr/lib/monodoc/monodoc.xml

02:44:01 <DanC> usr/lib/monodoc/monodoc.xml devel/monodoc-manual

02:47:59 <DanC> hmm... I have ChannelWindow.cs open in monodevelop, but I don't see any clues about SetSortFunc

03:12:16 <DanC> $ monodoc

03:12:27 <DanC> cannot open assembly /usr/lib/monodoc/browser.exe

03:12:28 * DanC tries #mono ; nobody home

03:43:03 <DanC> aha! http://www.go-mono.com/docs/monodoc.ashx?link=T%3aGtk.ListStore

03:43:50 <DanC> Internal() warning CS8018: Could not find the symbol writer assembly (Mono.CSharp.Debugger.dll). This is normally an installation problem. Please make sure to compile and install the mcs/class/Mono.CSharp.Debugger directory.

03:44:49 * DanC got that when trying to build monopod-0.4

03:44:49 * DanC thinks it's time to declare defeat

04:13:51 <DanC> logger, pointer?

04:13:52 <DanC> See http://www.ilrt.bris.ac.uk/discovery/chatlogs/swig/2005-08-02#T04-13-51

04:24:31 <bijan> logger, antipointer?

04:24:33 <bijan> I'm logging. Sorry, searching removed.

04:24:44 <bijan> Ooh, too bad

04:25:03 <DanC>http://www.advogato.org/person/connolly/diary.html?start=32

04:25:07 <dc_swig> A: http://www.advogato.org/person/connolly/diary.html?start=32 from DanC

04:25:11 <DanC> A:|Adventures with Mono

04:25:11 <dc_swig> Titled item A.

04:25:30 <DanC> A:my struggles to build monodevelop; tonights episode ends in failure

04:25:30 <dc_swig> Added comment A1.

04:26:00 <DanC> A1:my struggles to build monopod; tonights episode ends in failure

04:26:00 <dc_swig> Replaced comment A1.

04:26:05 <DanC> A1:my struggles to build monopod; tonight's episode ends in failure

04:26:06 <dc_swig> Replaced comment A1.

04:26:07 <bijan> Shoudln't you try to "catch" mono? :)

04:26:38 <DanC> .0001 :)

04:27:39 <bijan> Is that a thousandth of a smiley or an obscure numeric pun with a smiley to help indicate that it's a joke?

04:31:04 <bijan>http://www.idealliance.org/papers/extreme03/html/2003/Lyons01/EML2003Lyons01.html

04:31:04 <dc_swig> B: http://www.idealliance.org/papers/extreme03/html/2003/Lyons01/EML2003Lyons01.html from bijan

04:31:13 <bijan> B:|Complexity of schema conformance

04:31:14 <dc_swig> Titled item B.

04:31:22 <bijan> B:I find it hard to believe I've not chumped this before.

04:31:23 <dc_swig> Added comment B1.

04:31:58 <DanC> that's a thousanth of a chuckle at your "catch" joke

04:32:09 <bijan> B: Before you waggle your finger at OWL DL, check out DTDs with fixed-value IDREFs! NP-hard.

04:32:09 <dc_swig> Added comment B2.

04:32:21 <bijan> Yes, I know

04:32:41 <bijan> I guess that's a -50 of a chuckle at the lame but subsequent ambiguity joke?

04:33:05 <bijan> B:XML Schema...Undecidable.

04:33:07 <dc_swig> Added comment B3.

04:35:34 <DanC> uh.. I guess so

04:37:07 <DanC> "MURATA Makoto offered a proof that the RELAX NG conformance problem is solvable in linear time"

04:37:15 <DanC> B:"MURATA Makoto offered a proof that the RELAX NG conformance problem is solvable in linear time"

04:37:16 <dc_swig> Added comment B4.

04:37:23 * DanC !

04:38:13 <DanC> B:" It turns out that the RELAX NG conformance problem is NP-hard3 when the schemas are allowed to use W3C XML Schema Datatypes"

04:38:14 <dc_swig> Added comment B5.

04:39:29 <DanC> B:" It turns out that the Schematron conformance problem is so difficult that it is undecidable." er... why is this a surprise? Schematron is turing-complete, no?

04:39:29 <dc_swig> Added comment B6.

04:40:31 <DanC> B:hmm... cites wikipedia, e.g. [Wikipedia06], without a date

04:40:32 <dc_swig> Added comment B7.

04:42:40 <DanC> B:aw... anti-climax... the result regarding XSD is in terms of key/reference stuff, and says little about the system of complex types

04:42:40 <dc_swig> Added comment B8.

07:31:39 <CLoCkWoRk> CLoCkWoRk is now known as CLoCkWeRX

07:34:21 <CLoCkWeRX>http://www.openbrr.org/

07:34:21 <dc_swig> C: http://www.openbrr.org/ from CLoCkWeRX

07:34:33 <CLoCkWeRX> C:| Open Business Readiness Rating

07:34:33 <dc_swig> Titled item C.

07:35:18 <CLoCkWeRX> C: Something I saw via /., a collab of a few people looking to assert quality ratings on open source software. Sounds suspiciously like DOAP is just what they are wanting

07:35:19 <dc_swig> Added comment C1.

07:36:34 <CLoCkWeRX> C: After making the suggestion [http://www.openbrr.org/index.php?option=com_forum&Itemid=0&page=viewtopic&t=14], they seemed keen: any DOAPers who feel up to selling people on RDF / etc, wander on over and drop them a line or two

07:36:34 <dc_swig> Added comment C2.

08:04:37 <ani|silence> ani|silence is now known as aniasis

08:06:48 <SunDevil> heu

08:13:27 <leasa> Some best prective questions

08:13:36 <leasa> best practice

08:15:37 <leasa> The best practice mechanism for referring to external taxonomies

08:16:32 <leasa> IS there one defined?

08:19:47 <SunDevil> i have no idea

08:27:20 <SunDevil> that pike as in /usr/bin/pike ?

08:38:59 <Jibbler2> Jibbler2 is now known as Jibbler

09:39:26 <raxor__> raxor__ is now known as raxor

11:01:25 <russell_> russell_ is now known as optika

11:21:04 * dajobe checks up on planet danbriayers

11:24:55 <jeen> :)

11:49:39 <danbri> dajobe, what needs to happen before we can get a feed from the chump? (A:->planetrdf,etc)

11:49:46 <danbri> into planetrdf i mean?

13:46:26 <d1223m> my distutils doesnt seem to understand .i files

13:46:36 <d1223m> sorry, first, hi

13:47:02 <d1223m> im not having much luck finding distutils swig docs

13:47:23 <balbinus> mmm

13:47:32 <d1223m> but iv seen a few snippets like Extension("something", ["something.i"])

13:47:33 <balbinus> #swig is Semantic Web Interest Group

13:47:37 <d1223m> doh

13:47:39 <d1223m> :)

13:47:45 <d1223m> iv done this before

13:47:52 <balbinus> :))

13:47:57 <d1223m> sorry

13:48:02 <balbinus> no prob

13:48:09 <d1223m> have fun

13:55:25 <DanC> libby, there seems to be an IETF CALSIFY meeting today. at 9am (in France?) http://lists.osafoundation.org/pipermail/ietf-calsify/2005-August/000696.html

13:56:09 <DanC> " - I've also been told that IANA doesn't have the ability to do a

13:56:09 <DanC> registry with the features

13:56:09 <DanC> specified in this document."

13:57:40 <libby> oh I didn;t realize it was in france

13:57:46 <libby> I saw it going by

13:58:35 <libby> teefal! long time no see

13:58:49 <teefal> hey libby

13:59:04 <teefal> yep, been undercover for a while

13:59:18 <teefal> how's things across the water?

13:59:43 <libby> not bad...I moved job

13:59:57 <teefal> i see iswc is in galway in november

14:00:05 <teefal> missed both japan trips

14:00:30 <teefal> www in edinburgh too ... looks like this is UK year

14:01:08 <teefal> (or island group that includes ireland and UK :)

14:01:25 <DanC> 9am tuesday in france already happened, right?

14:01:53 <libby> yeah

14:04:55 <DanC> seems WG was created 28 July. http://lists.osafoundation.org/pipermail/ietf-calsify/2005-July/000689.html

14:06:07 <libby> missed that

14:09:34 <teefal> i'm trying to put name to nick ... is leo sauermann on irc?

16:54:07 <libby> he was teefal

16:54:53 <raxor__> raxor__ is now known as raxor

17:03:36 <danbri> DanC, I'm looking to cite an old almost-note of yours... is:

17:03:38 <danbri> <dt>[<a id="ref-Connolly96" name="ref-Connolly96"]</dt>

17:03:40 <danbri> <dd><a href="http://www.w3.org/Architecture/NOTE-link.html">Describing and Linking Web Resources</a>, <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a> (editor), Unpublished W3C Note Draft (November 1996). Available at: http://www.w3.org/Architecture/NOTE-link.html</dd>

17:03:46 <danbri> ...an OK citation form?

17:04:04 <danbri> (for a TR, where in-face URIs seem to get used this way)

17:04:25 * danbri looked at another SWBPD Note, and at Dave's recent SPARQL results spec

17:04:58 <dajobe>http://www.w3.org/TR/2005/WD-rdf-sparql-XMLres-20050801/

17:04:59 <dc_swig> D: http://www.w3.org/TR/2005/WD-rdf-sparql-XMLres-20050801/ from dajobe

17:05:08 <dajobe> D:|SPARQL Query Results XML Format - W3C Working Draft 1 August 2005

17:05:09 <dc_swig> Titled item D.

17:05:13 <dajobe> D:where rdf and xml meet. again.

17:05:14 <dc_swig> Added comment D1.

17:05:47 <dajobe> D:this time with normative relaxng and xml schemas plus xquery and xslt examples

17:05:48 <dc_swig> Added comment D2.

17:10:09 <DanC> hmm... s/Unpublished W3C Note Draft/work in progress/ , danbri

17:10:30 <DanC> actually, that later got published, I think...

17:11:23 <danbri> I don't see it in /TR/

17:11:33 <danbri> but some old stuff wasn't in TR/ I guess

17:11:51 <DanC> no I'm confusing it with something else

17:13:32 <DanC> 1996. interesting cast of characters. where are you citing it, danbri?

17:15:32 <danbri> SWBPD WG Note-to-be that wraps my RDFS for HTML link types

17:16:32 <danbri> what-i-made-today c/o http://www.w3.org/2005/05/hrel/

17:16:38 * danbri still fiddlign with it

17:18:00 <danbri> scope section doesn't capture anything of why this might be worthwhile

17:25:08 <DanC> er... Namespace URI: http://www.w3.org/2002/06/xhtml2/ ? no #?

17:25:29 <DanC> 404 @ http://www.w3.org/2002/06/xhtml2/meta

17:25:30 <danbri> Steven in swbp telecon earlier "we used / 'cos we thought it'd make things more flexible re rdf'

17:25:54 <danbri> where's /meta come from?

17:26:01 <danbri> they're ok with idea of a redirect

17:26:19 <danbri> discussing whether the redirected-thing could then be content negotiated

17:26:23 <danbri> for rdf/a vs rdf/xml

17:26:33 <DanC> "propfile"? typo for profile?

17:26:55 <danbri> ouch

17:27:01 <danbri> thought i'd cut/pasted cleanly

17:27:09 <danbri> yup, tpyo

17:27:15 <danbri> thx

17:27:53 <DanC> hmm... I assumed rdf:ID="meta" + http://www.w3.org/2002/06/xhtml2/ = http://www.w3.org/2002/06/xhtml2/meta ... but now I see rdf:about"#meta

17:28:06 <DanC> sic. missing =

17:28:15 <DanC> are you typing this RDF/OWL by hand??!?

17:28:56 <danbri> the goal is to get it out there in a form we can say "Dear HTML WG, pls add a few markers so we can XSLT this from the XHTML2 spec

17:28:58 <danbri> "

17:29:12 <danbri> at time i 1st did it, was working from their unpublished WG docs

17:30:01 <danbri> it's the <dl> in http://www.w3.org/TR/2005/WD-xhtml2-20050527/mod-metaAttributes.html#s_metaAttributesmodule

17:30:18 <DanC> "This document has no formal standing within W3C." contradicts the sentence before it

17:31:57 <DanC> "For an RDF vocabulary such as this to be used in actual RDF data, it needs to be associated with a namespace URI." strictly speaking, not so. you just need a URI for each term.

17:32:48 <DanC> goodness... the list of open issues is enough to scare anybody away.

17:32:50 <danbri> re 'formal', that's from http://www.w3.org/2005/03/28-editor-style.html

17:33:01 <danbri> i could comment 'em out ;)

17:33:24 <danbri> they could perhaps be rationalised; wnated to get them in 1 place first.

17:34:20 <DanC> the concept of #Document doesn't seem like "minimal innovation"

17:34:53 <danbri> For an RDF vocabulary such as this to be used in actual RDF data,

17:34:55 <danbri> the terms it defines need to be associated with URIs. This is typically accomplished by associating the vocabulary with a <em>namespace URI</em>.

17:35:25 <danbri> Document; we talked with Steven about this, and agree that TAG's notion of 'information resource' is what we both mean...

17:35:44 <DanC> pity the TAG hasn't chosen a URI for the class InformationResource

17:35:58 <danbri> I agree <!-- this is the most creative addition; most other text is from HTML spec --> re creativity

17:36:01 <danbri> it's the point of most discomfort

17:36:51 * DanC went to look to see whether "Document" is mentioned explicitly in the XHTML2 spec... notes the irony of no XHTML2 ref in the bib section

17:37:24 <danbri> that's what I'm doing now, harvesting citations from other specs... haven't found one that cites XHTML2 yet :/

17:37:29 <DanC> it really seems awakward to do this outside the HTML WG. it's borderline squatting.

17:37:50 <DanC> you've seen the bibliography generator, no?

17:38:05 * danbri shares that feeling, but on Steven's advice, it's a SWBP thing

17:38:10 <DanC> . http://www.w3.org/2002/01/tr-automation/tr-biblio-ui

17:38:43 <danbri> oh cool. i think if i'd seen it, i'd forgotten it.

17:56:40 * danbri wonders whether s/Document/InformationResource/ would remove sense of inventing new stuff

18:11:40 <bjoern_> "@@FIXME@@ At publication time replace http://www.w3.org/2001/sw/DataAccess/rf1/result2.xsd and references to result2.xsd in the linked files to the final publication location under /TR/." -- http://www.w3.org/TR/2005/WD-rdf-sparql-XMLres-20050801/

18:14:01 <DanC> pretend you didn't see that for an hour or so, bjoern_ ?

18:14:36 <bjoern_> sure

18:47:34 <balbinus_> balbinus_ is now known as balbinus

19:01:48 <chris2> is there a faster/more efficient tool to convert rdf/xml to ntriples than cwm?

19:01:59 <danbri> DanC, is a literal string an 'information resource' in TAG's sense?

19:02:14 <danbri> redland/rapper is pretty fast

19:02:18 <chris2> hmm

19:02:50 <danbri> rapper -o ntriples linktypes.rdf

19:02:55 <danbri> ...works for me

19:02:57 <chris2> thx

19:08:55 <chris2> small at least :)

19:15:25 <DanC> prolly, danbri

19:16:21 <danbri> hmm, i just s/Document/InformationResource/

19:16:29 <danbri> i can't decide this stuff

19:16:31 * danbri mailing wg

19:29:28 <chris2> rapper is wonderful :)

19:53:17 <CaptSolo> hi all

19:53:44 <CaptSolo> is dajobe here?

20:33:53 <chrismurf> It seems like RDF has been adopted as a metadata storage format within a number of other formats - examples include inside JPEG EXIF data, and information within SVG

20:34:09 <rich_holygoat> and Adobe use it for XMP.

20:34:15 <chrismurf> yes

20:34:22 <chrismurf> has anything been done wrt. appropriate ways of storing data within RDF

20:34:35 <chrismurf> that doesn't fit the RDF model.

20:34:45 <rich_holygoat> data: URIs are one possibility

20:34:48 <chrismurf> for instance large scientific data sets

20:34:51 <danbri> sometimes you'll see data: uris, yup

20:35:14 <rich_holygoat> but it's using a hammer to chop firewood if you try to store a big JPEG as some RDF encoding.

20:35:19 <danbri> and you can include non-RDF XML markup inside using XML literals

20:35:30 <danbri> RDF tends towards being annotational and out-of-band though

20:35:40 <chrismurf> right

20:35:51 <chrismurf> one benefit of doing it the other way around though

20:36:02 <chrismurf> would be you would understand the metadata, and could ignore the data.

20:36:08 <chrismurf> right now, you have to parse the data to get to the metadata.

20:36:13 <rich_holygoat> if you have unique identifiers within your dataset -- such as LSIDs -- then you can make RDF annotations of them.

20:36:38 <chrismurf> data: URI's are just a standard way of doing that I assume?

20:36:41 <rich_holygoat> but if you store the whole dataset in RDF you're going to get it swelling up quite quickly.

20:36:52 <chrismurf> of course.

20:37:05 <rich_holygoat> data: URIs are ways of encoding small chunks of data -- e.g. PNGs -- as a URI string

20:37:08 <rich_holygoat> rather than as a file.

20:37:15 <chrismurf> oh - wow. okay.

20:37:24 <chrismurf> like, base64 encoded or whatever

20:37:33 <rich_holygoat> I'll dig up a ref.

20:38:04 <rich_holygoat> this is a form to make them: http://infomesh.net/2001/03/dataencode/

20:38:31 <chrismurf> thanks

20:38:41 <rich_holygoat> this is the RFC: http://www.faqs.org/rfcs/rfc2397.html

20:39:01 * rich_holygoat shrugs

20:40:33 <chrismurf> sorry about that - gnome spontaneously combusted.

20:40:56 <chrismurf> thanks for the link

20:43:06 <rich_holygoat> no worries.

20:43:20 <rich_holygoat> there is a size limitation on data: URIs, which is why you can't use them for storing scientific data.

20:43:29 <rich_holygoat> but small chunks will be fine.

20:43:34 <rich_holygoat> text you can store in literals.

20:43:41 <rich_holygoat> XML you can store in XML literals.

20:43:46 <chrismurf> no - I'm talking large data sets.

20:44:19 <rich_holygoat> binary?

20:44:26 <chrismurf> not necessarily

20:44:32 <chrismurf> typically ascii

20:44:45 <chrismurf> positioning information from a variety of sensors

20:44:53 <rich_holygoat> does it lend itself well to a graph representation?

20:44:53 <chrismurf> roundtrip times to beacons

20:44:55 <chrismurf> that sort of thing

20:45:06 <chrismurf> there's a lot of it, and it's time-series

20:45:12 <chrismurf> so I would lean towards no.

20:45:16 <rich_holygoat> it's unlikely to be a good match, then.

20:45:31 <rich_holygoat> but if you can identify persistent identifiers, you can annotate with RDF.

20:45:34 <chrismurf> I was trying to be clever and mix the metadata about the dataset

20:45:38 <chrismurf> with the data

20:45:46 <chrismurf> 'clever'

20:45:52 <rich_holygoat> :)

20:46:02 <rich_holygoat> best not to do so.

20:46:15 <rich_holygoat> (at least, that's my recommendation from what i can see)

20:46:21 <chrismurf> fair enough

20:46:35 <chrismurf> so just store the data as tab delimited ascii or whatever

20:46:52 <chrismurf> and have an rdf file pointing at identifiers for each

20:46:58 <chrismurf> er -

20:47:12 <rich_holygoat> sounds reasonable. I mean, you _could_ translate it into RDF, but it doesn't sound like you're likely to get utility from an RDF representation.

20:47:12 <chrismurf> have identifiers for each file that I can make rdf statements about.

20:47:28 <rich_holygoat> either annotate the files, or annotate the beacons/sensors

20:47:31 <chrismurf> no - it was more from a 'keeping it all in one place' standpoint

20:47:40 <chrismurf> fair point

20:47:57 <chrismurf> the beacons and such could have uri's.

20:48:01 <rich_holygoat> if it's ASCII, you could of course store it as literals in the store, so it would all be in one place -- but it's cheating :D

20:48:10 <chrismurf> yuck :-P

20:48:24 <chrismurf> ok - thanks - that gives me some stuff to think about

20:48:28 <rich_holygoat> no probs.

20:51:05 <d2m_> d2m_ is now known as d2m

20:56:25 <danbri> logger, pointer

20:56:25 <danbri> See http://www.ilrt.bris.ac.uk/discovery/chatlogs/swig/2005-08-02#T20-56-25

21:04:01 <ronwalf> Hum. Of the 19K tags in my sparql result document, 13K are from unbound variables

21:06:14 <danbri>http://www.w3.org/2005/05/hrel/

21:06:14 <dc_swig> E: http://www.w3.org/2005/05/hrel/ from danbri

21:06:46 <danbri> E:|"XHTML link types in RDF", a work-in-progress within the RDF-in-XHTML taskforce

21:06:46 <dc_swig> Titled item E.

21:07:31 <danbri> E:I've just sent this to the SWBPD WG and RDF-in-XHTML TF lists, so may as well share here also. Feedback welcomed (particularly from those who actually _use_ these link types in HTML).

21:07:31 <dc_swig> Added comment E1.

21:08:01 <danbri> E:"This document describes an RDF representation of XHTML 2.0's built-in link types. It is based on the Metainformation Attributes Module of XHTML2, and uses W3C's RDF Schema and Web Ontology languages to describe several kinds of relationship that can hold between information resources."

21:08:02 <dc_swig> Added comment E2.

21:09:21 <danbri> E:It's still a little rough; wrote it all this afternoon (the RDF design itself was done a couple months back). See also [http://www.w3.org/2005/05/hrel/linktypes.rdf|linktypes.rdf] the raw RDFS/OWL document.

21:09:21 <dc_swig> Added comment E3.

21:10:50 <danbri> (not to self, only search for 'owl pellet' if you're looking for bird crap)

21:11:02 <danbri> eg. http://www.scienceman.com/pgs/archive21_owlpellet.html (thx, mindswap ;)

21:12:16 <danbri> E:Pellet claims the vocab is in [http://www.mindswap.org/cgi-bin/2003/pellet/pelletGet.cgi?inputFile=http%3A%2F%2Fprotege.stanford.edu%2Fplugins%2Fowl%2Fowl-library%2Fcamera.owl&inputFormat=RDF%2FXML&inputString=&classifyFormat=NONE&queryFile=&queryString=|OWL DL], which is new territory for me. Note the extra rdf:type stuff in the schema; am trying to be non-OWL RDF friendly too. Did it work?

21:12:16 <dc_swig> Added comment E4.

21:12:35 <danbri> oh, i take that back, i validated wrong url :)

21:13:00 <danbri> (it was DL when I checked previously tho)

21:13:51 <danbri> Input file: http://www.w3.org/2005/05/hrel/linktypes.rdf

21:13:53 <danbri> OWL Species: Lite

21:13:55 <danbri> DL Expressivity: ALI

21:13:56 <danbri> Time: 1344 ms (Loading: 1169 Species Validation: 175 )

21:15:05 <danbri> E4:Pellet claims the vocab is [http://www.mindswap.org/cgi-bin/2003/pellet/pelletGet.cgi?inputFile=http%3A%2F%2Fwww.w3.org%2F2005%2F05%2Fhrel%2Flinktypes.rdf&inputFormat=RDF%2FXML&inputString=&classifyFormat=NONE&queryFile=&queryString=|OWL Lite], which is new territory for me. It hardly uses any OWL, really; but being able to represent the inverses is handy. Note the extra rdf:type stuff in...

21:15:12 <dc_swig> Replaced comment E4.

21:15:12 <danbri> ...the schema; am trying to be non-OWL RDF friendly too. Did it work?

21:16:33 <danbri> E:Nearby: [http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2005Aug/|taskforce mailing list]

21:16:33 <dc_swig> Added comment E5.

21:16:50 <ronwalf> oh, bad validator

21:17:09 <ronwalf> I don't think it would have ever thought you'd go and make literal types

21:18:12 <danbri> hmm that link worked in my browser, must've transferred it wrong

21:18:37 <danbri> oh i see, the results confused me

21:18:49 <danbri> did it work earlier or not, i'm not sure. looks now like an error but it continues anyway...

21:19:26 <danbri> nope it's fine. chatzilla got the hyperlink wrong in my chat window. ignore me :)

21:20:35 <danbri> so, do you think it's OWL Lite? missing the issue re literal types

21:20:49 <danbri> the rdf:type="http://www.w3.org/2002/07/owl#ObjectProperty" notation is specialcased in rdf/xml as i understand it

21:20:58 <danbri> ie they're resources not literals

21:21:27 <ronwalf> Oh, huh

21:21:35 <ronwalf> Yay for complete inconsistency

21:25:34 <ronwalf> On just a cursory glance, it looks like it's in owl Lite

21:26:00 * ronwalf retracts his dumb bug report to pellet

21:31:13 <ronwalf> danbri: Both pellet and owlapi don't complain. The only one left to test is Jena...

21:32:00 <danbri> do you have the ability to do that handy?

21:32:12 * danbri didn't know jena could classify into dl/lite/full

21:40:24 <schepers> schepers is now known as vb

21:40:43 <vb> vb is now known as schepers

21:40:59 <raxor> raxor is now known as vb

21:41:19 <vb> vb is now known as raxor

21:41:22 <schepers> schepers is now known as schepers_

21:41:29 <schepers_> schepers_ is now known as schepers

22:54:51 <ronwalf> danbri: I don't have any webservice I can point to (or code in my pocket, for that matter)

22:55:00 <ronwalf> I just know it exists

23:20:51 <danbri> ok, thanks