The CML2 Language: Constraint-based configuration for the Linux kernel and elsewhere, by Eric Raymond
danbri: "Though the Python implementation of CML2 is pleasingly compact at 4800-odd lines, there are theoretical reasons Scheme or Prolog might have been a better vehicle - in particular, in Prolog I might have been able to make the compiler unnecessary by simply having the rulebase be itself a set of Prolog assertions."
danbri: see also the CML2 resources page.
danbri: Python and rules... Sounds like cwm territory.
danbri: see also the CML2 resources page.
danbri: Python and rules... Sounds like cwm territory.
Seth: in this paper, defines the cases in which graphics are used as "inferential surrogates" for what they represent.
Seth: me, still, thinks all you need is the graph ... it contains all the information there is about the situation
Seth: me, still, thinks all you need is the graph ... it contains all the information there is about the situation
danbri: RDF query and SOAP for file sharing service discovery (demo by screenshot)
danbri: Sorry about all the annoying "s in the data; I fixed that in the SOAP service after taking the screenshot.
pldab_: If it isn't clear from the screenshot, the main window is just the default Gnome view of an rdf query result (against a napster-clone server list); the 2nd window shows the same data in the gnapster client.
pldab_: It doesn't _do_ anything yet! GUI based on the perl.com Gnome intro.
pldab_: some sample data describing napster-clone servers. Note: just as the act of PICS labeling a web service isn't an endorsement, my posting this RDF isn't either!
danbri: Sorry about all the annoying "s in the data; I fixed that in the SOAP service after taking the screenshot.
pldab_: If it isn't clear from the screenshot, the main window is just the default Gnome view of an rdf query result (against a napster-clone server list); the 2nd window shows the same data in the gnapster client.
pldab_: It doesn't _do_ anything yet! GUI based on the perl.com Gnome intro.
pldab_: some sample data describing napster-clone servers. Note: just as the act of PICS labeling a web service isn't an endorsement, my posting this RDF isn't either!
AaronSw: This is an article I'm working on about MusicBrainz, the Semantic Web, Web Services, agoric economies, and other stuff.
AaronSw: Please send me comments and suggestions.
AaronSw: Please send me comments and suggestions.
Seth: this is in response to a challenge made by Sean, who apparently doesnt believe it
Seth: for discussion please refer to RDFIG discussion
Seth: for discussion please refer to RDFIG discussion
DanC_: IANA now calls them URI schemes! Yeah! finally!
DanC_: linked from IANA protocol assignments
sbp: Heh: "In the Uniform Resource Locators (URI) definition [RFC2396,RFC1738]"
DanC_: linked from IANA protocol assignments
sbp: Heh: "In the Uniform Resource Locators (URI) definition [RFC2396,RFC1738]"
filsa: if that doesn't work try http://xmlns.filsa.net/metamail/0.1/ temporary url due to dns troubles
filsa: also see meta mail demo for some sample rdf files gen'd from mbox.
filsa: Some notes I made while making my schema.
filsa: I'd appreciate any feedback you have, particularly on the schema itself.
filsa: also see meta mail demo for some sample rdf files gen'd from mbox.
filsa: Some notes I made while making my schema.
filsa: I'd appreciate any feedback you have, particularly on the schema itself.
DanC: hypertext derived from SemEnglish.g
DanC: which derives from seth's diagram
DanC: also: SemEnglish.py, generated python code
DanC: excercise for the reader: (1) implement lexical details of namespaces and such (2) implement semantic actions to feed results to some KB (e.g. cwm) ala rdfn3.g
DanC: hardly tested.
DanC: the two elaborations of ExpObject in the diagram confused me. I improvised ExpObject_
DanC: the one test case it passes is a msg in rdf-interest
DanC: which derives from seth's diagram
DanC: also: SemEnglish.py, generated python code
DanC: excercise for the reader: (1) implement lexical details of namespaces and such (2) implement semantic actions to feed results to some KB (e.g. cwm) ala rdfn3.g
DanC: hardly tested.
DanC: the two elaborations of ExpObject in the diagram confused me. I improvised ExpObject_
DanC: the one test case it passes is a msg in rdf-interest
SethR: So who's got a server that does this ??
sbp: Hmm... this is something that swi-dev@yahoogroups.com should be tackling
AaronSw: This is the basic idea behind MOTO.
AaronSw: The Redfoot folks already do this -- in fact I think they're running a number of sites on the principle.
sbp: Hmm... this is something that swi-dev@yahoogroups.com should be tackling
AaronSw: This is the basic idea behind MOTO.
AaronSw: The Redfoot folks already do this -- in fact I think they're running a number of sites on the principle.
SethR: | Sean's [metadata for this page] button
DanC: in notation3/cwm, implies is a predicate, ranging over formulas. i.e. formulas are objects in the domain of discourse. Possible worlds semantics is the only mechanism I've seen for making sense of this.
DanC: I understand how the propositional operators (and/or/not/implies) work in possible worlds, but I'm trying to figure out how quanitification works.
DanC: oh yeah... (Kripke, 1963)... I've seen several allusions to that. Gotta read that one (or better yet: a more recent treatment of it. recommendations, anyone?)
DanC: hmm... googling on Kripke 1963 yields a nifty-looking Possible Worlds Semantics page
DanC: I understand how the propositional operators (and/or/not/implies) work in possible worlds, but I'm trying to figure out how quanitification works.
DanC: oh yeah... (Kripke, 1963)... I've seen several allusions to that. Gotta read that one (or better yet: a more recent treatment of it. recommendations, anyone?)
DanC: hmm... googling on Kripke 1963 yields a nifty-looking Possible Worlds Semantics page
danbri: Leigh's cleanup of the Inkling/RDFGraph Java sources
danbri: See also Leigh's work-in-progress log
danbri: See also Leigh's work-in-progress log
DanC: also: hypertext kifExpr grammar
DanC: hmm... many of the rules in this grammar are sorta irrelevant...
DanC: I was trying to parse KIF forms, but they're not LL(1) unless I combine the ( token with the one that follows it. I'll probably give that a try
DanC: transcribed from dpans KIF spec
DanC: ok... kifForm.g done, along with kifForm hypertext grammar
DanC: by Matthew Stone
DanC: in notation3/cwm, implies is a predicate, ranging over formulas. i.e. formulas are objects in the domain of discourse. Possible worlds semantics is the only mechanism I've seen for making sense of this.
DanC: I understand how the propositional operators (and/or/not/implies) work in possible worlds, but I'm trying to figure out how quanitification works.
DanC: see also: KIF spec, dpans version
DanC: oops... misplaced several annotations about possible worlds stuff there.
DanC: hmm... many of the rules in this grammar are sorta irrelevant...
DanC: I was trying to parse KIF forms, but they're not LL(1) unless I combine the ( token with the one that follows it. I'll probably give that a try
DanC: transcribed from dpans KIF spec
DanC: ok... kifForm.g done, along with kifForm hypertext grammar
DanC: by Matthew Stone
DanC: in notation3/cwm, implies is a predicate, ranging over formulas. i.e. formulas are objects in the domain of discourse. Possible worlds semantics is the only mechanism I've seen for making sense of this.
DanC: I understand how the propositional operators (and/or/not/implies) work in possible worlds, but I'm trying to figure out how quanitification works.
DanC: see also: KIF spec, dpans version
DanC: oops... misplaced several annotations about possible worlds stuff there.
edd: (well, modulo any naughty XMLhack contributors ignoring the warnings about invalid content.)
edd: this was possible thanks to changing advertising providers.
edd: this was possible thanks to changing advertising providers.
dajobe: I am working on this today; last call for comments, typos, outright arguments
dajobe: I've foolishly made one change I might remove, if you read this later in the day - RDF IDs are now XML IDs. I might delete this since it is probably beyond my editorial authority.
dajobe: now reverted to existing constraint, ISSUE nearby discussing this as a potential change
dajobe: added html and style changes so inserted/deleted bits work with Netscape 4.7x
dajobe: I've foolishly made one change I might remove, if you read this later in the day - RDF IDs are now XML IDs. I might delete this since it is probably beyond my editorial authority.
dajobe: now reverted to existing constraint, ISSUE nearby discussing this as a potential change
dajobe: added html and style changes so inserted/deleted bits work with Netscape 4.7x
danbri: A quick hack of a demo to show how it might work; idea is to contrib this as a driver to Inkling; see also Apache Axis pages.
danbri: Thanks to Glen Daniels for help understanding some SOAP issues (notably conventions for serializing hashtables / Maps)
danbri: I've just posted a slightly cleaned up version of the code. Next job: understanding Map serialization. (I need this for a MedCERTAIN deliverable on RDF aggregators...)
danbri: Next up: contrasting the latest snapshot with Inkling's use of JDBC and refining both. See also Glen's notes on Apache/Axis plans.
danbri: I've also posted an update to the Python RDF query SOAP client (thanks again to Aaron for Python help).
danbri: Thanks to Glen Daniels for help understanding some SOAP issues (notably conventions for serializing hashtables / Maps)
danbri: I've just posted a slightly cleaned up version of the code. Next job: understanding Map serialization. (I need this for a MedCERTAIN deliverable on RDF aggregators...)
danbri: Next up: contrasting the latest snapshot with Inkling's use of JDBC and refining both. See also Glen's notes on Apache/Axis plans.
danbri: I've also posted an update to the Python RDF query SOAP client (thanks again to Aaron for Python help).
danbri: See DAML joint committee archives (somewhere...) for more context.