tnanek's sandbox: SemWeb

I am starting to work on this project. This is for a user interface for something which will be more easily done when certain other modules are updated to Drupal 7.

This is to help people create new RDF schemas for their specific use cases. Ideally, it will take one or more schemas and allow you to use them along with your own modifications to create a new custom schema.

To use an example, take the foaf schema definition. For the moment, imagine that is the only schema in existence. Lets say you wanted to extend upon the relation knows with say a student, mentor relation of teaches. Ordinarily, that would create an issue of needing to copy certain things from the schema to say potentially update it, or to just modify it for your specific use case. You are intending to use modifications of the Person for both mentor and student. And teaches implies a knows relation at the very least from student to mentor, (if it is say a class with 1000 or more students, then the reverse is not necessarily true). You should be able to clarify that your teaches relation implies a knows relation in one way or two ways, dependent on your use case, right? Why have multiple relations on one thing, when the technology could potentially support taking one thing as another thing additionally?

The ultimate goal, put as simply as possible, is to enable someone who has no knowledge of syntax for the Resource Description Framework at all to build something like the relationship extension to foaf. The main target is the RDF Schema.

My live development work is proceeding at this site. Log in information is provided on the home page, to help show permissions (anonymous has nothing, authenticated has "Access the interface", which is provided by this module.

My git commit messages are the best place to get specific info about what has been done, view-able on the commits page.