Skip to main content

Home/ Future of the Web/ Group items tagged beginning

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

XML Production Workflows? Start with the Web and XHTML - 0 views

quod.lib.umich.edu/...n-workflows-start-with-the-web

OpenWeb XML XHTML-CSS HTML5-CSS3-JavaScript IDML

shared by Gary Edwards on 07 Nov 13 - No Cached
  • Challenges: Some Ugly Truths The challenges of building—and living with—an XML workflow are clear enough. The return on investment is a long-term proposition. Regardless of the benefits XML may provide, the starting reality is that it represents a very different way of doing things than the one we are familiar with. The Word Processing and Desktop Publishing paradigm, based on the promise of onscreen, WYSIWYG layout, is so dominant as to be practically inescapable. It has proven really hard to get from here to there, no matter how attractive XML might be on paper. A considerable amount of organizational effort and labour must be expended up front in order to realize the benefits. This is why XML is often referred to as an “investment”: you sink a bunch of time and money up front, and realize the benefits—greater flexibility, multiple output options, searching and indexing, and general futureproofing—later, over the long haul. It is not a short-term return proposition. And, of course, the returns you are able to realize from your XML investment are commensurate with what you put in up front: fine-grained, semantically rich tagging is going to give you more potential for searchability and recombination than a looser, more general-purpose approach, but it sure costs more. For instance, the Text Encoding Initiative (TEI) is the grand example of pouring enormous amounts of energy into the up-front tagging, with a very open-ended set of possibilities down the line. TEI helpfully defines a level to which most of us do not have to aspire.[5] But understanding this on a theoretical level is only part of the challenge. There are many practical issues that must be addressed. Software and labour are two of the most critical. How do you get the content into XML in the first place? Unfortunately, despite two decades of people doing SGML and XML, this remains an ugly question.
  • Practical Challenges In 2009, there is still no truly likeable—let alone standard—editing and authoring software for XML. For many (myself included), the high-water mark here was Adobe’s FrameMaker, substantially developed by the late 1990s. With no substantial market for it, it is relegated today mostly to the tech writing industry, unavailable for the Mac, and just far enough afield from the kinds of tools we use today that its adoption represents a significant hurdle. And FrameMaker was the best of the breed; most of the other software in decent circulation are programmers’ tools—the sort of things that, as Michael Tamblyn pointed out, encourage editors to drink at their desks. The labour question represents a stumbling block as well. The skill-sets and mind-sets that effective XML editors need have limited overlap with those needed by literary and more traditional production editors. The need to think of documents as machine-readable databases is not something that comes naturally to folks steeped in literary culture. In combination with the sheer time and effort that rich tagging requires, many publishers simply outsource the tagging to India, drawing a division of labour that spans oceans, to put it mildly. Once you have XML content, then what do you do with it? How do you produce books from it? Presumably, you need to be able to produce print output as well as digital formats. But while the latter are new enough to be generally XML-friendly (e-book formats being largely XML based, for instance), there aren’t any straightforward, standard ways of moving XML content into the kind of print production environments we are used to seeing. This isn’t to say that there aren’t ways of getting print—even very high-quality print—output from XML, just that most of them involve replacing your prepress staff with Java programmers.
  • Why does this have to be so hard? It’s not that XML is new, or immature, or untested. Remember that the basics have been around, and in production, since the early 1980s at least. But we have to take account of a substantial and long-running cultural disconnect between traditional editorial and production processes (the ones most of us know intimately) and the ways computing people have approached things. Interestingly, this cultural divide looked rather different in the 1970s, when publishers were looking at how to move to digital typesetting. Back then, printers and software developers could speak the same language. But that was before the ascendancy of the Desktop Publishing paradigm, which computerized the publishing industry while at the same time isolating it culturally. Those of us who learned how to do things the Quark way or the Adobe way had little in common with people who programmed databases or document-management systems. Desktop publishing technology isolated us in a smooth, self-contained universe of toolbars, grid lines, and laser proofs. So, now that the reasons to get with this program, XML, loom large, how can we bridge this long-standing divide?
  • ...44 more annotations...
  • Using the Web as a Production Platform The answer, I think, is right in front of you. The bridge is the Web, a technology and platform that is fundamentally based on XML, and which many publishers are by now comfortably familiar with. Perhaps not entirely comfortably, but at least most publishers are already working with the Web; they already either know or have on staff people who understand it and can work with it. The foundation of our argument is this: rather than looking at jumping to XML in its full, industrial complexity, which seems to be what the O'Reilly-backed StartWithXML initiative[6] is suggesting, publishers instead leverage existing tools and technologies—starting with the Web—as a means of getting XML workflows in place. This means making small investments and working with known tools rather than spending tens of thousands of dollars on XML software and rarefied consultants. It means re-thinking how the existing pieces of the production toolchain fit together; re-thinking the existing roles of software components already in use. It means, fundamentally, taking the Web seriously as a content platform, rather than thinking of it as something you need to get content out to, somehow. If nothing else, the Web represents an opportunity to think about editorial and production from outside the shrink-wrapped Desktop Publishing paradigm.
  • Is the Web made of Real XML? At this point some predictable objections can be heard: wait a moment, the Web isn’t really made out of XML; the HTML that makes up most of the Web is at best the bastard child of SGML, and it is far too flaky/unstructured/underpowered to be taken seriously. We counter by arguing that although HTML on the Web exists in a staggering array of different incarnations, and that the majority of it is indeed an unstructured mess, this does not undermine the general principle that basic, ubiquitous Web technologies can make a solid platform for content management, editorial process, and production workflow.
  • With the advent of a published XML standard in the late 1990s came the W3C’s adoption of XHTML: the realization of the Web’s native content markup as a proper XML document type. Today, its acceptance is almost ubiquitous, even while the majority of actual content out there may not be strictly conforming. The more important point is that most contemporary Web software, from browsers to authoring tools to content management systems (from blogs to enterprise systems), are capable of working with clean, valid XHTML. Or, to put the argument the other way around, clean, valid XHTML content plays absolutely seamlessly with everything else on the Web.[7]
  • The objection which follows, then, will be that even if we grant that XHTML is a real XML document type, that it is underpowered for “serious” content because it is almost entirely presentation (formatting) oriented; it lacks any semantic depth. In XHTML, a paragraph is a paragraph is a paragraph, as opposed to a section or an epigraph or a summary.
  • n contrast, more “serious” XML document types like DocBook[8] or DITA-derived schemas[9] are capable of making semantic distinctions about content chunks at a fine level of granularity and with a high degree of specificity.
  • So there is an argument for recalling the 80:20 rule here. If XHTML can provide 80% of the value with just 20% of the investment, then what exactly is the business case for spending the other 80% to achieve that last 20% of value? We suspect the ratio is actually quite a bit steeper than 80:20 for most publishers.
  • Furthermore, just to get technical for a moment, XHTML is extensible in a fairly straightforward way, through the common “class” attribute on each element. Web developers have long leveraged this kind of extensibility in the elaboration of “microformats” for semantic-web applications.[10] There is no reason why publishers shouldn’t think to use XHTML’s simple extensibility in a similar way for their own ends.
  • XHTML, on the other hand, is supported by a vast array of quotidian software, starting with the ubiquitous Web browser. For this very reason, XHTML is in fact employed as a component part of several more specialized document types (ONIX and ePub among them).
  • Why re-invent a general-purpose prose representation when XHTML already does the job?
  • It is worth pausing for a moment to consider the role of XHTML in the ePub standard for ebook content. An ePub file is, anatomically, a simply disguised zip archive. Inside the zip archive are a few standard component parts: there are specialized files that declare metadata about the book, and about the format of the book. And then there is the book’s content, represented in XHTML. An ePub book is a Web page in a wrapper.
  • To sum up the general argument: the Web as it already exists presents incredible value to publishers, as a platform for doing XML content management with existing (and often free) tools, and without having to go blindly into the unknown. At this point, we can offer a few design guidelines: prefer existing and/or ubiquitous tools over specialized ones wherever possible; prefer free software over proprietary systems where possible; prefer simple tools controlled and coordinated by human beings over fully automated (and therefore complex) systems; play to our strengths: use Web software for storing and managing content, use layout software for layout, and keep editors and production people in charge of their own domains.
  • Putting the Pieces Together: A Prototype
  • At the SFU Master of Publishing Program, we have been chipping away at this general line of thinking for a few years. Over that time, Web content management systems have been getting more and more sophisticated, all the while getting more streamlined and easier to use. (NB: if you have a blog, you have a Web content management system.) The Web is beginning to be recognized as a writing and editing environment used by millions of people. And the ways in which content is represented, stored, and exchanged online have become increasingly robust and standardized.
  • The missing piece of the puzzle has been print production: how can we move content from its malleable, fluid form on line into the kind of high-quality print production environments we’ve come to expect after two decades of Desktop Publishing?
  • Anyone who has tried to print Web content knows that the existing methods leave much to be desired (hyphenation and justification, for starters). In the absence of decent tools for this, most publishers quite naturally think of producing the print content first, and then think about how to get material onto the Web for various purposes. So we tend to export from Word, or from Adobe, as something of an afterthought.
  • While this sort of works, it isn’t elegant, and it completely ignores the considerable advantages of Web-based content management.
  • Content managed online is stored in one central location, accessible simultaneously to everyone in your firm, available anywhere you have an Internet connection, and usually exists in a much more fluid format than Word files. If only we could manage the editorial flow online, and then go to print formats at the end, instead of the other way around. At SFU, we made several attempts to make this work by way of the supposed “XML import” capabilities of various Desktop Publishing tools, without much success.[12]
  • In the winter of 2009, Adobe solved this part of the problem for us with the introduction of its Creative Suite 4. What CS4 offers is the option of a complete XML representation of an InDesign document: what Adobe calls IDML (InDesign Markup Language).
  • The IDML file format is—like ePub—a simply disguised zip archive that, when unpacked, reveals a cluster of XML files that represent all the different facets of an InDesign document: layout spreads, master pages, defined styles, colours, and of course, the content.
  • IDML is a well thought-out XML standard that achieves two very different goals simultaneously: it preserves all of the information that InDesign needs to do what it does; and it is broken up in a way that makes it possible for mere mortals (or at least our Master of Publishing students) to work with it.
  • What this represented to us in concrete terms was the ability to take Web-based content and move it into InDesign in a straightforward way, thus bridging Web and print production environments using existing tools and skillsets, with a little added help from free software.
  • We would take clean XHTML content, transform it to IDML-marked content, and merge that with nicely designed templates in InDesign.
  • The result is an almost push-button publication workflow, which results in a nice, familiar InDesign document that fits straight into the way publishers actually do production.
  • Tracing the steps To begin with, we worked backwards, moving the book content back to clean XHTML.
  • The simplest method for this conversion—and if you want to create Web content, this is an excellent route—was to use Adobe’s “Export to Digital Editions” option, which creates an ePub file.
  • Recall that ePub is just XHTML in a wrapper, so within the ePub file was a relatively clean XHTML document. It was somewhat cleaner (that is, the XHTML tagging was simpler and less cluttered) than InDesign’s other Web-oriented exports, possibly because Digital Editions is a well understood target, compared with somebody’s website.
  • In order to achieve our target of clean XHTML, we needed to do some editing; the XHTML produced by InDesign’s “Digital Editions” export was presentation-oriented. For instance, bulleted list items were tagged as paragraphs, with a class attribute identifying them as list items. Using the search-and-replace function, we converted such structures to proper XHTML list and list-item elements. Our guiding principle was to make the XHTML as straightforward as possible, not dependent on any particular software to interpret it.
  • We broke the book’s content into individual chapter files; each chapter could then carry its own basic metadata, and the pages conveniently fit our Web content management system (which is actually just a wiki). We assembled a dynamically generated table of contents for the 12 chapters, and created a cover page. Essentially, the book was entirely Web-based at this point.
  • When the book chapters are viewed online, they are formatted via a CSS2 stylesheet that defines a main column for content as well as dedicating screen real estate for navigational elements. We then created a second template to render the content for exporting; this was essentially a bare-bones version of the book with no navigation and minimal styling. Pages (or even the entire book) can be exported (via the “Save As...” function in a Web browser) for use in either print production or ebook conversion. At this point, we required no skills beyond those of any decent Web designer.
  • Integrating with CS4 for Print Adobe’s IDML language defines elements specific to InDesign; there is nothing in the language that looks remotely like XHTML. So a mechanical transformation step is needed to convert the XHTML content into something InDesign can use. This is not as hard as it might seem.
  • Both XHTML and IDML are composed of straightforward, well-documented structures, and so transformation from one to the other is, as they say, “trivial.” We chose to use XSLT (Extensible Stylesheet Language Transforms) to do the work. XSLT is part of the overall XML specification, and thus is very well supported in a wide variety of tools. Our prototype used a scripting engine called xsltproc, a nearly ubiquitous piece of software that we found already installed as part of Mac OS X (contemporary Linux distributions also have this as a standard tool), though any XSLT processor would work.
  • In other words, we don’t need to buy InCopy, because we just replaced it with the Web. Our wiki is now plugged directly into our InDesign layout. It even automatically updates the InDesign document when the content changes. Credit is due at this point to Adobe: this integration is possible because of the open file format in the Creative Suite 4.
  • We wrote an XSLT transformation script[18] that converted the XHTML content from the Web into an InCopy ICML file. The script itself is less than 500 lines long, and was written and debugged over a period of about a week by amateurs (again, the people named at the start of this article). The script runs in a couple of seconds, and the resulting .icml file can then be “placed” directly into an InDesign template. The ICML file references an InDesign stylesheet, so the template file can be set up with a house-styled layout, master pages, and stylesheet definitions for paragraphs and character ranges.
  • The result is very simple and easy to use. Our demonstration requires that a production editor run the XSLT transformation script manually, but there is no reason why this couldn’t be built directly into the Web content management system so that exporting the content to print ran the transformation automatically. The resulting file would then be “placed” in InDesign and proofed.
  • It should be noted that the Book Publishing 1 proof-of-concept was artificially complex; we began with a book laid out in InDesign and ended up with a look-alike book laid out in InDesign. But next time—for instance, when we publish Book Publishing 2—we can begin the process with the content on the Web, and keep it there throughout the editorial process. The book’s content could potentially be written and edited entirely online, as Web content, and then automatically poured into an InDesign template at proof time. “Just in time,” as they say. This represents an entirely new way of thinking of book production. With a Web-first orientation, it makes little sense to think of the book as “in print” or “out of print”—the book is simply available, in the first place online; in the second place in derivative digital formats; and third, but really not much more difficult, in print-ready format, via the usual InDesign CS print production system publishers are already familiar with.
  • Creating Ebook Files Creating electronic versions from XHTML source is vastly simpler than trying to generate these out of the existing print process. The ePub version is extremely easy to generate; so is online marketing copy or excerpts for the Web, since the content begins life Web-native.
  • Since an ePub file is essentially XHTML content in a special wrapper, all that is required is that we properly “wrap” our XHTML content. Ideally, the content in an ePub file is broken into chapters (as ours was) and a table of contents file is generated in order to allow easy navigation within an ebook reader. We used Julian Smart’s free tool eCub[19] to simply and automatically generate the ePub wrapper and the table of contents. The only custom development we did was to create a CSS stylesheet for the ebook so that headings and paragraph indents looked the way we wanted. Starting with XHTML content, creating ePub is almost too easy.
  • Such a workflow—beginning with the Web and exporting to print—is surely more in line with the way we will do business in the 21st century, where the Web is the default platform for reaching audiences, developing content, and putting the pieces together. It is time, we suggest, for publishers to re-orient their operations and start with the Web.
  • Our project demonstrates that Web technologies are indeed good enough to use in an XML-oriented workflow; more specialized and expensive options are not necessarily required. For massive-scale enterprise publishing, this approach may not offer enough flexibility, and the challenge of adding and extracting extra semantic richness may prove more trouble than it's worth.
  • But for smaller firms who are looking at the straightforward benefits of XML-based processes—single source publishing, online content and workflow management, open and accessible archive formats, greater online discoverability—here is a way forward.
  • Rather than a public-facing website, our system relies on the Web as a content management platform—of course a public face could easily be added.
  • The final piece of our puzzle, the ability to integrate print production, was made possible by Adobe's release of InDesign with an open XML file format. Since the Web's XHTML is also XML, is can be easily and confidently transformed to the InDesign format.
  • today, we are able to put the process together using nothing but standard, relatively ubiquitous Web tools: the Web itself as an editing and content management environment, standard Web scripting tools for the conversion process, and the well-documented IDML file format to integrate the layout tool.
  • Using the Web as a Production Platform
  • Gary Edwards on 07 Nov 13
     
    I was looking for an answer to a problem Marbux had presented, and found this interesting article.  The issue was that of the upcoming conversion of the Note Case Pro (NCP) layout engine to the WebKit layout engine, and what to do about the NCP document format. My initial reaction was to encode the legacy NCP document format in XML, and run an XSLT to a universal pivot format like TEI-XML.  From there, the TEI-XML community would provide all the XSLT transformation routines for conversion to ODF, OOXML, XHTML, ePUB and HTML/CSS. Researching the problems one might encounter with this approach, I found this article.  Fascinating stuff. My take away is that TEI-XML would not be as effective a "universal pivot point" as XHTML.  Or perhaps, if NCP really wants to get aggressive; IDML - InDesign Markup Language. The important point though is that XHTML is a browser specific version of XML, and compatible with the Web Kit layout engine Miro wants to move NCP to. The concept of encoding an existing application-specific format in XML has been around since 1998, when XML was first introduced as a W3C standard, a "structured" subset of SGML. (HTML is also a subset of SGML). The multiplatform StarOffice productivity suite became "OpenOffice" when Sun purchased the company in 1998, and open sourced the code base. The OpenOffice developer team came out with a XML encoding of their existing document formats in 2000. The application specific encoding became an OASIS document format standard proposal in 2002 - also known as ODF. Microsoft followed OpenOffice with a XML encoding of their application-specific binary document formats, known as OOXML. Encoding the existing NCP format in XML, specifically targeting XHTML as a "universal pivot point", would put the NCP Outliner in the Web editor category, without breaking backwards compatibility. The trick is in the XSLT conversion process. But I think that is something much easier to handle then trying to
  • Gary Edwards on 07 Nov 13
     
    I was looking for an answer to a problem Marbux had presented, and found this interesting article.  The issue was that of the upcoming conversion of the Note Case Pro (NCP) layout engine to the WebKit layout engine, and what to do about the NCP document format. My initial reaction was to encode the legacy NCP document format in XML, and run an XSLT to a universal pivot format like TEI-XML.  From there, the TEI-XML community would provide all the XSLT transformation routines for conversion to ODF, OOXML, XHTML, ePUB and HTML/CSS. Researching the problems one might encounter with this approach, I found this article.  Fascinating stuff. My take away is that TEI-XML would not be as effective a "universal pivot point" as XHTML.  Or perhaps, if NCP really wants to get aggressive; IDML - InDesign Markup Language. The important point though is that XHTML is a browser specific version of XML, and compatible with the Web Kit layout engine Miro wants to move NCP to. The concept of encoding an existing application-specific format in XML has been around since 1998, when XML was first introduced as a W3C standard, a "structured" subset of SGML. (HTML is also a subset of SGML). The multiplatform StarOffice productivity suite became "OpenOffice" when Sun purchased the company in 1998, and open sourced the code base. The OpenOffice developer team came out with a XML encoding of their existing document formats in 2000. The application specific encoding became an OASIS document format standard proposal in 2002 - also known as ODF. Microsoft followed OpenOffice with a XML encoding of their application-specific binary document formats, known as OOXML. Encoding the existing NCP format in XML, specifically targeting XHTML as a "universal pivot point", would put the NCP Outliner in the Web editor category, without breaking backwards compatibility. The trick is in the XSLT conversion process. But I think that is something much easier to handle then trying to
