sbp: By Arjun Ray, on www-talk, 2001-06
sbp: I bet there'd be lots of stuff in xml-sig that's relevant to numerous TAG and RDF Core WG issues
sbp: But... <xover> It occurs to me that it's probably easier to get to the CIA files on the Kennedy hit, under the Freedom of Information Act, then to get to the xml-sig archives...
danb_lap: w3c-xml-sig was closed in 1998, "General discussion of XML and its underlying philosophy will take place in the public mailing lists and news groups that have been formed for this purpose."
xover: "The Freedom of Information Act generally provides that any person has a right, enforceable in court, of access to federal agency records, except to the extent that such records (or portions thereof) are protected from disclosure by one of nine exemptions."
xover: Can anyone point me to the W3C equivalent to that NSA page?
sbp: I bet there'd be lots of stuff in xml-sig that's relevant to numerous TAG and RDF Core WG issues
sbp: But... <xover> It occurs to me that it's probably easier to get to the CIA files on the Kennedy hit, under the Freedom of Information Act, then to get to the xml-sig archives...
danb_lap: w3c-xml-sig was closed in 1998, "General discussion of XML and its underlying philosophy will take place in the public mailing lists and news groups that have been formed for this purpose."
xover: "The Freedom of Information Act generally provides that any person has a right, enforceable in court, of access to federal agency records, except to the extent that such records (or portions thereof) are protected from disclosure by one of nine exemptions."
xover: Can anyone point me to the W3C equivalent to that NSA page?
JibberJim: "In particular, a student group in Berkeley California created a more reliable format which required people who posted information about someone else, to verify their relationship to that person. "
JibberJim: A job for RDF and FOAF!
JibberJim: A job for RDF and FOAF!
AaronSw: cited in an email by DJB
AaronSw: Establishes that in the US, standards organizations must " prevent the standard-setting process from being biased by members with economic interests in stifling product competition". AME paid $4.75 million.
AaronSw: The FTC apparently also said that stds orgs must provide due process, including "timely hearings with prompt decisions" and "the presentation of valid reasons for any potentially anticompetitive activity"
AaronSw: Is there any documentation of how the W3C meets these requirements?
DanC: quote forwarded without permission deleted
AaronSw: Actually, I think a People v. W3C lawsuit would be interesting... <duck />
DanC: W3C process has all sorts of checks, balances, and appeals. Who knows if it's enough. Or too much, even.
DanC: the requirement to formally address issues is probably the most relevant, along with the appeal processes.
AaronSw: Establishes that in the US, standards organizations must " prevent the standard-setting process from being biased by members with economic interests in stifling product competition". AME paid $4.75 million.
AaronSw: The FTC apparently also said that stds orgs must provide due process, including "timely hearings with prompt decisions" and "the presentation of valid reasons for any potentially anticompetitive activity"
AaronSw: Is there any documentation of how the W3C meets these requirements?
DanC: quote forwarded without permission deleted
AaronSw: Actually, I think a People v. W3C lawsuit would be interesting... <duck />
DanC: W3C process has all sorts of checks, balances, and appeals. Who knows if it's enough. Or too much, even.
DanC: the requirement to formally address issues is probably the most relevant, along with the appeal processes.
LotR: I don't think anyone is working on that.
danb_lap: Not sure if this got chump'd before. Also Edd's FOAF pages, including foafbot, pgp-signed RDF writeups etc.
danb_lap: I implemented the basic 'lookup annotations on some URL' on top of a RubyRDF/PostgreSQL/Squish RDF database.
danb_lap: I've checked this in as part of the RDFWeb's 'scutter' rdf harvester, but it's pretty much standalone, assuming some strategy for acquiring / authoring annotations and their RDF descriptions.
danb_lap: I've checked this in as part of the RDFWeb's 'scutter' rdf harvester, but it's pretty much standalone, assuming some strategy for acquiring / authoring annotations and their RDF descriptions.
DanC: PropertyList-1.0.dtd
DanC: used by, e.g., iTunes when exporting playlists to XML
DanC: I think I can convert to RDF in about 20 lines of XSLT...
xover: Apple Developer Documentation for Property List Services.
xover: Apple Developer Documentation for XML Services.
DanC: ok, so it took 79 lines of XSLT. but my plist2rdf.xsl is working, on at least one test case.
xover: The relevant code appears to be available in Darwin, so anyone with the time and inclination might manage to get some patches in through this route. :-)
DanC: the 100 lines of XSLT
DanC: other almost-RDF stuff seen lately: dia, gnumeric
DanC: used by, e.g., iTunes when exporting playlists to XML
DanC: I think I can convert to RDF in about 20 lines of XSLT...
xover: Apple Developer Documentation for Property List Services.
xover: Apple Developer Documentation for XML Services.
DanC: ok, so it took 79 lines of XSLT. but my plist2rdf.xsl is working, on at least one test case.
xover: The relevant code appears to be available in Darwin, so anyone with the time and inclination might manage to get some patches in through this route. :-)
DanC: the 100 lines of XSLT
DanC: other almost-RDF stuff seen lately: dia, gnumeric
bijan: Don't know if it's unfair or fair about the book, but it contains a number of whoppers.
bijan: """Expert systems today are not implemented in LISP; it is much too low level and inefficient a language."""
bijan: Interesting tension there, as "inefficient" usually goes with "high level". That tension isn't the whopper, of course. The whopper is that Lisp is a very high level language and plenty of ES are implented in it.
bijan: """For experimenters, the book also describes a LISP-like language called CLIPS."""
bijan: While CLIPS is, in fact, Lisp like (having been derivied from Lisp), that's hardly the most significant feature about it.
bijan: What makes CLIPS interesting is that it's a fast forward chainer. Aside from syntax, I believe it shares more with Prolog than with Lisp per se.
bijan: """As you read, you get a sense that some programming constructs, such as Smalltalk's "frames," didn't just materialize out of thin air."""
bijan: Er... Smalltalk's frames? Huh? Oh well.
bijan: You'd be better off reading Alan Kay's history of Smalltalk.
bijan: """Expert systems today are not implemented in LISP; it is much too low level and inefficient a language."""
bijan: Interesting tension there, as "inefficient" usually goes with "high level". That tension isn't the whopper, of course. The whopper is that Lisp is a very high level language and plenty of ES are implented in it.
bijan: """For experimenters, the book also describes a LISP-like language called CLIPS."""
bijan: While CLIPS is, in fact, Lisp like (having been derivied from Lisp), that's hardly the most significant feature about it.
bijan: What makes CLIPS interesting is that it's a fast forward chainer. Aside from syntax, I believe it shares more with Prolog than with Lisp per se.
bijan: """As you read, you get a sense that some programming constructs, such as Smalltalk's "frames," didn't just materialize out of thin air."""
bijan: Er... Smalltalk's frames? Huh? Oh well.
bijan: You'd be better off reading Alan Kay's history of Smalltalk.
dajobe: taking 12+ stances on unresolved issues, this isn't necessarily WebONT's final word
dajobe: points to webont datatypes issue saying amongst other things" One possible resolution would be to extend the DAML+OIL solution by allowing xsi:type attributes to provide local typing information."
danb_lap: Compare OWL feature synopsis, which says it'll wait on rdfcore.
dajobe: (far too much opinion in issue 5.8 datatypes than facts)