Semantic Web Interest Group IRC Chat Logs for 2005-01-19

This is an automatically generated IRC chat log made by the logger bot from the Semantic Web Interest Group IRC chat at irc://irc.freenode.net/swig (also known as server irc.freenode.net channel #swig if that URI does not work for you).

See also the Semantic Web Interest Group IRC Scratchpad for the collaboratively written weblog and ESW wiki.


Semantic Web Interest Group Logs > 2005 > 2005-01 > 2005-01-19 (Latest) (Search)

01:00:15 <eaon> has there any commenting work been done besides annotea?

01:12:43 <MarkB> crit comes to mind ...

01:13:22 <MarkB> hey, it's back!

01:13:28 <MarkB>http://crit.org/

01:13:28 <dc_swig> A: http://crit.org/ from MarkB

01:13:50 <MarkB> A:|Critlink/CritSuite - it's back!

01:13:51 <dc_swig> Titled item A.

01:21:01 <eaon> thanks

01:46:53 <danbri>http://www.elmundo.es/encuentros/invitados/2005/01/1400/index.html

01:46:54 <dc_swig> B: http://www.elmundo.es/encuentros/invitados/2005/01/1400/index.html from danbri

01:47:20 <danbri> B:|timbl q+a, lang="es"

01:47:22 <dc_swig> Titled item B.

01:47:30 <danbri> filmtrust, haven't had a good look yet

01:47:33 <danbri> sounds worthy though

01:47:55 <danbri> (what does it do for film IDs and actor IDs I wonder...)

02:35:27 <crschmidt> danbri: It doesn't do anything with actors.

02:42:20 <md-afk_> md-afk_ is now known as PhUrl

03:54:13 <PhUrl> PhUrl is now known as md-zzz

08:04:17 <[GNU]> moin

11:18:37 <md-zzz> md-zzz is now known as PhUrl

11:19:38 <PhUrl> moin moin [GNU]

11:45:45 <IsoosI> x/join #foaf

11:45:46 <IsoosI> doh

11:47:26 <IsoosI> I have a webpage that I want to return an rdf document if the query is successful

11:47:35 <IsoosI> but if it fails I want to signal the failure

11:47:44 <IsoosI> is there a way I can say in rdf "your query failed"?

11:48:01 <IsoosI> or do I have to return one of the http error codes?

11:48:02 <crschmidt> IsoosI: probably best to use HTTP error codes of some kind

11:48:14 <IsoosI> hrm

11:48:36 <crschmidt> http://www.w3.org/TR/2005/WD-rdf-sparql-protocol-20050114/#http might be a good starting point?

11:48:36 <dc_swig> C: http://www.w3.org/TR/2005/WD-rdf-sparql-protocol-20050114/#http from crschmidt

11:48:46 <crschmidt> C:| Sparql Protocol Draft

11:48:46 <dc_swig> Titled item C.

11:48:57 <crschmidt> I'm guessing you're not using sparql or anything like it

11:49:04 <crschmidt> but the error codes seem sensible to me

11:49:57 <IsoosI> hrm

11:50:04 <IsoosI> what I'm doing is yet-another SSO

11:50:27 <IsoosI> sitea asks auth1 to authenticate the user

11:50:36 <IsoosI> auth1 gives sitea a ticket back

11:50:43 <IsoosI> sitea then uses auth1 to verify the ticket

11:50:52 <IsoosI> at the moment it returns "SUCCESS" or "FAILURE"

11:51:10 <IsoosI> but it seems to me that it would be sane if it returned a FOAF style document about the user that it authenticated

11:51:28 <IsoosI> giving their name etc

11:51:41 <IsoosI> but if the ticket is invalid I have to do something

11:52:51 <IsoosI> on the flipside

11:52:57 <IsoosI> sparql looks very cool

11:56:08 <IsoosI> are there sparql bindings to anything else?

11:56:40 <crschmidt> Don't know, the draft was only a few days ago

11:56:50 <crschmidt> .g DawgShows

11:56:53 <phenny> DawgShows: http://esw.w3.org/topic/DawgShows

11:56:56 <crschmidt> might check there

12:02:00 <IsoosI> hrm

12:02:01 <IsoosI> interesting

