Line 11: |
Line 11: |
| * KISS and wiki principles: | | * KISS and wiki principles: |
| ** Straight to the point. | | ** Straight to the point. |
− | ** Everything can be modified (properties, values). | + | ** Everything can be modified (properties, values). Modified property/value pairs are not deleted, but archived. |
| ** Lowering the barrier: anyone should be able to do things easily. | | ** Lowering the barrier: anyone should be able to do things easily. |
| ** Accept as much usages as we can: fields are not constrained and anyone should enter anything as a new property or a new value. Organisation will come later. | | ** Accept as much usages as we can: fields are not constrained and anyone should enter anything as a new property or a new value. Organisation will come later. |
Line 34: |
Line 34: |
| * The user enters the property (see dedicated functional use case 2.1). | | * The user enters the property (see dedicated functional use case 2.1). |
| * The user enters the value (see dedicated functional use case 2.2). | | * The user enters the value (see dedicated functional use case 2.2). |
− | * The user saves the property/value pair. | + | * The user asks the system to save the property/value pair. |
| + | * The system checks for user authentication [this part is not detailed]. |
| + | * The system saves the property/value pair, with some metadata: the date and time of modification, the version, the username, and optionally a comment. |
| + | * The system archives the old property/value pair and its metadata, if any. |
| | | |
| '''Rationale''': to discover new properties, they have to be entered by people. Open Food Facts is a project opened to any kind of editors. | | '''Rationale''': to discover new properties, they have to be entered by people. Open Food Facts is a project opened to any kind of editors. |