Requirements-analysis

From IKS Project

This requirements analysis discusses the collection of requirements obtained from the IKS partners during the Rome' meeting on Requirements Capturing (23-25 March 2009).

Please feel free to add any requirements for semantic CMS that come to mind.

*** work in progress ***

Requirements	Functional Description	Improved Semantics Description
User notification	To inform users when their content has been edited, moved…	RSS and beyond
User preferences	Ability to filter content according to the users needs	Re-use of user profiles in different CMS
Search	Standard and non-standard methods for searching (e.g. latent analysis)	Our proposed definition of ideal semantic search is: for any query give all valid answers.
Content transformation (Conversion)	Formating, channeling...	Metadata transformation
Tags	Assigning tags to content items	Tagging languages
Document types	Format and/or domain-related types of documents	The structure of the document supports certain aspects of the real world
Imaging	Character recognition	Word recognition
Relations	HREF hyperlinks and traditional CMS-related associations such as versioning, ownership definitions...	Microformats, OWL, RDF, RDFa... Creating smart content
Audit/Archive	Audit trail of users managing or archiving content	Managing audits and archiving of content according to business  rules
Intelligent content	e.g. being able to guarantee certain levels of content consistency	Keeping content consistent according to business rules
Workflow	e.g. NUXEO uses jBPM (based on BPEL)	We have to look at Semantic BPM
Directories	e.g. NUXEO uses LDAP and SQL	WebDAV and beyond (e.g. http://www.semdav.org/news.php?lang=en)
Access rights	e.g. access rights, access control lists, http://drupal.org/project/taxonomy_access   http://en.wikipedia.org/wiki/Java_Authentication_and_Authorization_Service
Replication, synchronization, scalability