Gonzalo San Gil, PhD.

Beginning Git and Github for Linux Users | Linux.com - 0 views

www.linux.com/...git-and-github-for-linux-users

beginning git github linux GNU_Linux CVS RCS revision control system version begin

shared by Gonzalo San Gil, PhD. on 22 Nov 14 - No Cached
  • Gonzalo San Gil, PhD. on 22 Nov 14
     
    "The Git distributed revision control system is a sweet step up from Subversion, CVS, Mercurial, and all those others we've tried and made do with. It's great for distributed development, when you have multiple contributors working on the same project, and it is excellent for safely trying out all kinds of crazy changes. We're going to use a free Github account for practice so we can jump right in and start doing stuff."
  • Gonzalo San Gil, PhD. on 22 Nov 14
     
    "The Git distributed revision control system is a sweet step up from Subversion, CVS, Mercurial, and all those others we've tried and made do with. It's great for distributed development, when you have multiple contributors working on the same project, and it is excellent for safely trying out all kinds of crazy changes. We're going to use a free Github account for practice so we can jump right in and start doing stuff."
Gonzalo San Gil, PhD.

Infamous "podcast patent" heads to trial | Ars Technica - 0 views

arstechnica.com/...casts-next-week-a-jury-decides

patent turn money collecting business instead invention promotion

