Hello everyone,
This is to announce the first release of my Google Summer of Code 2014 Project. You can download the module from https://www.drupal.org/project/rdfui
A screencast, covering all the features of the modules, is also available.
The project RDF UI consists of two modules, RDF UI and RDF UI Builder. As explained in my previous post https://groups.drupal.org/node/424838 the project contains two tools to integrate Schema.org mappings to Drupal 8. RDF UI module contains the 'Schema.org mapping tool', while RDF UI Builder module is for Schema.org-driven Content type builder. The module are tested for Drupal 8-alpha14.
I will keep updating the module and improving it with new features. Feel free to contact me on any issues regarding the module. All suggestion and complaints are warmly welcome. (Issue queue)
A Big Thanks goes out to my mentors Stéphane Corlosquet (scor), Kevin O’Leary and Drupal Community. GSoC with Drupal is really a great experience!
Comments
Fantastic work!
Thanks Sachini for all your work, you've done an amazing job during your Google Summer of Code term. I hope you can continue to contribute your ideas and your code to Drupal beyond the duration of this year's GSoC.
Thanks for the great work, that makes it much easier for ...
Hi Sachini,
Thanks for the great work, that makes it much easier for non-SemWeb-Geeks to add meaningful RDF mappings (and sets of fields) to their content types.
Watching your screencast, I wonder if you think about handling the case too when the target of a property is an object itself - for example the schema:performer of a schema:SportsEvent, which according to http://schema.org/SportsEvent should be a schema:Person or schema:Organization. The type schema:Person - and perhaps even the data - are already present in your example system! In other cases (like schema:Location Brazil) you may want to add it from a source like Geonames.
So that would mean beeing able to reference an URI instead of inserting a string value, and - in a perfect world - to select it from a list of suggestions. Are such things in your plans?
Cheers, Joachim
That's a great suggestion
That's a great suggestion Joachim.
I think this would mean that a Content Type should have a set of Content types as properties.
No I did not have that in my plans, but I would definitely consider implementing it.
Sachini
Hi Joachim, These are great
Hi Joachim,
These are great ideas. I purposely left them out of scope for the project, since I first wanted to have a basic workflow working at the end of the GSoC project. To achieve the kind of feature you describe will require several steps in the setup, and more UX work. Feel free to start discussing this in the issue queue directly so we can start tracking the different use cases that people want to see.