12:13:11 <PhUrl> News: Semantic web is going to help the US intelligence : "In addition, the advent of the Semantic Web (which adds definition tags to information in Web pages so that computers can interact more productively) will further empower end users of information and make the Web a much more efficient tool." http://www.technologyreview.com/articles/05/02/issue/megaphone.asp

12:13:46 <PhUrl> further quote : "If the government stopped spending billions producing what was already available for free or at low cost on the Web, then it could devote more money to the new technologies that will truly transform intelligence."

12:13:57 <PhUrl> yeah, give me the money....

12:13:59 <PhUrl> :)

12:25:47 * bijan imagines some proposals...

12:25:59 <bijan> "XML2! It's XML, only it cost you another 2 million!"

12:26:32 <bijan> "RDFMicroCore: Just subjects! Cost overruns killed predicates and object always seemed like a bad idea"

12:29:50 <[GNU]> furl!

12:53:54 <PhUrl> bijan: lol

12:54:42 <PhUrl> [GNU]: good one, f=ph

12:57:02 <[GNU]> furl: ne.. i am sure you know that we had a rechtschreibreform in germany and tried to remove all "ph" :)

12:57:45 <PhUrl> hehehe

13:33:05 <sh1mmer> sometimes I think I have the devil's own luck :)

13:34:18 <[GNU]> that means to be the luckies man in the world?

13:34:36 <sh1mmer> er.. possibly.

13:34:46 <sh1mmer> I visited the book shop just because I was passing

13:34:59 <sh1mmer> and I ended up leaving with £330 worth of books for £20

13:37:21 <[GNU]> ahm... that belongs in the category lucky bastard is guess

13:40:06 <sh1mmer> yeah, especially because I was only going to buy 4 at 50% off and then the lady said it was 5 for £5, which is a lot cheaper!

13:41:04 <[GNU]> hmm... maybe she get fired on monday and is doing a good job for the last final days?!

13:41:05 * bijan establishes a hatred regimen for sh1mmer

13:41:14 * bijan has not gotten lucky on book buys for a while

13:43:56 <sh1mmer> I did buy some weird stuff though

13:44:07 <sh1mmer> I got a bulgarian cookbook which is the last thing I was expecting to buy today

13:44:21 <[GNU]> :)

13:44:29 <[GNU]> is it english text?

13:44:34 <sh1mmer> yes

13:44:39 <bijan> Ooooo

13:44:40 <bijan> sexy

13:44:45 <[GNU]> definitly

13:44:59 <sh1mmer> I love my cooking so I am happy, but I wouldn't have paid £20 for it

13:45:09 * bijan ups the hatredenvy-o-meter on sh1mmer to "Bulgarian"

13:45:14 <sh1mmer> lol

13:45:28 <[GNU]> .wn hatredenvy

13:45:31 <sh1mmer> oh that reminds me

13:45:43 <[GNU]> .w hatredenvy

13:45:44 <[GNU]> :/

13:45:48 <sh1mmer> is anyone from Galway around?

13:45:49 <phenny> I couldn't find hatredenvy in WordNet.

13:46:03 <[GNU]> hmm

13:46:08 <bijan> Er...it's a fused word

13:46:11 <bijan> Coined right now

13:46:15 <sh1mmer> .w antidisestablishmentarianism

13:46:22 <phenny> I couldn't find antidisestablishmentarianism in WordNet.

13:46:23 <bijan> .w wanker

13:46:33 <phenny> wanker 1. terms of abuse for a masturbator

13:46:33 <[GNU]> ah

13:46:49 <sh1mmer> well I supose that is technically acurate.

13:47:05 <bijan> But not just *ANY* masturbator, phenny! There are distinctions to be drawn!

13:47:29 * bijan suspects that it's time to terminate this line...

13:47:44 <sh1mmer> Actually, I would suggest that it is not a term of abuse for masturbators more a term of abuse insinuating the person is a masturbator

13:48:01 <bijan> Hardly insinuating :)

13:48:22 * sh1mmer wonders what spy cams bijan has

13:48:31 * sh1mmer runs off to check his bedroom

13:48:32 <bijan> Er...none :)

13:48:47 <sh1mmer> pfff... you would say that!

13:49:04 <sh1mmer> So who is going to the techincal plenary?

13:49:05 * bijan prefers holes in the walls...spying and drug adminstration either airbourne or dart deleivered

13:49:15 <bijan> Plus, poking

