XWiki Help Desk Data Model Proposal of a preliminary data model/ The terms "Issue" and "IssueLog" are used preferably to "Question" and "Answer" since the help desk concepts are very close to the ones of an issue tracker, and using a common data model for both may be handy. Issue Title Description Language

= XWiki Help Desk Data Model = Proposal of a preliminary data model/ The terms "Issue" and "IssueLog" are used preferably to "Question" and "Answer" since the help desk concepts are very close to the ones of an issue tracker, and using a common data model for both may be handy. |=Issue |Title

) further introduces the concept of shareable nodes which allows multiple paths of access to a node

the concept of journaled listeners which can ask the repository to re-play all events after a certain

. JSR283 hence introduces the (optional) concept of shareable nodes. This allows implementing multiple

://whiteboardjunkie.wordpress.com/2008/11/24/where-am-i-using-jcr-and-why/] * JSR 283 (JCR 2.0) further introduces the concept

navigations through content * JSR 283 further introduces the concept of journaled listeners which can ask

) concept of shareable nodes. This allows implementing multiple URIs for a given model object

on the old cache services concepts even all the names changes but the more I'm working with JBoss cache

eviction algorithms concept like JBoss or cache4j do to replace the way restriction like capacity

on the old cache services concepts even all the names changes but the more I'm working with JBoss cache

thinking of introduce eviction algorithms concept like JBoss or cache4j do to replace the way restriction

workspace. Users have the possibility to enhance the public graphs locally by adding concepts and relations

on a view concept for the tailoring of ontologies. This view concept turned out to be of additional value

to enhance the public graphs locally by adding concepts and relations that make sense to them, involving

. It is also based on a view concept for the tailoring of ontologies. This view concept turned out

. * Skin extensions sounds like an afterthought. I wonder if we cannot somehow merge the concepts together

if we cannot somehow merge the concepts together. I guess I'd need to see some examples

needs to be easy to use for newcomes and people lowly familiar with the concept of a wiki ** Speed : how

://enterprise.xwiki.org/xwiki/bin/view/Main/Features MILESTONE 1: Clear concept of what is to be coded/written http

/view/Main/Features]] **MILESTONE 1: Clear concept of what is to be coded/written** [[http

architecture using a Component Manager * Each component group (set of components for implementing a concept

concept used in this proposal. Private keys, Public keys and Passphrases To encrypt data, a mathematical

concepts as much as possible: Integrity checks: process of checking a signature, and extracting

concept used in this proposal. == Private keys, Public keys and Passphrases == To encrypt data

will not be possible. To achieve those goals, the implementation will separate the following concepts as much