GSoC 2011 Proposal for Drupal : Porting Neologism to Drupal 7

I support Drupal’s vision to become the best CMS in projects related to Semantic web.

In view of the above initiative, Drupal 7 comes with a core RDF module. There is a contributed RDF module as well which allows us to extend the functionality of the core module through :
1. RDFx – Provides additional serialization formats.
2. RDF-UI – UI to specify RDF Mappings.
3. Evoc    – UI to import Vocabularies and store them in DB.

For different sites to have perfectly interoperable RDF, they should use the same RDF vocabulary. It is a fact that presently no comprehensive vocabulary exists which can provide predicates to suit each and every Semantic web-development project. For instance, foaf may be a very good choice of RDF vocabulary when it comes to building social networking web-sites. However, if one wants to create a project which involves Learning Resource Objects, foaf would not be able to provide predicates for all the Learning object metadata elements. That’s why it’s important to be able to create new vocabularies according to the specific requirements of the project.

As of now, there is no standard User interface for creating an entire RDF Vocabulary in Drupal 7. One has to write an RDF Schema in XML format and then register it with Drupal using Evoc.

My initial idea :

I initially wanted to extend the functionality of the Contributed RDF Module by adding a User Interface to “create” and “register” customised RDF-vocabularies. The module would generate the corresponding RDFS in backend and allow the user to register the vocabulary with the Drupal and provide an easy UI for creating the vocabularies in the frontend.

Why I felt the Need for this extension :

Since the Drupal has a relatively steep learning curve, we must try to make things as easy as possible for the newbies so that more and more people can enthusiastically join Drupal’s Semantic initiative and start using Drupal for their Semantic Web Projects.

Using the User Interface that I planned to develop, someone with even a little knowledge of writing an RDF Schema would be able to create and register his own vocabulary.

Change of Plans :

I thus went ahead and posted my proposal on GSoC-11 Drupal Group.

