ronwalf: I seem to have broken them :(
WillWare: I tried this to import rules (like the ones in schema-rules.n3) and discovered that the forAll variables don't work in the file that is importing the other. Then I remembered that "this forAll" specifies a scope for only the file in which the variables are defined.
dajobe: hmm, 3 years and I have tarballs, rpms and debs but still no logo or T-Shirt. I'm doing this all wrong.
danbri: "Samizdat is a generic RDF-based engine for building collaboration and open publishing web sites. Samizdat will let everyone publish, view, comment, edit, and aggregate text and multimedia resources, vote on ratings and classifications, filter resources by flexible sets of criteria, cooperate and coordinate on all kinds of activities (see Design Goals document for details). "
danbri: "Samizdat intends to promote values of freedom, openness, equality, and cooperation."
danbri: "Samizdat builds its underlying data model on RDF (Resource Description Framework), and defines a schema of resource classes and properties for core concepts of a Samizdat site: member, message, thread, tag, proposition, vote, version, part, and so on (see Concepts document). "
danbri: "Open nature of RDF allows to add new metadata and new uses of site resources without effort, and to transparently interoperate with diverse set of applications supporting this standard."
danbri: "It differs from other advanced open publishing engines, such as Active2 or MirCode, in that it uses RDF model from the ground up and targets other domains beyond publishing, such as coordination, education, and material items exchange."
danbri: OK I'm motivated to work on packaging rubyrdf stuff now...
danbri: "Samizdat intends to promote values of freedom, openness, equality, and cooperation."
danbri: "Samizdat builds its underlying data model on RDF (Resource Description Framework), and defines a schema of resource classes and properties for core concepts of a Samizdat site: member, message, thread, tag, proposition, vote, version, part, and so on (see Concepts document). "
danbri: "Open nature of RDF allows to add new metadata and new uses of site resources without effort, and to transparently interoperate with diverse set of applications supporting this standard."
danbri: "It differs from other advanced open publishing engines, such as Active2 or MirCode, in that it uses RDF model from the ground up and targets other domains beyond publishing, such as coordination, education, and material items exchange."
danbri: OK I'm motivated to work on packaging rubyrdf stuff now...
danbri: "I've been trying to come up with a good example to demonstrate Topicalla, since I'm not sure if people know exactly what it's supposed to do."
danbri: "So far, I've been using RSS and FOAF as simple examples, as well as a simple movie/actor example. The former two I used because many people are familiar with them and there is a large pool of existing RSS and FOAF ready to use."
danbri: "(...) The movie data can be more graph-like, as actors are associated with different movies in various ways. One issue is getting some public domain movie information and pictures, since I think images will make the screenshots look more interesting."
danbri: I agree re pictures, they improve almost any demo, but particulary data query demos.
danbri: Re non-imdb movie info, TAP's KB has a class Actor, class Movie, and a relation hasActor between movies'n'actors
danbri: I believe it has good number of movies and actors, but little or no information in the KB about actual relations between the two.
danbri: ...so one thing anybody/somebody/nobody might do (student project?) is build a WWW interface that used TAP's constrained list of actors and movies and gave a UI for claiming "(actor) X was in (movie) Y". A little CGI should do it.
danbri: "So far, I've been using RSS and FOAF as simple examples, as well as a simple movie/actor example. The former two I used because many people are familiar with them and there is a large pool of existing RSS and FOAF ready to use."
danbri: "(...) The movie data can be more graph-like, as actors are associated with different movies in various ways. One issue is getting some public domain movie information and pictures, since I think images will make the screenshots look more interesting."
danbri: I agree re pictures, they improve almost any demo, but particulary data query demos.
danbri: Re non-imdb movie info, TAP's KB has a class Actor, class Movie, and a relation hasActor between movies'n'actors
danbri: I believe it has good number of movies and actors, but little or no information in the KB about actual relations between the two.
danbri: ...so one thing anybody/somebody/nobody might do (student project?) is build a WWW interface that used TAP's constrained list of actors and movies and gave a UI for claiming "(actor) X was in (movie) Y". A little CGI should do it.