13:49:16 <bijan> moi

13:49:32 <sh1mmer> poking avec le stick or poking avec le zee zee

13:49:32 <sh1mmer> ?

13:49:38 <bijan> Er...

13:49:43 * bijan not touching that one

13:49:52 <bijan> But I have a knitting needle around here somewhere

13:50:12 <sh1mmer> men doing crochet, very post modern.

13:50:28 <bijan> knitting ~= cochet!

13:50:32 <bijan> crochet :)

13:50:46 <sh1mmer> I'm dyslexic, I let people who care spell.

13:50:50 <sh1mmer> bijan do you know if Jen has had any news from her job application?

13:51:20 <bijan> No

13:51:29 <bijan> I feel certain I would have heard :)

13:51:33 <bijan> Seems a tad early

13:51:45 <sh1mmer> I don't know how long these things take

13:51:50 <bijan> A while

13:51:51 <bijan> :)

13:51:52 <sh1mmer> I have never applied to become a member of a faculty

13:51:58 <bijan> A long while

13:52:03 <sh1mmer> what about PhD apps?

13:52:49 <bijan> At least in philosophy, there's a vetting, then perhaps an interview at the APA, then an on campus (for as many as 10 people! so multiple weeks), then deliberation, then drafting an offer letter...

13:52:54 <bijan> It's a many month long process

13:53:07 <bijan> You mean application to a phd program?

13:53:14 <sh1mmer> to a program

13:53:15 <bijan> That too is a many month long process :)

13:53:23 <sh1mmer> hmm o

13:53:24 <sh1mmer> k

13:53:29 <bijan> Similar to the other only prolly no interviews

13:53:32 * sh1mmer is bored of waiting already

13:53:36 <bijan> Or on campus visits

13:54:06 <sh1mmer> well I was going to email the MIT people to say I was around in Feb for the TP so if they wanted to do an interview that would be a good time for it

13:54:13 <bijan> For phil, the applications went out in fall, maybe as late as feb, and the earliest was march

13:54:25 <bijan> I wouldn't pop an interview, but I woudl say, "i'd like to visit and chat"

13:54:36 <sh1mmer> good idea

13:54:51 <sh1mmer> I was going to get one of the w3 people to take me around if possible anyway

13:54:55 <sh1mmer> they all have staff cards

13:54:59 <bijan> Heh

13:55:02 <bijan> When will you be there?

13:55:08 <bijan> During the tech plen?

13:55:11 <sh1mmer> ya

13:55:15 <sh1mmer> and an extra day

13:55:32 <bijan> I'll take you around!

13:55:43 <sh1mmer> I thought you worked at maryland

13:55:50 <bijan> "I can't go in there. I don't know what that is. Over there it looks like something but I probably can't get you in."

13:55:55 <bijan> I do :)

13:55:58 <sh1mmer> lol

13:56:02 * sh1mmer thwacks bijan

13:56:25 <bijan> Well, you can have teh smarmy insider view, or the snarker embittered outsider view

13:56:26 <sh1mmer> I was tempted to apply there too. Maybe I shoulda.

13:56:41 <bijan> IT's a good program, overall

13:56:44 <bijan> MD sucks

13:56:49 <bijan> Esp. compared to Cambridge

13:56:52 <bijan> siiiigh.

13:57:31 * crschmidt is going to cambridge tonight, probably

13:57:55 <sh1mmer> Well I am apply to MIT, Cambridge (england), Manchester (england), Southampton and Galway

13:58:02 <sh1mmer> hiya crschmidt :)

13:58:09 <bijan> Oooo

13:58:11 <sh1mmer> crschmidt are we goign to see you in Feb maybe?

14:01:23 <crschmidt> nope

14:01:34 <sh1mmer> :(

14:01:39 <crschmidt> Don't know who "we" is, but I can pretty well guess that the answer is no.

14:01:51 <eaon> good then i don't have to be jealous

14:01:58 <sh1mmer> well the technical plenary is in Boston/Cambridge

14:03:50 <sh1mmer> you said you might come by since I was on the right side of hte atlantic and not miles away

14:04:01 * sh1mmer amused

14:04:45 <crschmidt> Ah, right. Not going to be able to make it, no.

14:06:02 <sh1mmer> aparently applying to Cambridge you have to pay more to use the online than the paper. bizare.

14:08:48 * bijan notes that convenience for everyone involved is a PRIVALEDGE not a right

14:09:18 <bijan> So too for correct orthography

14:11:11 <sh1mmer> Well MIT charge $75 across the board, but then I think they probably get a deluge.

14:14:12 <sh1mmer> Talliesin_ heya Jon

14:14:29 <Talliesin_> hey

14:14:39 <sh1mmer> hows tricks?

14:15:00 <Talliesin_> grand

14:15:09 <sh1mmer> :)

