Changes

Jump to navigation Jump to search
Case 2.3 (documentation)
Line 64: Line 64:  
* The system returns:
 
* The system returns:
 
** The list of all products using this property; for each product: the product's barcode, optionally the product name, the product's photo, the last modification date, the editor of the property, the value.
 
** The list of all products using this property; for each product: the product's barcode, optionally the product name, the product's photo, the last modification date, the editor of the property, the value.
** The link to the property's documentation.
+
** The link to the property's ation.
    
'''Rationale''': the list of products with a particular property allows:
 
'''Rationale''': the list of products with a particular property allows:
Line 78: Line 78:  
* The system returns:
 
* The system returns:
 
** The list of all products using this property; for each product: the product's barcode, optionally the product name, the product's photo, the last modification date, the editor of the property.
 
** The list of all products using this property; for each product: the product's barcode, optionally the product name, the product's photo, the last modification date, the editor of the property.
** The link to the property's documentation.
+
** The link to the property's ation.
    
'''Rationale''': this use case allows hundreds of new usages; eg. listing all the products that have been recalled last month; all products that are blue; etc.
 
'''Rationale''': this use case allows hundreds of new usages; eg. listing all the products that have been recalled last month; all products that are blue; etc.
Line 98: Line 98:  
* The system suggests back all properties containing these letters (beginning at the second letter).
 
* The system suggests back all properties containing these letters (beginning at the second letter).
 
* The user selects a property or continues to type.
 
* The user selects a property or continues to type.
 +
* If the property is a new one, the system informs the user about social aspects of property creation: documentation, values, reuse, etc. It encourages the user to write the documentation of the new property, providing him the automatic link to the documentation.
 +
* Eventually the user documents the property (see 2.3).
 
* Back to use case 2.
 
* Back to use case 2.
   Line 107: Line 109:  
* The user selects a value or continues to type.
 
* The user selects a value or continues to type.
 
* Back to use case 2.
 
* Back to use case 2.
 +
 +
== 2.3 The user documents the property ==
 +
[TODO]
 +
 +
* The system shows the dedicated documentation page for the given property.
 +
* The user can specify:
 +
** usages
 +
** values
 +
** See also
 +
** the category
 +
** [to be completed]
    
== Questions ==
 
== Questions ==
   −
* For transparency reasons (and maybe for other reasons):
+
* For '''transparency''' reasons (and maybe for other reasons):
 
** Should we provide a use case to let the user see the history of property/value pairs for each product? Version 2?
 
** Should we provide a use case to let the user see the history of property/value pairs for each product? Version 2?
** Should we provide a use case to let the users see the history of all property/value pairs for all product(something like the "recent changes" in Mediawiki/Wikipedia)? Version 2?
+
** Should we provide a use case to let the users see the history of all property/value pairs for all product (something like the "recent changes" in Mediawiki/Wikipedia)? Version 2?
* Should we immediately provide use cases related to private property/value pairs?
+
* Should we immediately provide use cases related to '''private property/value pairs''' for V1?
 +
** Eg. my_morning_diet=yes;
 
** Should these use cases take care of stocks issues?
 
** Should these use cases take care of stocks issues?
 +
** Could public properties be used privately?
 +
*** CONs: one can build a big private database with Open Food Facts resources.
 +
** Could private properties be used publically?
 +
** If private properties can only be used privately, should we clearly separate them from the private ones:
 +
*** Show another section in the product page?
 +
*** Name them to ensure they are private; eg. private:my_prefered_product=yes
 +
** Should private properties be documented as well as public properties?
 +
** Should some properties be necessarily private? Eg. our_prefered_product=yes
 +
** Should the property suggestion take care of private properties?
 +
** Should we adopt some limits to private usage? (to take care of common resources)
 +
*** How would it look like? Max number of property/value pairs?
 +
* Should we take care of '''stock issues''' for V1?
 +
** Eg. I have three items of this product, one ending 2021-10-10, and two ending 2021-10-31.
 +
* When a new property is created, we need to inform user about social aspects of property creation: documentation, values, reuse, etc.
 +
* Synonyms of a property.?
 
[[Category:Folksonomy Engine]]
 
[[Category:Folksonomy Engine]]

Navigation menu