--- a/Readme.md	Tue Mar 31 15:32:56 2015 +0200
+++ b/Readme.md	Tue Apr 07 20:03:04 2015 +0200
@@ -48,23 +48,32 @@
 
 ## Additional/Advanced informations ##
 
-** Changing the property list : ** If you want to change the property list available to users editing/creating categories, you have to edit the following entry in config.py
+** Changing the property list : ** If you want to change the default property list available to users editing/creating categories, you have to edit the following entry in config.py
 
 * PROPERTY_LIST : My list of properties ...
 
 The list of property has a fixed structure. The property list is a dict of python dicts, each following the fixed structure:
 
-    "propertyKey" : {
+    "propertyURI" : {
         "descriptive_label_fr" : "mylabelfr",
         "descriptive_label_en" : "mylabelen",
         "object_type": "my-object-type",
         "rdflib_class": some-RDFLib-concept,
-        "object_rdflib_class": some-RDFLib-class,
+        "usable_in_editor: boolean so the property appears or not in the editor
     }
 
+* "propertyURI" is the complete URI of the property, for a rdflib property that will be the string you get when calling NAMESPACE.property.toPython()
 * "object_type" : "my-object-type",  -> either "literal", "uriref-category" or "uriref-link" at the moment
-* "rdflib_class" : some-RDFLib-concept, -> a rdflib class of some sort with its namespace, examples: SKOS.related or RDF.Type representing the predicate
-* "object_rdflib_class" : some-RDFLib-class:  -> a rdflib class representing the object, either Literal or URIRef
+* "usable_in_editor": if true, the property will appear in the editor and users will be able to apply it to categories, if false they won't be able to.
+* "rdflib_class" : some-RDFLib-concept, -> a rdflib namespaced property with its namespace, examples: SKOS.related or RDF.Type representing the predicate
+
+** Custom property list **
+
+To setup a custom set of property you need to add a properties/properties.json file in the repository that has 2 values:
+* namespace_title is the string that defines the namespace of your custom properties for this repository (not really used right now but will be useful in the future)
+* property_list is a dict that follows the exact same format as the config.py property list, of course in json format, so the propertyURI that is used as a key must be written explicitely
+
+If you make the property list evolve, don't forget to keep the old properties you don't want your users to use anymore to ensure backward compatibility. You just need to set the "usable_in_editor" key to false in the property you don't want your users to have access to. Note this won't affect existing categories with this property, but only ensure that they will be readable. Then it's up to the users to "clean up" if a deprecated property is still used.
 
 ## Testing Protocol for CatEdit (development) ##