14:15:16 <sh1mmer> I love you, you are so wonderfully Irish

14:36:49 <balbinus_> balbinus_ is now known as balbinus

16:38:02 <Ismael> how can I test the correctness of a relaxng schema?

16:38:38 <crschmidt> Run it through a relaxng schema validator?

16:38:48 <crschmidt> the relax ng page has a relax ng schema for relax ng, i believe

16:39:24 <Ismael> hum, great

16:39:29 <Ismael> thanks :)

16:39:54 <crschmidt> http://www.relaxng.org/spec-20011203.html appendix A

16:41:24 <Ismael> it works! haha

17:07:19 <xavier> crschmidt: so... do you have a blosxom plugin for ityet?

17:08:58 <crschmidt> xavier: we don't have an RSS 1.1 implementation in blosxom yet, no

17:09:06 <crschmidt> xavier: mostly because I don't know blosxom :)

17:09:08 <sbp> feel free to write one for us! :-)

17:09:10 <xavier> k. sounds like a project :-)

17:09:34 <crschmidt> Does blosxom have 1.0 support?

17:09:40 <xavier> yup.

17:09:42 <xavier> as a plugin.

17:10:01 <crschmidt> Got a link?

17:11:00 <xavier> http://www.blosxom.com/plugins/syndication/rss10.htm Blosxom RSS 1.0 plugin

17:11:00 <dc_swig> D: http://www.blosxom.com/plugins/syndication/rss10.htm from xavier

17:11:17 <xavier> D:|Blosxom RSS 1.0 plugin

17:11:17 <dc_swig> Titled item D.

17:11:32 <xavier> (gah, i really need to submit my patches to chumpbot)

17:11:38 <crschmidt> Thanks. With that, I'll give it a go

17:11:53 <xavier> K.

17:12:05 <xavier> (bah, taking away my fun :p)

17:12:41 <crschmidt> feel free to do it before me ;)

17:14:40 <crschmidt> looking at the code, maybe I won't do it.

17:14:44 <crschmidt> I don't see an <rdf:RDF>

17:14:50 <crschmidt> until I see one, I have no clue what to do :)

17:14:58 <xavier> hehe.

17:15:45 <crschmidt> looks like i need to understand what flavours are

17:16:59 <xavier> Yeah. They're templates, essentially.

17:19:22 <sbp> where's the rss10 flavour file?

17:20:59 <xavier> That's a really good question.

17:30:51 * KjetilK wonders if there is a "Web Architecture for Policy Makers" somewhere?

17:33:11 <KjetilK> most policy makers around here seems to try to break as much as they can, banning (deep) links, building monolithic hierarchal portals, URIs that are platform dependent down to the backend db chosen, etc...

17:35:39 <sbp> KjetilK: there's a lot of such stuff in http://www.w3.org/TR/webarch/

17:36:07 <KjetilK> sbp: yup, I just read it, great document, but policy makers wont read it....

17:37:31 <KjetilK> they really don't want to read anything, but if forced, it may be possible to get them to read something that is written expressedly for them...

17:39:36 <sbp> just convince them that that is expessly written for them

17:39:47 <crschmidt> heh

17:40:13 <KjetilK> hehe

17:40:16 <crschmidt> s/<title>.*?</title>/<title>Web Architecture for Policy Makers</title>/

17:40:30 <crschmidt> bah, trailing characters after /

17:40:38 * crschmidt shoulda used !

17:41:37 <Ismael> I need a tip: how can I do a relaxng schema let two elements in any order? seting both optional? :-m

17:43:17 <KjetilK> I'm afraid they won't make it pass the first mention of "URI" where they will think "huh?" but won't admit that they need to read up, because they are policy makers and can't admit that they don't know everything