shared by Gonzalo San Gil, PhD. on 06 Sep 14 - No Cached
  • Gonzalo San Gil, PhD. on 06 Sep 14
     
    [# ! Patents turned into a collecting business instead of a invention promotion mechanism :/ ...] "A few years later, "monetizing" patents through lawsuits turned into an industry of its own. Logan turned his patents into a powerhouse licensing machine, beginning with a case filed against Apple in 2009. He went to trial and won $8 million. Settlements with other industry giants, like Samsung and Amazon, followed."
  • Gonzalo San Gil, PhD. on 06 Sep 14
     
    [# ! Patents a collecting business instead of a invention promotion mechanism :/ ...] "A few years later, "monetizing" patents through lawsuits turned into an industry of its own. Logan turned his patents into a powerhouse licensing machine, beginning with a case filed against Apple in 2009. He went to trial and won $8 million. Settlements with other industry giants, like Samsung and Amazon, followed."
  • Gonzalo San Gil, PhD. on 06 Sep 14
     
    [# ! Patents turned into a collecting business instead of a invention promotion mechanism :/ ...] "A few years later, "monetizing" patents through lawsuits turned into an industry of its own. Logan turned his patents into a powerhouse licensing machine, beginning with a case filed against Apple in 2009. He went to trial and won $8 million. Settlements with other industry giants, like Samsung and Amazon, followed."
Gonzalo San Gil, PhD.

Linux Newbie Administrator Guide - Linux Newbie Administrator Guide [# ! Lead 'Note'...] - 1 views

linux.about.com/...gdenwb_idx.htm

linux administration guide newbies

shared by Gonzalo San Gil, PhD. on 26 Mar 15 - Cached
  • Gonzalo San Gil, PhD. on 26 Mar 15
     
    [# ! every day is a new beginning...] "Table of Contents 1. For the Undecided (Linux Benefits) 1.1 Fundamentally, why Linux? 1.2 Is Linux for me? 1.3 Linux is difficult for newbies. 1.4 What are the benefits of Linux?"
  • Gonzalo San Gil, PhD. on 26 Mar 15
     
    [# ! every day is a new beginning...] "Table of Contents 1. For the Undecided (Linux Benefits) 1.1 Fundamentally, why Linux? 1.2 Is Linux for me? 1.3 Linux is difficult for newbies. 1.4 What are the benefits of Linux?"
  • Gonzalo San Gil, PhD. on 26 Mar 15
     
    [# ! every day is a new beginning...] "Table of Contents 1. For the Undecided (Linux Benefits) 1.1 Fundamentally, why Linux? 1.2 Is Linux for me? 1.3 Linux is difficult for newbies. 1.4 What are the benefits of Linux?"
Gonzalo San Gil, PhD.

This lawsuit could be the beginning of the end for DRM | Defective by Design - 1 views

www.defectivebydesign.org/...uit_could_be_beginning_end_drm

EFF lawsuit Section 1202 DMCA could end DRM

shared by Gonzalo San Gil, PhD. on 17 Sep 16 - No Cached
  • Gonzalo San Gil, PhD. on 17 Sep 16
     
    Submitted by Zak Rogoff on August 17, 2016 - 9:20am Our friends at the Electronic Frontier Foundation (EFF) recently filed a lawsuit challenging Section 1201 of the US's Digital Millenium Copyright Act, which provides legal reinforcement to the technical shackles of Digital Restrictions Management (DRM). Defective by Design applauds this lawsuit and agrees with the EFF that Section 1201 violates the right to freedom of speech. We hope that excising Section 1201 from US law can be the beginning of the end for DRM.
Gonzalo San Gil, PhD.

Blender: An Introduction for Final Cut Pro Users | FOSS Force - 0 views

fossforce.com/...troduction-final-cut-pro-users

blender introduction Final cut Pro professional video audio-video editing production open source free software

shared by Gonzalo San Gil, PhD. on 26 Sep 16 - No Cached
  • Gonzalo San Gil, PhD. on 26 Sep 16
     
    "Phil Shapiro Have you often considered quitting your day job to begin an exciting career as a filmmaker? You don't need the resources of a Hollywood studio anymore. In fact, you can do it all with free and open source software."
  • Gonzalo San Gil, PhD. on 26 Sep 16
     
    "Phil Shapiro Have you often considered quitting your day job to begin an exciting career as a filmmaker? You don't need the resources of a Hollywood studio anymore. In fact, you can do it all with free and open source software."
Paul Merrell

New York company says it can beam free OUTERNET Wi-fi to every person on Earth | Mail O... - 0 views

www.dailymail.co.uk/...-wi-fi-person-Earth-space.html

internet internet-access Outernet satellite broadband

shared by Paul Merrell on 26 Feb 14 - No Cached
  • An ambitious project known as Outernet is aiming to launch hundreds of miniature satellites into low Earth orbit by June 2015Each satellite will broadcast the Internet to phones and computers giving billions of people across the globe free online accessCitizens of countries like China and North Korea that have censored online activity could be given free and unrestricted cyberspace'There's really nothing that is technically impossible to this'
  • You might think you have to pay through the nose at the moment to access the Internet.But one ambitious organisation called the Media Development Investment Fund (MDIF) is planning to turn the age of online computing on its head by giving free web access to every person on Earth.Known as Outernet, MDIF plans to launch hundreds of satellites into orbit by 2015.And they say the project could provide unrestricted Internet access to countries where their web access is censored, including China and North Korea.
  • Using something known as datacasting technology, which involves sending data over wide radio waves, the New York-based company says they'll be able to broadcast the Internet around the world.The group is hoping to raise tens of millions of dollars in donations to get the project on the road.
  • ...2 more annotations...
  • The company's plan is to launch hundreds of low-cost miniature satellites, known as cubesats, into low Earth orbit.Here, each satellite will receive data from a network of ground stations across the globe.
  • THE OUTERNET PROJECT TIMELINEBy June of this year the Outernet project aims to begin deploying prototype satellites to test their technologyIn September 2014 they will make a request to NASA to test their technology on the International Space StationBy early 2015 they intend to begin manufacturing and launching their satellitesAnd in June 2015 the company says they will begin broadcasting the Outernet from space
Gonzalo San Gil, PhD.

Teaching kids game design with open source software | Opensource.com - 2 views

opensource.com/...teaching-digital-creativity

teaching kids game design open source creativity

shared by Gonzalo San Gil, PhD. on 29 Sep 14 - No Cached
  • Gonzalo San Gil, PhD. on 29 Sep 14
     
    "Youth Digital just moved into their new offices, tucked away in a nondescript office park in Chapel Hill, North Carolina. It's a big step up from their humble beginnings, when company founder and director Justin Richards hauled a laptop to his students' houses, tutoring them on web and graphic design. "
  • Gonzalo San Gil, PhD. on 29 Sep 14
     
    "Youth Digital just moved into their new offices, tucked away in a nondescript office park in Chapel Hill, North Carolina. It's a big step up from their humble beginnings, when company founder and director Justin Richards hauled a laptop to his students' houses, tutoring them on web and graphic design. "
Gonzalo San Gil, PhD.

Congressional attack on patent trolls begins anew | Ars Technica - 0 views

arstechnica.com/...k-on-patent-trolls-begins-anew

USA congress attack patent begins against trols spur innovation hope it helps open source too

shared by Gonzalo San Gil, PhD. on 30 Apr 15 - No Cached
  • Gonzalo San Gil, PhD. on 30 Apr 15
     
    "Bill "will help patent holders, spur innovation and ultimately grow our economy." by David Kravets - Apr 29, 2015 8:32 pm UTC"
  • Gonzalo San Gil, PhD. on 30 Apr 15
     
    "Bill "will help patent holders, spur innovation and ultimately grow our economy." by David Kravets - Apr 29, 2015 8:32 pm UTC"
Gonzalo San Gil, PhD.

Get involved with the Open Source Hardware Association | Opensource.com - 0 views

opensource.com/...en-source-hardware-association

open source hardware association get involved OSHW associate

shared by Gonzalo San Gil, PhD. on 26 Apr 15 - No Cached
  • Gonzalo San Gil, PhD. on 26 Apr 15
     
    "Back in October of 2014, I was lucky enough to be elected to the Open Source Hardware Association (OSHWA) board. Because the association received its nonprofit status, the board is finally able to begin increasing its reach in the community."
  • Gonzalo San Gil, PhD. on 26 Apr 15
     
    "Back in October of 2014, I was lucky enough to be elected to the Open Source Hardware Association (OSHWA) board. Because the association received its nonprofit status, the board is finally able to begin increasing its reach in the community."
Gary Edwards

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

weblogs.mozillazine.org/...en_letter_to_chris_wilson.html

es4 es3 javascript brendan-eich microsoft

shared by Gary Edwards on 28 Jan 09 - Cached
  • 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.
  • Gary Edwards on 28 Jan 09
     
    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.
Gonzalo San Gil, PhD.

Why is everyone hating on operating systems? | Opensource.com - 0 views

opensource.com/...lightning-talks-brian-proffitt

operating syatems haterd opensource.com love containers virtualization interaction

shared by Gonzalo San Gil, PhD. on 22 Dec 14 - No Cached
  • Gonzalo San Gil, PhD. on 22 Dec 14
     
    All Things Open 2014 lightning talk with Brian Proffitt "In the beginning, there were operating systems. Computers have changed, evolved, and grown ever more powerful. But the operating system is still underlying everything, and it's not going anywhere."
  • Gonzalo San Gil, PhD. on 22 Dec 14
     
    All Things Open 2014 lightning talk with Brian Proffitt "In the beginning, there were operating systems. Computers have changed, evolved, and grown ever more powerful. But the operating system is still underlying everything, and it's not going anywhere."
Gonzalo San Gil, PhD.

2015: Open Source Has Won, But It Isn't Finished - Technology Blog and Community from I... - 0 views

www.computerworlduk.com/...open-source-has-won-3592314

open source technology community experts wins winner year

shared by Gonzalo San Gil, PhD. on 11 Jan 15 - No Cached
  • Gonzalo San Gil, PhD. on 11 Jan 15
     
    "At the beginning of a new year, it's traditional to look back over the last 12 months. But as far as this column is concerned, it's easy to summarise what happened then: open source has won. Let's take it from the top:"
  • Gonzalo San Gil, PhD. on 11 Jan 15
     
    "At the beginning of a new year, it's traditional to look back over the last 12 months. But as far as this column is concerned, it's easy to summarise what happened then: open source has won. Let's take it from the top:"
Gonzalo San Gil, PhD.

Thunderclap: Free Information from Space Outernet for Aug 11, 2014 - 0 views

www.thunderclap.it/...77-free-information-from-space

free information space Outernet thunderclap August 11 2014

shared by Gonzalo San Gil, PhD. on 24 Jul 14 - No Cached
  • Right now, only 40% of humanity can connect to the Internet. Even less than that have access to truly free, uncensored Internet. What this represents is an enormous gap in access to information. While the Internet is an amazing communication tool, it is also the largest library ever constructed. It grants access to anything from books, videos, courseware, news, and weather, to open source farm equipment or instructions on how to treat infection or prevent HIV from spreading. #ImagineIf everyone could have that information for free?On August 11, 2014, Outernet will make that library available from space for free for the first time. Help us tell the world.#ImagineIf everyone had any information they wanted - what would that world look like? What new inventions would be created or diseases cured? What would people read about if their governments no longer deprived them of their right to free information? Soon, we won't have to imagine.
  • Right now, only 40% of humanity can connect to the Internet. Even less than that have access to truly free, uncensored Internet. What this represents is an enormous gap in access to information. While the Internet is an amazing communication tool, it is also the largest library ever constructed. It grants access to anything from books, videos, courseware, news, and weather, to open source farm equipment or instructions on how to treat infection or prevent HIV from spreading. #ImagineIf everyone could have that information for free?On August 11, 2014, Outernet will make that library available from space for free for the first time. Help us tell the world.#ImagineIf everyone had any information they wanted - what would that world look like? What new inventions would be created or diseases cured? What would people read about if their governments no longer deprived them of their right to free information? 
  • Paul Merrell on 24 Jul 14
     
    INFORMATION FOR THE WORLD FROM OUTER SPACE Unrestricted, globally accessible, broadcast data. Quality content from all over the Internet. Available to all of humanity. For free. Through satellite data broadcasting, Outernet is able to bypass censorship, ensure privacy, and offer a universally-accessible information service at no cost to global citizens. It's the modern version of shortwave radio, or BitTorrent from space.
  • Gonzalo San Gil, PhD. on 25 Jul 14
     
    ""#ImagineIf every human had a free library at home... Information equality begins TODAY: Outernet is LIVE from space! http://thndr.it/1pazaP3" "
  • Gonzalo San Gil, PhD. on 25 Jul 14
     
    ""#ImagineIf every human had a free library at home... Information equality begins TODAY: Outernet is LIVE from space! http://thndr.it/1pazaP3" "
Paul Merrell

Yahoo to begin offering PGP encryption support in Yahoo Mail service | Ars Technica - 0 views

arstechnica.com/...-support-in-yahoo-mail-service

surveillance state NSA-reform NSA-blowback Yahoo! email

shared by Paul Merrell on 08 Aug 14 - No Cached
  • Yahoo Chief Information Security Officer Alex Stamos announced today at Black Hat 2014 that starting in the fall of this year, the purple-hued company will begin giving users the option of seamlessly wrapping their e-mails in PGP encryption. According to Kashmir Hill at Forbes, the encryption capability will be offered through a modified version of the same End-to-End browser plug-in that Google uses for PGP in Gmail. The announcement was tweeted by Yan Zhu, who has reportedly been hired by Yahoo to adapt End-to-End for use with Yahoo Mail. Zhu formerly worked as an engineer at the Electronic Frontier Foundation, an organization that has consistently been outspoken in its call for the widespread use of encryption throughout the Web and the Internet in general.
Gonzalo San Gil, PhD.

Net neutrality is only the beginning of an open internet | Technology | The Guardian - 0 views

www.theguardian.com/...-beginning-of-an-open-internet

Net Neutrality net neutrality just beginning open INternet the guardian technology

shared by Gonzalo San Gil, PhD. on 05 Mar 15 - No Cached
  • Gonzalo San Gil, PhD. on 05 Mar 15
     
    "US regulators are voting on whether to enshrine the openness of the internet, and the outcome is likely to influence policy worldwide"
Gonzalo San Gil, PhD.

9 Linux distros to watch in 2015 | inforworld.com - 0 views

www.infoworld.com/...-distros-to-watch-in-2015.html

linux distros watch 2015 infoworld.com open source free software GNU GNU_Linux

shared by Gonzalo San Gil, PhD. on 15 Jan 15 - No Cached
  • Gonzalo San Gil, PhD. on 15 Jan 15
     
    "Looking ahead Predictions are fun. We all enjoy tech predictions at the beginning of each year. This isn't that. This is a list of the nine Linux distributions that I feel will be the most interesting to watch during 2015. "
  • Gonzalo San Gil, PhD. on 15 Jan 15
     
    "Looking ahead Predictions are fun. We all enjoy tech predictions at the beginning of each year. This isn't that. This is a list of the nine Linux distributions that I feel will be the most interesting to watch during 2015. "
Gonzalo San Gil, PhD.

Maybe It's Time to Trust Microsoft -- Maybe Not | FOSS Force - 0 views

fossforce.com/...time-trust-microsoft-maybe-not

Linux not time trust Microsoft yes sake understanding computers people

shared by Gonzalo San Gil, PhD. on 10 Apr 16 - No Cached
  • Gonzalo San Gil, PhD. on 10 Apr 16
     
    "Ken Starks The Heart of Linux In this story, Microsoft is the cunning spider and Linux the intended victim, the fly. Everyone knows how the story begins. 'Will you walk into my parlour?' said the Spider to the Fly."
  • Gonzalo San Gil, PhD. on 10 Apr 16
     
    "Ken Starks The Heart of Linux In this story, Microsoft is the cunning spider and Linux the intended victim, the fly. Everyone knows how the story begins. 'Will you walk into my parlour?' said the Spider to the Fly."
Paul Merrell

Lawrence, KS To Get Gigabit Fiber - But Not From Google - Slashdot - 0 views

tech.slashdot.org/...abit-fiber-but-not-from-google

gigabit ISP broadband roll-out Google

shared by Paul Merrell on 27 Apr 13 - No Cached
  • "Just 40 miles west on the Kansas Turnpike from Kansas City Kansas sits Lawrence, KS. With the slow rollout of Google fiber in their neighbor city, it was looking like their 89,000 people were not going to get the gigabit fiber to the home for quite some time. Up steps Wicked Broadband, a local ISP. With a plan remarkably similar to Google's they look to build out fiber to the home, business, and so on with gigabit speed and similar rates, symmetric bandwidth and no caps. Wicked Fiber's offer is different than Google Fiber's, with more tiers — with cute names. The "Flying Monkey" gigabit plan is $100/month, "Tinman" at 100Mbps is $70/month. They offer TV as well but strangely put Internet streaming and Roku to the fore. They are even using Google's method of installing first in the neighborhoods with the most pre-registration to optimize efficiency, and installing only where there is enough demand. It seems Google's scheme to inspire competition in broadband access is working — if Wicked Fiber gets enough subscribers to make it pay. If this succeeds it may inspire similar ISPs near us to step up to gigabit fiber so let's root for them."
  • Paul Merrell on 27 Apr 13
     
    It shouldn't take a lot of similar initiatives from companies other than Google to force major ISPs to begin rolling out gigabit ISP services in the U.S. in order to protect their market share from predation. To be followed by lower charges, hopefully. 
Gonzalo San Gil, PhD.

Community Grants Training: Writing a Community Grants Proposal | Internet Society - 0 views

www.internetsociety.org/...ting-community-grants-proposal

community grants training writing proposal internet society

shared by Gonzalo San Gil, PhD. on 22 Jan 13 - No Cached
  • Gonzalo San Gil, PhD. on 22 Jan 13
     
    [Home » Community Grants Training: Writing a Community Grants Proposal Community Grants Training: Writing a Community Grants Proposal The Community Grants Programme will accept applications beginning Monday, 4 March 2013. The application round will close Monday, 01 April and award notifications made at the end of May 2013. This Training Session will be offered twice on 5 February 2013 in order to cover different time zones, namely at 10:30 UTC and at 20:00 UTC. Please sign up at http://www.doodle.com/d6adh23v9gucr4mt if you plan to participate in this session. Thanks! Venue: WebEx (see details for both sessions below) Agenda: Turning a project idea into a plan Characteristics of a great grant proposal Overview of the grant application Expectations of our grantees ...]
1 - 20 of 114 Next › Last »
Showing 20▼ items per page