11 Matching Annotations
  1. Oct 2017
    1. The use of the MVC pattern in web applications exploded in popularity after the introduction of Apple's WebObjects in 1996, which was originally written in Objective-C (that borrowed heavily from Smalltalk) and helped enforce MVC principles. Later, the MVC pattern became popular with Java developers when WebObjects was ported to Java. Later frameworks for Java, such as Spring (released in October 2002), continued the strong bond between Java and MVC. The introduction of the frameworks Django (July 2005, for Python) and Rails (December 2005, for Ruby), both of which had a strong emphasis on rapid deployment, increased MVC's popularity outside the traditional enterprise environment in which it has long been popular. MVC web frameworks now hold large market-shares relative to non-MVC web toolkits.[14]

      A bit of history and relation with Smalltalk.

    2. Some web MVC frameworks take a thin client approach that places almost the entire model, view and controller logic on the server. This is reflected in frameworks such as Django, Rails and ASP.NET MVC. In this approach, the client sends either hyperlink requests or form submissions to the controller and then

      Some ideas related to specific frameworks Django, Rails and ASP.NET

  2. Sep 2017
    1. Aid in Danger Security in Numbers Database

      There is not specific information about this Database in the Aid in Danger or Insecurity Insight Websites. A report from Insecurity Insight explained that "summarises selected findings from the Aid in Danger Monthly News Briefs, which are based on open-source monitoring." [1] but is not clear how the ngos or general public will have access to the data and what they understand by opensource.

      When data is collected under open-source licenses, the license is usually displayed in the website, establishing clearly how the data can be accessed and by who.

      • Humanitarian Data Exchange contains only two very basic datasets in excel format from Insecurity Insight. I think. They are not particularly a good example for information analysis.

      In regards to the section, it is not possible for the reader to compare its collected data with any system that exemplifies how the data can be analyzed.

      • On the other side, The AWSD can be a good example for big ngos about how to store and maintain a big database with security events. Probably interesting to make a mention in the book and share the link . https://aidworkersecurity.org/about

      [1] http://www.insecurityinsight.org/aidindanger/wp-content/uploads/2017/08/AiD-Incident-Trends-KIK-incidents-Jan-Jun-2017.pdf?mc_cid=11d4c4644f&mc_eid=ab91e71a1b

    2. Not analysed
      • DATA PROTECTION - It seems confusing, I'm not sure if this refers to what platform has backup capabilities. In any case is very important to know how the data is licensed when captured inside the platform, meaning Who has the right to access it: The platform holder, the company who made the platform or the NGO. (In

      Example, is Microsoft able to access the information stored in the free version of Sharepoint 360 that is distributed to ngos? Not even for statistics purposes?) Or If the user od SIMSON wants to remove the data, is the data completely removed or the platform will keep a copy for their own use?

      I don't see the value of having a criteria sections where non of the platforms has been analyzed about.

    3. See the table below for a comparison of some online incident reporting systems.

      I miss a sort explanation about the definition of the different criteria, although some of them are detailed in Chapter4.

      • LICENSED its not opposite to OPEN SOURCE. In fact, all the Open Source platforms are licensed with specific licenses, ie. GPL, MIT,..etc (https://en.wikipedia.org/wiki/Open-source_license)

      • OPEN SOURCE is not the same as FREE. This can lead misunderstanding. (https://opensource.com/business/16/11/open-source-not-free-software)

      • It seems STANDARD and TAILOR-MADE are considered as opposite in this table. I find it confusing as, ie all the Open Source platforms, by definition, can be completely tailored by the end-user. On the other side, products like Sharepoint, where not tailored are highly customable.

      I expected the table to contain the following extra criteria:

      • DATA LICENSE and OWNERSHIP- When NGO submits the data into this platforms, Who owns the data, and who is responsible of the data?
      • DATASET FORMAT: How the data is stored in the platform?: Is it in excel files/format, csv, database (Sql, sqlite, json private formats), Is the information "structured or not? . Dataset format is an important point in order to choose what Visualization and Analysis Technology we could implement later to extract information from this data.

      • ANALYSIS AND VISUALIZATION CAPABILITIES: Does the Template includes Visualization and Data Analysis Tools?. I see some of them includes Geo-positioning of events in a world-map, but is that all? what about tools that navigates the data and show graphs comparing different events?

    4. Requires a very manual trend analysis

      The key idea behind this is related to having structured data -vs- unstructured data. With unstructured data, there is difficult to perform correct data analysis.