As you can see here(, the discussions turned out to be very fruitful indeed. Lin Clark advised me to have a look at the ongoing Neologism Project(, which provided a free and open-source vocabulary publishing platform. It turned out to be functionally very similar to what I had planned for my project. However, Neologism is not yet available as a module for Drupal 7, Lin also advised me to get in touch with Richard Cyganiak (, who was actively working on Neologism development.

Neologism is a powerful codebase for publishing customised vocabularies that is already in quite some use in the RDF community, but using it in existing Drupal sites is difficult since there is no dedicated D7 Module. Moreover, the code is hosted on Google Code Repositories. To confuse matters further, there is a very old version of the neologism module on, which was not updated as the project progressed on Google Code. It also has several dependencies, a few of which are not even easily available on the internet since the previously existing links are now broken. So there was scope of collaboration.

I contacted Richard and we discussed my project proposal over several emails. Richard informed me that he would soon be working to port Neologism to D7. I offered to do it as a part of my GSoC project. I felt it was better to contribute to Neologism module rather than creating another module from scratch which overlaps in functionality with the upcoming Neologism module. Moreover, Neologism has many good features like a vocabulary overview diagram and a time tested User Interface, due to which it makes even more sense to port it to D7. Richard liked the idea of pooling our resources to work for a common cause. He also agreed to mentor the project.

Finally, we came up with the following abstract for the project :

  1. Porting Neologism to D7
  2. Migrating the Neologism code-base and documentation from Google Code to
  3. Updating the documentation and informing existing users about the change.
  4. Testing that the Neologism module works well in existing D7 sites
I intend to carry forward the work that has already been put into creating the Neologism vocabulary publishing platform by porting it to D7 and making it available to the huge Drupal community and any existing Drupal sites that want to use RDF with custom vocabularies.

At this moment, I believe that that the Evoc module in D7 provides all the features that we need to successfully create the Neologism module.

Timeline for the Proposed Project:

April 25 – May 23 (Before official coding period starts) [Information Learning Curve and Background readings]
  • Familiarise with the current Neologism codebase and Drupal RDF modules.
  • Go through the current documentation of the Neologism project.
  • Discuss the implementation plans and risks with the mentors.
  • Familiarise the coding standards and development practices followed while creating Drupal modules.
  • Get used to working on the Drupal Repositories since code migration from Google code to Drupal repositories would also be a part of the SoC project.

May 23 – 29 (First week) [Familiarizing]

  • Fix some bugs/implement simple features for the current Neologism platform to familiarize further with the codebase.
  • Create a document for general reference which describes how the module would appear at the end of the Summer of Code. Documentation at this stage would not go into the technical details but only describe how the module would appear to the end user at the end of the project.

May 30 – June 5 (1 week) [DB Migration]
Neologism is currently running on D6. There are a lot of differences between the Evoc module in D6 and D7. Thus, we need to change the DB Schema of Neologism to match the D7 Version of Evoc.

This marks the End of Phase-1.
At this moment, we are ready to start porting Neologism to D7.

June 6 – July 24 (7 weeks)[Porting Neologism to D7]
This is the major task of the project. This task has been further divided into sub-tasks as follows :
Week 1 : Port the menu system and vocabulary list to D7

Week 2 : Port the vocabulary overview page to D7
Week 3 : Port the RDF output to D7
Week 4 : Provide the feature of importing and loading vocabulary by using the evoc module
Week 5 : Port the vocabulary creation/edit form to D7
Week 6 : Port the class/property creation/edit forms to D7
Week 7 : Port content negotiation and caching to D7

Also, during this period, I would need to carry out integration testing for the module.

This marks the end of Phase 2.
At this stage, we have a functional D7 port of Neologism module.

July 25 – July 31 (1 week) [Documentation Migration/Upgrading and Migrating the code to Drupal Repository]
The tasks planned for this phase are as following :
  • Set up infrastructure for neologism module
  • Coordinate with documentation team to move existing documentation to   
  • Update documentation wherever needed
  • Notify existing users of the changes

August 1 – August 7 (1 week) [Test the module on existing Drupal sites]We would need to evaluate how the Neologism module works if installed into existing D7 sites and identify any issues. Currently Neologism is built as an installation profile which installs an entire site that provides just a vocabulary editor. There might be some initialization which was previously done during the installation procedure which would now need to be done when the Neologism module is installed into existing sites. We need to make sure there are no issues faced when the module is installed or reinstalled into existing D7 sites.

August 8 – August 14 (1 week) [Buffer period]

Buffer for general Neologism bugfixing/improvements as identified throughout the project

August 15 – GSoC Ends.
End of Phase 3.

Deliverables :

  • A functional D7 Port of Neologism, which isntalls on existing sites without any major issues.
  • Updated Documentation of Neologism.
  • Documentation of the status of the module at the end of GSoC completes and the plan of action for the future.
  • List of known issues in the module.

Link to Discussion created in on Drupal Groups

I had already planned my idea well before GSoC. Thus, I was quick to draft my proposal initially on the Drupal GSoC-11 Group. You may find the discussion here :

I also asked the members of the Semantic Web Group in Drupal-Groups to provide me feedback on my proposal.

On the IRC Channels of drupal, (drupalcommerce and drupal-contribute) I got the opportunity to discuss my idea with a few people who provided me with useful bits of information and guidance.


I tried to contact the people who have been actively involved with the development of RDF and related Modules in Drupal 7. Lin Clark(linclark) (, suggested I get in touch with Richard Cyganiak (cygri) (, for mentoring me on my project since it relates to the Neologism project( he had started and has been working on. I contacted Richard and he generously agreed to mentor me on my GSoC project.

Lin Clark (linclark) has offered to help me during the first few weeks to learn the customs of using issue queue and creating clean patches.

Guido Cecilio, (guidocecilio) who is the current main developer of Neologism, will also be available to answer questions regarding Neologism code and coordinate his work with me.

Stephane Corlosquet (scor) has agreed to help by answering questions regarding D6 to D7 migration.

Thus, I have the overwhelming support of the Drupal community to assist me during the course of my project.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: