Implementing the basic, default, entities revisioning system into the structFieldStorage module. We can now create and delete revisions for the fields that are saved into structWSF.

We also added a new setting to be able to map all the fields, including the ones that doesn't use the structfieldstorage storage type. This new setting is used in a data migration workflow.

Change the behavior of the RDF MAPPING section. Now, if the field type/widget is referring to another entity, then we will autocomplete on the list of owl:ObjectProperty from the ontologies. Otherwise, we will continue to display owl:DatatypeProperty and owl:AnnotationProperty to them.

The current field types/widgets that uses object properties are:

 (1) entityreference
 (2) Text with the struct_lookup_field widget
 (3) Text with the struct_lookup_field_with_scones_suggest widget

(1) direct the user to structOntology from the RDF MAPPING section to create new properties if required
(2) in the RDF MAPPING section, only return Annotation & Datatype properties to the user for now since there is no mechanism to create URIs from the Content Type forms for now

Creation of the two synchronization procedures used to synchronize Content Type schemas (bundles and fields) changes for the data that resides into the structWSF instance:

  * structfieldstorage_synchronize_bundles_changes()
  * structfieldstorage_synchronize_fields_changes()

   (a) Make sure that Title and Body are automatically mapped to iron:prefLabel and iron:description
   (b) Make sure that only the structfieldstorage fields are mapped to RDF. Ignore others
(2) In structfieldstorage_admin_rdf_overview_form()
    (a) Make sure that only the structfieldstorage fields are displayed in that list

First working prototype of the structFieldStorage module that is used to replace the default storage system of the content type entities.