17:44:37 <KjetilK> there has been a few cases on deep linking around here, and AFAIK, they have all ended with a loss, so it seems like linking in Norway and Denmark is pretty much illegal by now... :-(

17:45:54 <KjetilK> or rather, a statement that "you cannot link us" has legal weight

17:48:31 <KjetilK> also, .no gov't is planning a huge portal, that seems architecturally broken in pretty much every aspect I can think of, and I'm pretty sure it'll make identity theft into a great kids' game...

17:48:45 <Talliesin_> Talliesin_ is now known as Talliesin

17:49:28 <KjetilK> with the IT industry here dancing happily along with all the money that is poured over them, it is going to be very, very hard to convince policymakers that they've got the Wrong Idea...

17:50:33 <jsled> Can you point them to other the fruits of other eGov effort's labors which have reasonable recommendations?

17:51:09 <KjetilK> that's why I'd like to refer to a W3C document written in a form they can read

17:52:08 <KjetilK> jsled: I have tried to point to the German project, that created stuff like ?gypten and Sphinx, but I don't have the right contacts

17:52:53 <KjetilK> also, I'll give them that, some parts of this is truly novel

17:53:28 <KjetilK> so, there is no real precedent, they'll have to think about architecture from scratch

17:57:30 <KjetilK> for an idea of the level of brokeness we're talking, one of the agencies that will play an important role here shut down their web site every night for "regular maintenance".... A friend of mine works there. There are more horror stories...

18:05:25 <xavier> crschmidt: one thing which del.icio.us fails to do in its semantic output is deal with the rdf:about tag properly.

18:06:27 <xavier> As it asserts that the poster of a link is the creator of the link.

18:06:48 <xavier> You hint at that in the 1.1 spec, but don't address it directly (or so I've seen)

18:08:41 <crschmidt> xavier: That was my primary motivation for making the rdf:about optional in 1.1

18:08:44 <xavier> mmm, you somewhat do in the usage notes.

18:08:51 <xavier> Yeah.. a good idea.

18:09:04 <crschmidt> however, that's really the fault of the content provider, and rdf:about has been requested in several different sectors by people to be brought back as mandatory

18:10:42 <crschmidt> Really, just need to make content providers actually understand RDF before they create it :p

18:10:50 <xavier> Yeah..

18:11:07 <xavier> of course, if you can do that...

18:17:19 <xavier> well, rdf:about is like a permalink for something. Which is really good. However if you don't have such, ala delicious, it'd be nice if it were omitable.

18:18:04 <xavier> So, yay RSS 1.1

18:18:23 <crschmidt> Well, RSS 1.1 is going to be rolling that change back, per popular demand

18:18:36 <crschmidt> If you don't have a permalink, you should use a local identifier

18:18:47 <crschmidt> del.icio.us/crschmidt#foo

18:18:53 <xavier> Yup.

18:19:54 <crschmidt> It'd be nice, but no permalinks is uber-bad for aggregators

18:20:09 <crschmidt> they need a unique identifier, and without rdf:about, there isn't much they can dco

18:20:46 <xavier> Yeah. I guess the question is if misapplied unique identifiers is worse..

18:20:55 <xavier> in order to satiate the spec.

18:21:25 <crschmidt> At first, I said yes.

18:21:27 <crschmidt> Now, I say no. :)

18:22:02 <xavier> Bad data is better than no data? ;p

18:23:13 <crschmidt> Tool friendliness is more important than the possibility of broken semantics in this limited case.

18:23:25 <xavier> ouch: "User-Agents MUST NOT continue to process feeds that are not well-formed XML, and MUST inform the user. "

18:23:55 <crschmidt> If it's not valid XML, most aggregators break anyway

18:24:34 <xavier> Hm. I beg to differ ;p

18:24:49 <xavier> It depends on where the XML is invalid.

18:24:56 * crschmidt shrugs.

18:25:01 <xavier> like, entitites in it that aren't defind make it invalid.

18:25:25 <xavier> yet you have HTML entities in RSS feeds all the time - not necessarily correctly, mind you.

18:25:51 * bijan notes that if they can't get wellformedness right...well, they suck

18:26:24 <xavier> Many many web pages can't get welformedness right ;p

18:26:43 <bijan> And so, they shoudlnt' claim to be XHTML

18:26:52 <xavier> Very true.

18:27:08 <bijan> Besides, with machine generated RSS, the suckiness is bigger :)

18:27:14 <bijan> More sucky

18:27:41 <xavier> Well, let's hope that by making the spec. stricter, more will conform.

18:29:11 <crschmidt> There'rs also the fact that most user-agents will probably not be fully conforming.

18:32:27 <xavier> I'm very fond of the move to the List inheritance. That's how it should have been from the start.

18:32:47 <xavier> well, rdf:Seq

18:32:49 <bijan> List?

18:32:52 <bijan> Seq?

18:32:55 <bijan> Ewwwwwwwwwwwwwww

18:33:33 <xavier> Pardon?

18:33:47 <bijan> They subclass rdf:List?

18:33:50 <bijan> That's jsut a mistake

18:34:23 <xavier> "Removed the rss:items element and all its content. This was a hack to get around the fact that the item definitions were unordered in RDF, and is now handled by an rdf:List instance instead, per the rdf:parseType="Collection" requirement. This resolves IssueRequiredRdfSeq."

18:34:31 <xavier> Why do you say that?

18:35:03 <bijan> Collections and containers in RDF are busted, IMHO

18:35:19 <xavier> Ah.

18:35:23 <bijan> If you want to use OWL DL, Collections in particular are extra busted

18:36:24 <bijan> RDF is more like the relational calculus than like XML, so one is generally better off using extra formalism ordering constructs

18:36:29 <bijan> E.g., in your application

18:36:39 <bijan> OR by providing a property (e.g., a timestamp)

18:42:59 <xavier> well, broken or not, inheriting it is better than making a separate section that has to be generated specially.

18:43:34 <xavier> (for XML-based generators, that is)

18:46:56 <bijan> eh

18:47:02 <bijan> Not from my persepective ;)

18:47:11 <bijan> I never had any difficulty

18:47:26 <bijan> Plus, hte obviously better solution doesn't requrie "a separate section"

18:47:33 <bijan> Of course, niether did usign seq

18:47:42 <bijan> You could have inlines stuff just as well then

18:47:51 <bijan> (from an rdf pov)

19:28:01 <rubys> sbp: http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.intertwingly.net%2Fblog%2Findex.rss11

19:30:42 <sbp> rubys: wow great, thanks! that was rather quick

19:30:57 <rubys> I'm not done, but I'm getting there.

19:31:03 <rubys> I pass all of the "pos" tests.

19:31:12 <rubys> Some of the "neg" tests are still ongoing.

19:31:13 <sbp> we're still collecting feedback from all over the place, and we have a few things that we need to fix that may affect the validation. I presume you want me to keep to informed of all the changes that are made?

19:31:15 <xavier> :-) whee, mine validated.

19:31:18 <sbp> cool

19:31:51 <xavier> of course, i know mine's invalid as I still have xhtml in my <description/>

19:32:09 <sbp> hence neg still ongoing...

19:32:14 <xavier> Yup.

19:32:44 <rubys> sure. I'll periodically poll the site too. My goal is to pass all of your test cases

19:33:00 * sbp nods

19:33:08 <rubys>http://feedvalidator.org/testcases/rss11/must/

19:33:08 <dc_swig> E: http://feedvalidator.org/testcases/rss11/must/ from rubys

19:33:11 <sbp> the test cases will certainly be updated to reflect the changes

19:33:24 <sbp> so you can just keep track of test.tar.gz

19:33:47 <sbp> E:|RSS 1.1 Test Cases (feedvalidator.org style)

19:33:48 <dc_swig> Titled item E.

19:34:25 <rubys> the tests that I don't pass yet involve extensions. Currently, I pretty much ignore them, but rss 1.0 has specific restrictions that I need to enforce.

19:34:34 <rubys> Shouldn't be a problem, but I wanted to commit this part first.

19:35:01 <rubys> but consider this supported in the sense that I will accept bug reports

19:35:19 <rubys> feel free to update the documentation to reflect that and mention my feed.

19:35:24 <sbp> excellent. I'll make a note of it in the guide

19:35:30 <rubys> I'll also mention it on my blog later today.

19:35:31 <sbp> yep! certainly planning on doing so :-)

19:35:49 <sbp> ah, thank you. it's a tremendous bit of progress--I can't thank you enough

19:36:34 * sbp knows from working on validator.py just how difficult it is to get these things down correctly

