In the resource descriptors we have: id, label, description, permission, type, creation date, updated date, (in case of file we have file type)
This model is not very convenient, it is rigid and limited.
I propose we add properties to any resource, like most of filesystems supports.
What could be stored in this properties?
tags, we could tag resources and search by tag
we could store comments
we could keep track who currently opened the file
label, description, file type could go into properties
UUID to identify a resource, eventually made ID = UUID this allows many applications later, like keep references if something is moved
could allow different more advanced permission schemas
we could implement versioning like it is done in jackrabbit or other repositories
translations
what editor should be used
editor preferences, default values, etc.
instructions how to cache a resource (image, jrxml, report)
instructions on which JRIO node to execute a report
instructions how to execute a report
different attributes for specific use cases
Repository services should be able to search on any property.
Veaceslav Chicu
