Changes between Initial Version and Version 1 of JuergeN/Notes


Ignore:
Timestamp:
19.08.2011 20:45:13 (13 years ago)
Author:
JuergeN
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • JuergeN/Notes

    v1 v1  
     1{{{ 
     2Striked-through items have been transfered to ticket-system or elsewhere or are obsolet. 
     3}}} 
     4 
     5= Julian Priest, Wed, 3 Aug 2011 = 
     6>  
     7> hey juergen, 
     8>  
     9> thanks have installed and it all looks good. 
     10>  
     11> contacts import would be a good feature for mapping your personal 
     12> networks - and nice to not be posting it to the world! 
     13>  
     14> the html interface seems really good and reckon a .deb installer would 
     15> be a boost too. 
     16>  
     17> cheers 
     18>  
     19> /julian 
     20 
     21= Notes from 18.07.2011 jpn,jri,dgf = 
     22 * Product Name DeepaMehta 4 
     23  * ~~New DM without properties is called DM4~~ 
     24  * ~~Replace DeepaMehta 3 in Github to DeepaMehta~~ 
     25  * ~~TopicType URIs shall be changed to dm4.xxx.yyy.zzz~~ 
     26  * ~~Modulnames (e.g. TypeEditor) shall be called DeepaMehta 4 TypeEditor~~ 
     27 * Trac 
     28  * ~~Enable Email for all purposes (Notification, Account, etc.)~~ 
     29  * ~~Connect to GitHub~~ 
     30 * Is OWL useful for DeepaMehta ? 
     31  * Think about OWL when dealing with XML export 
     32 * Wording 
     33  * ~~Standard DeepaMehta Webclient is called "DeepaMehta Webclient"~~ 
     34  * ~~DeepaMehta Application Framework is called "DeepaMehta Server"~~ 
     35  * DeepaMehta Components are called "DeepaMehta REST Server, DeepaMehta CORE Server, etc." 
     36  * OSGi Bundle = Maven Modul = DeepaMehta Plugin 
     37  * There may be a special DeepaMehta Desktop Edition in the future 
     38  * ~~Rename DeepaMehta Server Plugin to DeepaMehta Webservice Plugin~~ 
     39  
     40 
     41= Notes from 16.07.2011 = 
     42 * ~~Define Words for DeepaMehta Application Server and DeepaMehta Standard GUI to clearify~~ 
     43 * Write Documentation 
     44 * ~~Clearify License Terms and Fullfillment in distribution!~~ 
     45 
     46 
     47= Notes from Gilleleje 09./10.07.2011 = 
     48 * HTML5 approach for user-interface is the right direction 
     49 * A text based interface would be cool for testing (Eclipse?) 
     50 * What can we learn from LDAP especially in terms of LDIF and syncronisation? 
     51 * We need a glossary. What is a workspace (=domain?)  
     52 * Associations may also be functions or transformations. How could this be handled in the user-interface? 
     53 * Workspaces could suggest predefined ACL settings like a private, family or job workspace 
     54 * What hooks do we need? cron, timer, event handler ...  
     55 * Can we use OWL? What would be missing? 
     56 * Describe a valid file for ObjectClass, AssociationType and their instances 
     57 * Binary Content shall be stored in filesystem or in database like Couche-DB (including full-text index and versioning) 
     58 * make concept for versioning (of content) 
     59 * Define more pre-defined edges (like order or critical path) 
     60 * change edges to Bezier curves 
     61 * adding weight to edges could be useful 
     62 * Do we switch to a new Version Name DeepaMehta 4? 
     63 
     64== Urgently Missing Concepts for Operational Platform == 
     65 
     66== Security Concept == 
     67Especially today with all the myfaces and other social networks out there, the sensitivity for data security is widely rising. Not just for that reason, but also because it is my personal precondition, I want DeepaMehta to be a very secure application. Therefore I think that the following concepts should all go into the core of DeepaMehta and no workarround should be implemented at any time or for any reason. In a later version we might even implement a GPG like public private key data encryption. 
     68 
     69 
     70=== User Concept === 
     71 
     72Every operation in DeepaMehta should be done by an identified user. Users (and groups) should be handled through UID (and GID) 
     73 
     74 
     75{{{ 
     76 SYSTEM 
     77   | 
     78  root  
     79   | 
     80  user(n) 
     81   | 
     82 anonymous 
     83   | 
     84 nobody(?) 
     85}}} 
     86 
     87Every user should have their own group (like in UNIX) 
     88 
     89=== Secure Passwords === 
     90 
     91Passwords should be stored securely, hashes with salt etc. (do research) 
     92 
     93=== Operations === 
     94 
     95Which operations does the server offer/allow on objects and associations? 
     96We need to define a list of valid operations for Topics Associations and ~Types. Those are: 
     97 * create (createTopic / createAssociation / createTopicType / createAssociationType) 
     98 * update/modify 
     99 * delete 
     100 * get/read (by ID/Value) 
     101 * search/scan 
     102 * navigate (what's related?) 
     103 * still missing: equals/compare(true/false) 
     104 
     105=== Roles === 
     106 
     107Valid operations should be defined/idenfied through roles (via Tokens), like 
     108 
     109 * SYSTEM 
     110 * administrator 
     111 * creator 
     112 * owner 
     113 * member (workspace) 
     114 * peer/manager/editor 
     115 * everyone (=every user) 
     116 * anonymous 
     117 
     118Roles should be assined to users and groups. 
     119 
     120 
     121=== Attributes === 
     122Every object should have a set of inherent attributes ( which may be properties or associations), e.g. 
     123 * create time 
     124 * modify time 
     125 * access time 
     126 * not property: creator -> association 
     127 * not property: owner -> association 
     128 * ro 
     129 * not property: hidden -> association (viewable e.g. based on context) 
     130 * private (interface shortcut for ACL) 
     131 * isolated (=object cannot be associated) (insterface shortcut for ACL) 
     132 * not property: label -> association -> name/label 
     133 
     134=== Access Control Lists === 
     135Every object (nodes and edges) shall have inherent ACLs (properties) to define permissions on this object.  
     136 * Group A: read only (ro) 
     137 * Group B: read write (rw) incl. delete 
     138 * everyone: read only (ro) 
     139 * user(n): associate (a) (create an association towards this object) 
     140 
     141Questions: How do ACLs relate to edges? May one see the association to a hidden object? 
     142 
     143ACLs can be set on user and group level. 
     144 
     145=== Operation Control List === 
     146Especially for TopicType and WorkSpace, we need to define who may do what by role and operation on the object. It defines e.g if  user may create or search an instance of an object, user may join a certain workspace, create (and send) an email (function) or in general who may use domain specific functions.   
     147The operation is to a certain role:  
     148  
     149 * role: operation 
     150 * member: createInstance  
     151 
     152=== Locations === 
     153 
     154Operations could be limited through location address (localhost, 192.168.0.1, etc.), Just like in Apache or 'MySQL' 
     155Location shall be part of the Token to allow certain operations only from localhost, or IP XXX.YYY.ZZZ.ABC 
     156e.g. when uploading a file it is important to know if you work on localhost (just add a link) or if working on a remote server then open upload dialogue. 
     157 
     158=== Token === 
     159 
     160Server creates Token for user and validates the token (like Kerberos or OpenAuth).