Search: concept

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

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

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

keywords. Note: could reuse the "Types" concept here maybe, with a built-in type "SPAM" that would

particular keywords. Note: could reuse the "Types" concept here maybe, with a built-in type "SPAM" that would

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

) This concept is to replace (in a lazy way) initial HTML by a richer HTML. What I mean by richer? In order

, expanding the DocumentName concept) Annotation model changes to store such a reference to a field

? === ==== Solution n°1 : Richer HTML (not used) ==== This concept is to replace (in a lazy way) initial HTML

will be devised (for example, expanding the DocumentName concept) * Annotation model changes to store

, PatchId toPatch) /** do we need to introduce a concept of dependencies between patches? */ Iterator

://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

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

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