19:37:03 <rubys> I've got a framework in place which makes it pretty easy. In fact, the code changes were fairly small.

19:42:43 * sbp finishes changing The Rough Guide

19:43:08 <sbp> linked to the FeedValidator results for your valiation link, and tested it locally in the other validator too (and it works, of course)

19:44:09 <sbp> hmm. browsing through http://cvs.sourceforge.net/viewcvs.py/feedvalidator/

19:45:03 <sbp> I need to read other people's code more often. didn't know about this:

19:45:04 <sbp> import codecs

19:45:04 <sbp> ENCODING='UTF-8'

19:45:04 <sbp> sys.stdout = codecs.getwriter(ENCODING)(sys.stdout)

19:45:29 <sbp> I presume it does an .encode('utf-8') on anything you print to sys.stdout then

19:49:53 <rubys> sbp: my feed validates with your validator too

19:52:18 <sbp> yep. that's what I meant by "tested it locally in the other validator"

19:53:31 <rubys> I'd only suggest that my "validate" link be the same as the others.

19:54:23 <rubys> you've got the official rss 1.1 validator - it likely will end up being stricter than mine, if only in that it is scoped specifically to one version of rss.

19:59:32 <sbp> I was thinking about putting both links there

20:00:38 <sbp> actually I can't wait to make changes to the draft so that I can go back to coding. implementing that was really fun; doing all the proselytization on the lists, on the other hand, is not fun

20:00:52 <sbp> I just had an email-noise a moment ago from Thunderbird and cheered when I found out it was a spam

20:01:07 <sbp> if one more person comments about Collection...

20:04:45 <sbp> hmm. I should also think about machine readable output, either as XML or HTTP headers

20:04:57 <sbp> then I can automatedly check that everybody on the list still validates

21:19:18 <bskahan> anyone have a sample rss1.1 feed up?

21:20:30 <crschmidt> http://miscoranda.com/rss1.1 is is pretty simple, i think

21:20:30 <dc_swig> F: http://miscoranda.com/rss1.1 from crschmidt

21:20:35 <bskahan> crschmidt: tnx

21:20:36 <crschmidt> F:| Example RSS 1.1 Feed

21:20:36 <dc_swig> Titled item F.

21:20:42 <crschmidt> F: From miscoranda

21:20:42 <dc_swig> Added comment F1.

21:21:13 <crschmidt> oh, hm, that's a bad feed example, it uses encoded stuff in <description>

21:21:25 <sbp> ssh

21:21:42 <sbp> actually, I meant to fix that

21:22:24 <crschmidt> bskahan: http://inamidst.com/rss1.1/guide#Sites has other examples

21:23:00 <eaon> bskahan: hey my commited version is valid ;) i already tested ;)

21:23:55 <bskahan> nice

21:24:00 <bskahan> blam works with 1.1

21:24:18 * bskahan ponders how to sync his blog with subversion

21:25:21 <rubys>http://www.intertwingly.net/blog/2005/01/19/RSS-1-1

21:25:21 <dc_swig> G: http://www.intertwingly.net/blog/2005/01/19/RSS-1-1 from rubys

21:28:29 <crschmidt> G:| RSS 1.1 Post from Sam Ruby

21:28:29 <dc_swig> Titled item G.

21:28:40 <crschmidt> Thanks, rubys, looks very nice, glad to see you like it

21:33:08 * rubys wonders where it says that he likes it. ;-)

21:33:33 <crschmidt> You're using it. That's endorsement enough for me :)

21:33:47 * rubys chuckles

21:34:00 <rubys>http://www.intertwingly.net/feeds/

21:34:00 <dc_swig> H: http://www.intertwingly.net/feeds/ from rubys

21:34:53 <eaon> .. i did't know someone actually implemented rss 3.0

21:35:03 <crschmidt> There's a bloxsom module for it too

21:36:33 <crschmidt> H:| Feeds From intertwingly

21:36:33 <dc_swig> Titled item H.

23:20:31 <Talliesin_> Talliesin_ is now known as Talliesin


The IRC chat here was automatically logged without editing and contains content written by the chat participants identified by their IRC nick. No other identity is recorded.

Alternate versions: RDF Resource Description Framework Metadata and Text

Provided by Dave Beckett. Hosted by Useful Information Company.