peepo: Technologies must be (a) capable of being understood by millions of people, and (b) easily implemented by these same people.
peepo: this is something I've been saying since 1998, obviously with a lot less cogency ~:"
danbri: "It's like the W3C has created a way to Say Everything but haven't given a person a way to say "I exist"."
danbri: <Document rdf:about=""><maker><Person/></maker></Document> = "I exist and (I made this)!"
danbri: Hmm well "I" is tricky actually ;)
danbri: <Person/> is "Someone exists" (can't get simpler than that...)
peepo: danbri: it's not just the language, but also the authoring tools, and the means to publish. not everyone is a bureaucrat, but you know that already ~:"
peepo: this is something I've been saying since 1998, obviously with a lot less cogency ~:"
danbri: "It's like the W3C has created a way to Say Everything but haven't given a person a way to say "I exist"."
danbri: <Document rdf:about=""><maker><Person/></maker></Document> = "I exist and (I made this)!"
danbri: Hmm well "I" is tricky actually ;)
danbri: <Person/> is "Someone exists" (can't get simpler than that...)
peepo: danbri: it's not just the language, but also the authoring tools, and the means to publish. not everyone is a bureaucrat, but you know that already ~:"
sh1m: Have wrapped RDF repositories (among others) with an SQI gateway
sh1m: Aimed at learning resources
sh1m: Aimed at learning resources
lion: Idea of binding data automatically from RDF to a particular form in code
lion: and back. Similar to XML data binding.
Wack: I've used some hacked-up 2-way (read/write) RDF-path language for easier, dynamic, data access to RDF graphs
Wack: I guess it depends on whether you want to convert existing data-structures (such as objects, lists, dicts, etc) into RDF or have all data explicit as RDF.
Wack: In the latter case, some RDF(S) meta-class could autogenerate objects with properties from the same namespace/schema and set those up with get/set methods that create and store the triples?
lion: and back. Similar to XML data binding.
Wack: I've used some hacked-up 2-way (read/write) RDF-path language for easier, dynamic, data access to RDF graphs
Wack: I guess it depends on whether you want to convert existing data-structures (such as objects, lists, dicts, etc) into RDF or have all data explicit as RDF.
Wack: In the latter case, some RDF(S) meta-class could autogenerate objects with properties from the same namespace/schema and set those up with get/set methods that create and store the triples?
danbri: Nearby: FOAFCorp experiments including Dino's SVG foafcorp based on an earlier snapshot.
danbri: Also some old scripts I used to convert this to RDF/XML (prev version of the SQL, not sure if will still work).