danbri: Kinda cheeky. They mean, they're using P2Pish techniques to share the contents of bookmark lists. I think.
dajobe: I found it on O'reilly Network weblogs from Tim O'Reilly - doesn't seem to be a URL for that particular blog
AaronSw: Aha, TimO's thoughts
DanC_: on coordination languages, see also my WebApps essay of Mar/Apr 1997
DanC_: Baker's reply is heartening.
AaronSw: Aha, TimO's thoughts
DanC_: on coordination languages, see also my WebApps essay of Mar/Apr 1997
DanC_: Baker's reply is heartening.
AaronSw: """These are some excerpts to a response to questions posed by Clay Shirky as part of a research report he is doing for O'Reilly on Web Services."""
AaronSw: I basically claim that Web Services is merely a facet of the Semantic Web
AaronSw: I basically claim that Web Services is merely a facet of the Semantic Web
DanC_: The O'Reilly Peer-to-Peer and Web Services Conference
DanC_: Washington, D.C. -- September 18-21, 2001
DanC_: Washington, D.C. -- September 18-21, 2001
DanC_: nifty web services portal
DanC_: http://conferences.oreilly.com/p2p/
DanC_: who runs this thing? I can't find an "about..." page
DanC_: http://conferences.oreilly.com/p2p/
DanC_: who runs this thing? I can't find an "about..." page
bijan: | VML, ML extened with "hypothetical views"
bijan: Via the Lambda the Ultimate weblog.
bijan: "Operationally, a hypothetical view is a value with a representation that indicates how the value was created."
bijan: Sounds familiar :)
bijan: Via the Lambda the Ultimate weblog.
bijan: "Operationally, a hypothetical view is a value with a representation that indicates how the value was created."
bijan: Sounds familiar :)
AaronSw: "Reliable HTTP" - HTTPR
AaronSw: Designed in part for business-critical web service stuff
AaronSw: Mark Baker responds: """"request" appears to be nothing more than a means of encoding an RPC style method invocation mechanism over HTTP POST. This doesn't fit well with the hypertext transfer application semantics that HTTP defines."""
AaronSw: Designed in part for business-critical web service stuff
AaronSw: Mark Baker responds: """"request" appears to be nothing more than a means of encoding an RPC style method invocation mechanism over HTTP POST. This doesn't fit well with the hypertext transfer application semantics that HTTP defines."""
AaronSw: Principle 1: Don't interfere with the conversation (act only when called upon)
AaronSw: Principle 2: Don't allow users to make irreversable mistakes
AaronSw: Principle 2: Don't allow users to make irreversable mistakes
AaronSw: A Web interface to ARP
AaronSw: barstow, it'd be nice if SiRPAC pointed here saying that ARP was better for validation...
danbri: done. kinda.
danbri: I'd like to find a space to pay tribute to the role the (now ageing) SiRPAC parser played in RDF history. This'll do for starters! SiRPAC was critical in getting the first wave of RDF apps off the ground; we all owe a dept to Janne.
AaronSw: I agree, SiRPAC is very important... however, there have been some problems with folks putting out bad RDF and saying "SiRPAC said it was fine"
danbri: I agree, the SiRPAC codebase was showing its age, and ARP is a fine successor (for Java-heads).
em: Notes the fact that Janne implemented SiRPAC from the spec only... it was an interesting test to see if people could develope to the RDF spec independant of working with members of the working group...
AaronSw: barstow, it'd be nice if SiRPAC pointed here saying that ARP was better for validation...
danbri: done. kinda.
danbri: I'd like to find a space to pay tribute to the role the (now ageing) SiRPAC parser played in RDF history. This'll do for starters! SiRPAC was critical in getting the first wave of RDF apps off the ground; we all owe a dept to Janne.
AaronSw: I agree, SiRPAC is very important... however, there have been some problems with folks putting out bad RDF and saying "SiRPAC said it was fine"
danbri: I agree, the SiRPAC codebase was showing its age, and ARP is a fine successor (for Java-heads).
em: Notes the fact that Janne implemented SiRPAC from the spec only... it was an interesting test to see if people could develope to the RDF spec independant of working with members of the working group...
deltab: Apache allows handlers to be called for specified directories and filename extensions
deltab: Handlers can be provided by modules, or be arbitrary programs
deltab: They're used for processing files before output - useful for special markup, or adding headers and footers automatically
deltab: Handlers can be provided by modules, or be arbitrary programs
deltab: They're used for processing files before output - useful for special markup, or adding headers and footers automatically
DanC_: p3p.rdf by BrianM; p3p.{svg,png} by EricM; p3p-bis.{svg,png} by DanC
danbri: Cool demo by Libby Miller; visionary original vision by Libby & DanBri
danbri: see also original wishlist writeup from Kowloon and the RDFWeb site.
DanC_: yeah, that is cool
danbri: Aaron and DanBri play at finding paths through the RDFWeb co-depiction graph...
danbri: From libby to aaron, via jan, [dave|http://swordfish.rdfweb.org/discovery/2001/08/codepict/codepict.jsp?mbox=mailto:dave.beckett@bristo
danbri: ...and emiller. Maybe we should dump this all in prolog/n3 for logic geeks to play with?
danbri: oh, I messed up the blog hyperlinks, but you get the idea.
DanC_: I keep looking for the "view source" button/link. e.g. where's the actual query that's used? can I get the database in RDF/xml form?
libby: now you can look at the list of urls used
libby: the query used is at the bottom of the page
danbri: see also original wishlist writeup from Kowloon and the RDFWeb site.
DanC_: yeah, that is cool
danbri: Aaron and DanBri play at finding paths through the RDFWeb co-depiction graph...
danbri: From libby to aaron, via jan, [dave|http://swordfish.rdfweb.org/discovery/2001/08/codepict/codepict.jsp?mbox=mailto:dave.beckett@bristo
danbri: ...and emiller. Maybe we should dump this all in prolog/n3 for logic geeks to play with?
danbri: oh, I messed up the blog hyperlinks, but you get the idea.
DanC_: I keep looking for the "view source" button/link. e.g. where's the actual query that's used? can I get the database in RDF/xml form?
libby: now you can look at the list of urls used
libby: the query used is at the bottom of the page
DanC_: call for participation went out yesterday. We're now open for business.
dajobe: and DanC is staff contact
dajobe: and DanC is staff contact
DanC_: recently A Proposal for Encoding Logic in RDF/DAML of 8 Aug 2001
DanC_: this 8Aug proposal is pretty clean... doesn't monkey with RDF basics. But it assumes RDF sequences have the "and that's all" property, when it's not clear that they do.
DanC_: looks remarkably like my Aug DAML draft, which is ironic, considering how Drew responded to that.
DanC_: this 8Aug proposal is pretty clean... doesn't monkey with RDF basics. But it assumes RDF sequences have the "and that's all" property, when it's not clear that they do.
DanC_: looks remarkably like my Aug DAML draft, which is ironic, considering how Drew responded to that.
nephrael: Updated form of Sigma Inference Engine
nephrael: Go to Ask/Tell and make a Ask: (instance ?SPINE SpinalColumn)
nephrael: Click "ask" Button
nephrael: Use the "3 Seconds" Option
nephrael: Go to Ask/Tell and make a Ask: (instance ?SPINE SpinalColumn)
nephrael: Click "ask" Button
nephrael: Use the "3 Seconds" Option
AaronSw: Written after reading the XP Reqs and not finding it
AaronSw: In the end I got no response from the WG, and it ended up devolving into a discussion about how SOAP/XML-RPC always over POST were easier to use than preserving the GET/POST semantics
AaronSw: I wrote a message to Hugo today checking up on the issue