Skip to main content

Home/ Future of the Web/ Group items tagged roadmap

Rss Feed Group items tagged

Paul Merrell

Transparency Toolkit - 0 views

  • About Transparency Toolkit We need information about governments, companies, and other institutions to uncover corruption, human rights abuses, and civil liberties violations. Unfortunately, the information provided by most transparency initiatives today is difficult to understand and incomplete. Transparency Toolkit is an open source web application where journalists, activists, or anyone can chain together tools to rapidly collect, combine, visualize, and analyze documents and data. For example, Transparency Toolkit can be used to get data on all of a legislator’s actions in congress (votes, bills sponsored, etc.), get data on the fundraising parties a legislator attends, combine that data, and show it on a timeline to find correlations between actions in congress and parties attended. It could also be used to extract all locations from a document and plot them on a map where each point is linked to where the location was mentioned in the document.
  • Analysis Platform On the analysis platform, users can add steps to the analysis process. These steps chain together the tools, so someone could scrape data, upload a document, crossreference that with the scraped data, and then visualize the result all in less than a minute with little technical knowledge. Some of the tools allow users to specify input, but when this is not the case the output of the last step is the input of the next. Tools Existing and planned Transparency Toolkit tools include include scrapers and APIs for accessing data, format converters, extraction tools (for dates, names, locations, numbers), tools for crossreferencing and merging data, visualizations (maps, timelines, network graphs, maps), and pattern and trend detecting tools. These tools are designed to work in many cases rather than a single specific situation. The tools can be linked together on Transparency Toolkit, but they are also available individually. Where possible, we build our tools off of existing open source software. Road Map You can see the plans for future development of Transparency Toolkit here.
  •  
    If you think this isn't a tool for some very serious research, check the short descriptions of the modules here. https://github.com/transparencytoolkit I'll be installing this and doing some test-driving soon. From the source files, the glue for the tools seems to be Ruby on Rails. The development roadmap linked from the last word on this About page is also highly instructive. It ranks among the most detailed dev roadmaps I have ever seen. Notice that it is classified by milestones with scheduled work periods, giving specific date ranges for achievement. Even given the inevitable need to alter the schedule for unforeseen problems, this is a very aggressive (not quite the word I want) development plan and schedule. And the planned changes look to be super-useful, including a lot of "make it easier for the user" changes.   
Gonzalo San Gil, PhD.

What's in the new Digital Single Market Strategy from the EU for open source? | Opensou... - 0 views

  •  
    "After months of preparation, the European Commission (EC) released its broad 5-year roadmap in early May for information and communications technology (ICT) policy, the Digital Single Market Strategy, or DSM."
Gary Edwards

Brendan's Roadmap Updates: Open letter to Microsoft's Chris Wilson and their fight to s... - 0 views

  • The history of ECMAScript since its beginnings in November 1996 shows that when Microsoft was behind in the market (against Netscape in 1996-1997), it moved aggressively in the standards body to evolve standards starting with ES1 through ES3. Once Microsoft dominated the market, the last edition of the standard was left to rot -- ES3 was finished in 1999 -- and even easy-to-fix standards conformance bugs in IE JScript went unfixed for eight years (so three years to go from Edition 1 to 3, then over eight to approach Edition 4). Now that the proposed 4th edition looks like a competitive threat, the world suddenly hears in detail about all those bugs, spun as differences afflicting "JavaScript" that should inform a new standard.
  • In my opinion the notion that we need to add features so that ajax programming would be easier is plain wrong. ajax is a hack and also the notion of a webapp is a hack. the web was created in a document centric view. All w3c standards are also based on the same document notion. The heart of the web, the HTTP protocol is designed to support a web of documents and as such is stateless. the proper solution, IMO, is not to evolve ES for the benefit of ajax and webapps, but rather generalize the notion of a document browser that connects to a web of documents to a general purpose client engine that connects to a network of internet applications. thus the current web (document) browser just becomes one such internet application.
  •  
    the obvious conflict of interest between the standards-based web and proprietary platforms advanced by Microsoft, and the rationales for keeping the web's client-side programming language small while the proprietary platforms rapidly evolve support for large languages, does not help maintain the fiction that only clashing high-level philosophies are involved here. Readers may not know that Ecma has no provision for "minor releases" of its standards, so any ES3.1 that was approved by TG1 would inevitably be given a whole edition number, presumably becoming the 4th Edition of ECMAScript. This is obviously contentious given all the years that the majority of TG1, sometimes even apparently including Microsoft representatives, has worked on ES4, and the developer expectations set by this long-standing effort. A history of Microsoft's post-ES3 involvement in the ECMAScript standard group, leading up to the overt split in TG1 in March, is summarized here. The history of ECMAScript since its beginnings in November 1996 shows that when Microsoft was behind in the market (against Netscape in 1996-1997), it moved aggressively in the standards body to evolve standards starting with ES1 through ES3. Once Microsoft dominated the market, the last edition of the standard was left to rot -- ES3 was finished in 1999 -- and even easy-to-fix standards conformance bugs in IE JScript went unfixed for eight years (so three years to go from Edition 1 to 3, then over eight to approach Edition 4). Now that the proposed 4th edition looks like a competitive threat, the world suddenly hears in detail about all those bugs, spun as differences afflicting "JavaScript" that should inform a new standard.
Paul Merrell

Cox Lays Out Gigabit Roadmap | Light Reading - 0 views

  • Following up on its announcement at The Cable Show last month, Cox Communications is now offering more detail on the company's pending rollout of gigabit broadband services throughout its territories. (See Cox Goes for a Gigabit .) Cox Communications Inc. is targeting Phoenix, Las Vegas, and Omaha as its first new gigabit markets and plans to begin deployments across its entire footprint by the end of 2016. In addition to residential home service, the company will offer gigabit connectivity to select condominiums and apartments and will expand WiFi service both in common areas of those multi-dwelling units (MDU) and in public locations across the Phoenix and Las Vegas metro areas. The announcement by Cox, the first major North American MSO to make a 1-Gig commitment throughout its footprint, follows a recent pattern of competitive announcements from broadband service providers. Typically, one operator introduces or says it will explore delivery of higher broadband speeds, and then other local providers rapidly follow suit. In February, for instance, Google Fiber Inc. said it would look at expanding fiber service to 34 new cities, including Phoenix, where it will compete against Cox for the first time. (See Google Fiber Shifts Into High Gear.)
  • At the same time, CenturyLink Inc. (NYSE: CTL) began offering gigabit service in Las Vegas last fall and in Omaha last May, putting Cox on the hot seat in those two markets as well. This isn't Cox's first venture into gigabit broadband service. In addition to providing gigabit connections to commercial customers, the operator started a fiber-to-the-home trial service in Orange County, Calif. last year. For the company's upcoming deployments, a spokesperson noted that Cox hasn't yet specified which technologies it will use, but said that it will rely on portions of Cox's existing network in addition to newer fiber infrastructure.
Paul Merrell

Collaboration and Content Strategies Blog: Lotus Symphony: Looking to Go Beyond Playing... - 0 views

  • IBM Lotus had several presentations on Lotus Symphony this year.
  • However, IBM Lotus is becoming a bit more outspoken about their future plans. On slide 5 of the IBM Lotus Symphony Overview (presentation ID506), the company portrayed a pyramid with five tiers, with an arrow pointing up the pyramid stating, "Over time, investment will shift."
  • The interesting one is number five: Beyond Office is the idea that Symphony should become part of an ecosystem that makes composite documents, similar to what the DITA standard allows for technical documentation.
1 - 5 of 5
Showing 20 items per page