Confirmed users, Bureaucrats and Sysops emeriti
1,057
edits
MDN/Archives/Projects/Development/CompatibilityTables/Vision: Difference between revisions
MDN/Archives/Projects/Development/CompatibilityTables/Vision (view source)
Revision as of 22:59, 25 September 2015
, 25 September 2015→Properties that has common attributes: more text improvements and questions
(→Which product attributes are critical to satisfying the needs selected, and therefore for the success of the product?: clarify some text, add a question or two) |
(→Properties that has common attributes: more text improvements and questions) |
||
| Line 119: | Line 119: | ||
## Convert a given ''data entry'' into a "contribution packet" to send to the API | ## Convert a given ''data entry'' into a "contribution packet" to send to the API | ||
=== Properties that | === Properties that have common attributes === | ||
Common properties should indicate the system dependencies and, therefore, makes them critical to supporting other features of the system as a whole. | Common properties should indicate the system dependencies and, therefore, makes them critical to supporting other features of the system as a whole. | ||
| Line 126: | Line 126: | ||
==== Data entry events ==== | ==== Data entry events ==== | ||
As stated in ''critical attributes'' above | As stated in ''critical attributes'' above: | ||
<blockquote>Erasing contributions should adjust internal data representation as the ''sum of data entries between an initial state and the entry events applied in an ordered manner'', modulo what's been erased</blockquote> | <blockquote>Erasing contributions should adjust internal data representation as the ''sum of data entries between an initial state and the entry events applied in an ordered manner'', modulo what's been erased</blockquote> | ||
The following | The following types of data are subject to edit events, and moderation may be required on a given event. | ||
In their respective contexts | In their respective contexts: | ||
* Bulk (i.e. event data adds/edits more than one data type) | * Bulk (i.e. event data adds/edits more than one data type) | ||
* Individual entry | * Individual entry, triggered from MDN | ||
* Individual entry, triggered from external site | * Individual entry, triggered from external site | ||
* Initial import | * Initial import (''is this the first scraping of MDN? what about with the skateboard plan, where each change is a scraping? that needs to be taken into consideration'') | ||
It means we may want to focus on a system that helps us | It means we may want to focus on a system that helps us browse ''data entry'' events. This will allow rolling back to the point at which errors or other problems occurred, and should allow us to support undoing individual changes, even though others happened later, at least in many cases. | ||
==== Search ==== | ==== Search ==== | ||
Search capability is required for two different contexts: | Search capability is required for two different contexts: the current data set and the contribution event history/log. | ||
==== Compile a data view as the sum of data entries ==== | ==== Compile a data view as the sum of data entries ==== | ||
Each visualization of the data, regardless of | Each visualization of the data, regardless of its presentation format, is the result of changes that has been made on a given resource (e.g. Feature, Specification, Browser, Labels) | ||
In order to support moderation, and the underlying need to allow removal of unaccepted data, we must have a system that handles ways to apply changes in an ordered manner. | In order to support moderation, and the underlying need to allow removal of unaccepted data, we must have a system that handles ways to apply changes in an ordered manner. | ||