- Timestamp:
- 14 Nov 2013, 09:50:44 (11 years ago)
- Location:
- main/eko-disco-specs/trunk
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
main/eko-disco-specs/trunk/data.rst
r10742 r10743 25 25 data entities connected. Connections to other data entities contain a 26 26 relationship telling how many instances of the described entity are 27 connected to how many instances of the related entity [#]_. 28 27 connected to how many instances of the related entity. 28 29 The following relation types may occur (in both directions): 30 31 - 1:1 (one on one) 32 - n:1 (many on one) 33 - n:m (many on many) 34 - p:1 (many or none on one) 35 - p:q (many or none on many or none) 36 - p:n (many or none on many) 37 - b:1 (one or none on one) 38 39 with 40 41 - n, m element of {1, 2, ...}, 42 - p, q element of {0, 1, 2, ...} 43 - b element of {0, 1} 44 45 Examples: 46 47 1:p service-contract relation means that each service 48 offered can result in various contracts, but each contract is 49 only based on one service. 50 51 p:q user-userrole relation means that each user can have no role or 52 several roles and each role can be assigned to no user or several users. 53 54 Relations can always be read in two directions. 29 55 30 56 .. _label-contact-address: … … 96 122 people. Instead it is an abstraction used inside the system. 97 123 98 It is always created from a :ref:`label-service` 124 It is always created from a :ref:`label-service`, which tells about 99 125 the basic data, with additional parameters set that depend on the type 100 126 of :ref:`label-service` ordered. … … 107 133 108 134 Connected to: :ref:`label-service` (p:1), :ref:`label-customer` (p:1), 109 :ref:`label-contract-addon` (1:p), :ref:`label-transaction` ( p:q)135 :ref:`label-contract-addon` (1:p), :ref:`label-transaction` (1:p) 110 136 111 137 Used in the following use cases: … … 121 147 parameters. Contract addons are created by :ref:`label-contract`\ s. 122 148 123 Connected to: :ref:`label-contract` (p:1) 149 Connected to: :ref:`label-contract` (p:1), 150 :ref:`label-service` (p:1), :ref:`label-customer` (p:1), 151 :ref:`label-transaction` (1:p) 124 152 125 153 … … 311 339 312 340 Connected to: :ref:`label-customer` (p:1), :ref:`label-service` 313 (p:1) 341 (p:1), :ref:`label-contract` (p:1) 314 342 315 343 Used in the following use cases: … … 346 374 Connected to: :ref:`label-user` (p:q) 347 375 348 349 .. [#] Relation types: (1:1): one on one, (1:n): one on many, (n:1):350 many on one, (n:m): many on many, (1:p): one on many or none,351 (p:1): many or none on one, (p:q): many or none on many or none,352 (1:b): one or none on one, (b:1): none or one on one353 354 In mathematical terms:355 356 n and m are elements of {1, 2, ...},357 p and q are elements of {0, 1, 2, ...},358 b is element of {0, 1}359 360 -
main/eko-disco-specs/trunk/index.rst
r10725 r10743 4 4 contain the root `toctree` directive. 5 5 6 Portal Specifications7 ===================== 6 Eko Disco Portal Specifications 7 =============================== 8 8 9 9 .. Contents: … … 19 19 license 20 20 install 21 22 23 Indices and Tables24 ==================25 26 * :ref:`genindex`27 * :ref:`search`
Note: See TracChangeset for help on using the changeset viewer.