Phurl: Creates a rdf collection that can be included in an n3 document to index any list of anon objects
Phurl: See example output Total.rdf
Phurl: Created with this command : perl makelist.pl http://introspector.sf.net/2004/12/PNetTree.owl\# 15 > list15.n3; cat list15.n3 BUG_8262_.n3 > merge.n3; ~/cwm/cwm.py merge.n3 -rdf > total.rdf
Phurl: From this Input file
Phurl: The next step is to automate the index creation of the index by looking for the ":call-stack:has-list _:genid1 ;:begins-with :stack-begin;:ends-with :stack-end;a :stack." and scanning between "[:stack-begin :call-stack]." and "[:stack-end :call-stack]." "
Phurl: it should be possible to write a cwm rule to replace the entire perl script and shell script
Phurl: See example output Total.rdf
Phurl: Created with this command : perl makelist.pl http://introspector.sf.net/2004/12/PNetTree.owl\# 15 > list15.n3; cat list15.n3 BUG_8262_.n3 > merge.n3; ~/cwm/cwm.py merge.n3 -rdf > total.rdf
Phurl: From this Input file
Phurl: The next step is to automate the index creation of the index by looking for the ":call-stack:has-list _:genid1 ;:begins-with :stack-begin;:ends-with :stack-end;a :stack." and scanning between "[:stack-begin :call-stack]." and "[:stack-end :call-stack]." "
Phurl: it should be possible to write a cwm rule to replace the entire perl script and shell script
jsled: "XML Query, the Semantic Web, and WS-* will continue to hold promise.
jsled: "The semantic web and RDF still require way too much deep geekery to grok. The WS-* stack will stabilize in 2005, but without platform-level support (which won't really emerge until 2006), its scope is limited to early adopters."
jsled: "The semantic web and RDF still require way too much deep geekery to grok. The WS-* stack will stabilize in 2005, but without platform-level support (which won't really emerge until 2006), its scope is limited to early adopters."
KjetilK: Bob DuCharme has an article about the use of the link types in connection with blogs and RDF
crschmidt: <p:highlight rdf:resource="http://www.picdiary.com/londonmarkets/img_4579.jpg"/>
crschmidt: Pulled from the source of http://www.picdiary.com/rss/londonmarkets.rss
crschmidt: NS URI is a 404: seems like that's the only property he uses (at least in the londonmarkets.rss file)
crschmidt: Pulled from the source of http://www.picdiary.com/rss/londonmarkets.rss
crschmidt: NS URI is a 404: seems like that's the only property he uses (at least in the londonmarkets.rss file)
jsled: Seems to output an RSS feed with <rawk:{thumbnail{,Width,Height}}> properties.
jsled: uses the namespace http://burtonini.com/rawk/ , which is 404. :(
jsled: uses the namespace http://burtonini.com/rawk/ , which is 404. :(
sbp: For when you want to add someone to your FOAF file but can't be bothered to look up all the details by hand.
sbp: In a similar vein to FOAFQ.
crschmidt: Based off data in julie
sbp: In a similar vein to FOAFQ.
crschmidt: Based off data in julie
danbri: Feb 2003 talk by Alun Preece.
dajobe: The tag algorithm lets people mint — create — identifiers that no one else using the same algorithm could ever mint.
dajobe: co-invented by sandro
dajobe: co-invented by sandro
danbri: A precursor to current Web Services scene, this work explored the reconceptualisation of HTTP (and FTP etc) as a set of distributed object interfaces, expressible in IDLs.
danbri: You might also think about this as a formalization (or re-documentation) of REST principles, along lines more recently explored by the W3C TAG work on Web Architecture.
danbri: "Objects which are Renderable may be asked to produce a Rendering based on a set of Preferences. This is analogous to HTTP Get. A Rendering is a transformation of the object's native data into some other form, typically a collection of bytes with an interpretation determined by a named type relative to some typespace. Common examples are illustrated by the various MIME types, e.g. text/html "
danbri: "...Rendering for viewing in a web browser, and an application/postscript Rendering for printing. When a Renderable object is asked for a Rendering of a preferred type, the implementation of the object's method for this operation transforms or maps the native data to this Rendering type. Note that this transformation may or may not be reversible. "
danbri: "If the Rendering format happens to be the same as the native data of the document, the transformation might be identity. Objects that have no native data themselves may be able to produce a Rendering by generating it from other sources (e.g. real world state, other objects)."
danbri: You might also think about this as a formalization (or re-documentation) of REST principles, along lines more recently explored by the W3C TAG work on Web Architecture.
danbri: "Objects which are Renderable may be asked to produce a Rendering based on a set of Preferences. This is analogous to HTTP Get. A Rendering is a transformation of the object's native data into some other form, typically a collection of bytes with an interpretation determined by a named type relative to some typespace. Common examples are illustrated by the various MIME types, e.g. text/html "
danbri: "...Rendering for viewing in a web browser, and an application/postscript Rendering for printing. When a Renderable object is asked for a Rendering of a preferred type, the implementation of the object's method for this operation transforms or maps the native data to this Rendering type. Note that this transformation may or may not be reversible. "
danbri: "If the Rendering format happens to be the same as the native data of the document, the transformation might be identity. Objects that have no native data themselves may be able to produce a Rendering by generating it from other sources (e.g. real world state, other objects)."
jsled: Or `emerge jabberd` on gentoo. :)