Skip to main content

Home/ Future of the Web/ Group items matching "basic" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
Gonzalo San Gil, PhD.

Musk: We need universal basic income because robots will take all the jobs | Ars Technica UK - 0 views

arstechnica.co.uk/...l-income-survive-robot-workers

Elon Musk Musk UBI Universal Basic Income universal basic income governments oblligation due robots working people welfare industry leisure health ideas beyond

shared by Gonzalo San Gil, PhD. on 08 Nov 16 - No Cached
  • Gonzalo San Gil, PhD. on 08 Nov 16
     
    "Elon Musk reckons the robot revolution is inevitable and it's going to take all the jobs. For humans to survive in an automated world, he said that governments are going to be forced to bring in a universal basic income-paying each citizen a certain amount of money so they can afford to survive. According to Musk, there aren't likely to be any other options."
  • Gonzalo San Gil, PhD. on 08 Nov 16
     
    "Elon Musk reckons the robot revolution is inevitable and it's going to take all the jobs. For humans to survive in an automated world, he said that governments are going to be forced to bring in a universal basic income-paying each citizen a certain amount of money so they can afford to survive. According to Musk, there aren't likely to be any other options."
Gonzalo San Gil, PhD.

Bsrtech.net: Linux Guide: Linux Interview Questions - 0 views

www.bsrtech.net/...linux-interview-questions.html

linux basics material tutorial guide interview questions

shared by Gonzalo San Gil, PhD. on 22 Apr 14 - No Cached
  • Gonzalo San Gil, PhD. on 22 Apr 14
     
    1). Linux Interview Questions on Basics : Part 1 2). Linux Interview Questions on Basics : Part 2 3). Interview Questions for Freshers&Experienced
Gonzalo San Gil, PhD.

Call for Papers | thinktwice.com | Creativity, Human Rights, Hacktivism [# Via FB's Francisco George x Arif Yıldırım] Deadline July 18th 2014 - 0 views

thinktwice.co/...cfp

thinktwice.com call papers creativity Human Rights hacktivism

shared by Gonzalo San Gil, PhD. on 15 Jun 14 - No Cached
  • Gonzalo San Gil, PhD. on 15 Jun 14
     
    "Call for Papers CALL FOR SUBMISSIONS We are looking for session submissions from Pirates, NGOs and Academia to following tracks: (other topics are allowed as well) Creativity: copyrights, patents, collaboration, citizen journalism, media, DRM, open access, FOI, public licensing, policy reform, education, etc… Human Rights: security, data protection, surveillance, FOI, basic income, emigration, voting rights, drones, non-proliferation, dual use technology, encryption, anonymity, transparency, net neutrality, open data, egovernment, society, whistle blowing, political science, etc… Activism|Hacktivism: Future, innovation, liquid democracy, transhumanism, cyborgs, startups, vision, 3d-printing, crowdsourcing, big data, participation, pirate parties, artificial intelligence, globalization, space travel, social networks, freemanning, freehammond, hacktivism, activism, civil disobedience, hacker culture, cyberpunk, cypherpunk, wikileaks, surveillance, digital activism, etc..."
  • ...1 more comment...
  • Gonzalo San Gil, PhD. on 15 Jun 14
     
    "Call for Papers CALL FOR SUBMISSIONS We are looking for session submissions from Pirates, NGOs and Academia to following tracks: (other topics are allowed as well) Creativity: copyrights, patents, collaboration, citizen journalism, media, DRM, open access, FOI, public licensing, policy reform, education, etc… Human Rights: security, data protection, surveillance, FOI, basic income, emigration, voting rights, drones, non-proliferation, dual use technology, encryption, anonymity, transparency, net neutrality, open data, egovernment, society, whistle blowing, political science, etc… Activism|Hacktivism: Future, innovation, liquid democracy, transhumanism, cyborgs, startups, vision, 3d-printing, crowdsourcing, big data, participation, pirate parties, artificial intelligence, globalization, space travel, social networks, freemanning, freehammond, hacktivism, activism, civil disobedience, hacker culture, cyberpunk, cypherpunk, wikileaks, surveillance, digital activism, etc..."
  • Gonzalo San Gil, PhD. on 15 Jun 14
     
    "Call for Papers CALL FOR SUBMISSIONS We are looking for session submissions from Pirates, NGOs and Academia to following tracks: (other topics are allowed as well) Creativity: copyrights, patents, collaboration, citizen journalism, media, DRM, open access, FOI, public licensing, policy reform, education, etc… Human Rights: security, data protection, surveillance, FOI, basic income, emigration, voting rights, drones, non-proliferation, dual use technology, encryption, anonymity, transparency, net neutrality, open data, egovernment, society, whistle blowing, political science, etc… Activism|Hacktivism: Future, innovation, liquid democracy, transhumanism, cyborgs, startups, vision, 3d-printing, crowdsourcing, big data, participation, pirate parties, artificial intelligence, globalization, space travel, social networks, freemanning, freehammond, hacktivism, activism, civil disobedience, hacker culture, cyberpunk, cypherpunk, wikileaks, surveillance, digital activism, etc..."
  • Gonzalo San Gil, PhD. on 16 Jun 14
     
    [# Via FB's Francisco George x Arif Yıldırım] Deadline July 18th 2014 "Call for Papers CALL FOR SUBMISSIONS We are looking for session submissions from Pirates, NGOs and Academia to following tracks: (other topics are allowed as well) Creativity: copyrights, patents, collaboration, citizen journalism, media, DRM, open access, FOI, public licensing, policy reform, education, etc… Human Rights: security, data protection, surveillance, FOI, basic income, emigration, voting rights, drones, non-proliferation, dual use technology, encryption, anonymity, transparency, net neutrality, open data, egovernment, society, whistle blowing, political science, etc… Activism|Hacktivism: Future, innovation, liquid democracy, transhumanism, cyborgs, startups, vision, 3d-printing, crowdsourcing, big data, participation, pirate parties, artificial intelligence, globalization, space travel, social networks, freemanning, freehammond, hacktivism, activism, civil disobedience, hacker culture, cyberpunk, cypherpunk, wikileaks, surveillance, digital activism, etc..."
Paul Merrell

The UN Releases Plan to Push for Worldwide Internet Censorship | Global Research - Centre for Research on Globalization - 0 views

www.globalresearch.ca/...5478411

internet freedom U.N. internet-censorship

shared by Paul Merrell on 28 Sep 15 - No Cached
  • The United Nations has disgraced itself immeasurably over the past month or so. In case you missed the following stories, I suggest catching up now: The UN’s “Sustainable Development Agenda” is Basically a Giant Corporatist Fraud Not a Joke – Saudi Arabia Chosen to Head UN Human Rights Panel Fresh off the scene from those two epic embarrassments, the UN now wants to tell governments of the world how to censor the internet. I wish I was kidding. From the Washington Post: On Thursday, the organization’s Broadband Commission for Digital Development released a damning “world-wide wake-up call” on what it calls “cyber VAWG,” or violence against women and girls. The report concludes that online harassment is “a problem of pandemic proportion” — which, nbd, we’ve all heard before. But the United Nations then goes on to propose radical, proactive policy changes for both governments and social networks, effectively projecting a whole new vision for how the Internet could work. Under U.S. law — the law that, not coincidentally, governs most of the world’s largest online platforms — intermediaries such as Twitter and Facebook generally can’t be held responsible for what people do on them. But the United Nations proposes both that social networks proactively police every profile and post, and that government agencies only “license” those who agree to do so.
  • People are being harassed online, and the solution is to censor everything and license speech? Remarkable. How that would actually work, we don’t know; the report is light on concrete, actionable policy. But it repeatedly suggests both that social networks need to opt-in to stronger anti-harassment regimes and that governments need to enforce them proactively. At one point toward the end of the paper, the U.N. panel concludes that“political and governmental bodies need to use their licensing prerogative” to better protect human and women’s rights, only granting licenses to “those Telecoms and search engines” that “supervise content and its dissemination.” So we’re supposed to be lectured about human rights from an organization that named Saudi Arabia head of its human rights panel? Got it. Regardless of whether you think those are worthwhile ends, the implications are huge: It’s an attempt to transform the Web from a libertarian free-for-all to some kind of enforced social commons. This U.N. report gets us no closer, alas: all but its most modest proposals are unfeasible. We can educate people about gender violence or teach “digital citizenship” in schools, but persuading social networks to police everything their users post is next to impossible. And even if it weren’t, there are serious implications for innovation and speech: According to the Electronic Frontier Foundation, CDA 230 — the law that exempts online intermediaries from this kind of policing — is basically what allowed modern social networks (and blogs, and comments, and forums, etc.) to come into being. If we’re lucky, perhaps the Saudi religious police chief (yes, they have one) who went on a rampage against Twitter a couple of years ago, will be available to head up the project. What a joke.
Gonzalo San Gil, PhD.

Linux Guide: Linux Basic Commands - 2 views

linuxguideco.blogspot.com.es/...linux-basic-commands.html

linux basic commands guide

shared by Gonzalo San Gil, PhD. on 13 May 13 - No Cached
  • Gonzalo San Gil, PhD. on 13 May 13
     
    The Future is Open... and Free. ✌☺
Alexandra IcecreamApps

TeamViewer Alternatives: 5 Best Remote Desktop Software - Icecream Tech Digest - 1 views

icecreamapps.com/...5-best-remote-desktop-software

alternative to teamviewer AnyDesk Chrome Remote Desktop free remote desktop join.me Mikogo remote access remote access software remote desktop software Splashtop TeamViewer TeamViewer alternative TeamViewer alternatives

shared by Alexandra IcecreamApps on 24 Feb 16 - No Cached
  • Alexandra IcecreamApps on 24 Feb 16
     
    Remote desktop access programs help users work on a computer through another one. Such programs can be extremely helpful for mutual work between people, technical support, and various help and tutorials. Basically, desktop sharing programs are perfect for all sorts … Continue reading →
  • Alexandra IcecreamApps on 24 Feb 16
     
    Remote desktop access programs help users work on a computer through another one. Such programs can be extremely helpful for mutual work between people, technical support, and various help and tutorials. Basically, desktop sharing programs are perfect for all sorts … Continue reading →
Paul Merrell

Archiveteam - 0 views

www.archiveteam.org/index.php

internet history archives Internet-Archives ArchiveTeam

shared by Paul Merrell on 30 Aug 16 - Cached
  • HISTORY IS OUR FUTURE And we've been trashing our history Archive Team is a loose collective of rogue archivists, programmers, writers and loudmouths dedicated to saving our digital heritage. Since 2009 this variant force of nature has caught wind of shutdowns, shutoffs, mergers, and plain old deletions - and done our best to save the history before it's lost forever. Along the way, we've gotten attention, resistance, press and discussion, but most importantly, we've gotten the message out: IT DOESN'T HAVE TO BE THIS WAY. This website is intended to be an offloading point and information depot for a number of archiving projects, all related to saving websites or data that is in danger of being lost. Besides serving as a hub for team-based pulling down and mirroring of data, this site will provide advice on managing your own data and rescuing it from the brink of destruction. Currently Active Projects (Get Involved Here!) Archive Team recruiting Want to code for Archive Team? Here's a starting point.
  • Archive Team is a loose collective of rogue archivists, programmers, writers and loudmouths dedicated to saving our digital heritage. Since 2009 this variant force of nature has caught wind of shutdowns, shutoffs, mergers, and plain old deletions - and done our best to save the history before it's lost forever. Along the way, we've gotten attention, resistance, press and discussion, but most importantly, we've gotten the message out: IT DOESN'T HAVE TO BE THIS WAY. This website is intended to be an offloading point and information depot for a number of archiving projects, all related to saving websites or data that is in danger of being lost. Besides serving as a hub for team-based pulling down and mirroring of data, this site will provide advice on managing your own data and rescuing it from the brink of destruction.
  • Who We Are and how you can join our cause! Deathwatch is where we keep track of sites that are sickly, dying or dead. Fire Drill is where we keep track of sites that seem fine but a lot depends on them. Projects is a comprehensive list of AT endeavors. Philosophy describes the ideas underpinning our work. Some Starting Points The Introduction is an overview of basic archiving methods. Why Back Up? Because they don't care about you. Back Up your Facebook Data Learn how to liberate your personal data from Facebook. Software will assist you in regaining control of your data by providing tools for information backup, archiving and distribution. Formats will familiarise you with the various data formats, and how to ensure your files will be readable in the future. Storage Media is about where to get it, what to get, and how to use it. Recommended Reading links to others sites for further information. Frequently Asked Questions is where we answer common questions.
  • Paul Merrell on 30 Aug 16
     
    The Archive Team Warrior is a virtual archiving appliance. You can run it to help with the ArchiveTeam archiving efforts. It will download sites and upload them to our archive - and it's really easy to do! The warrior is a virtual machine, so there is no risk to your computer. The warrior will only use your bandwidth and some of your disk space. It will get tasks from and report progress to the Tracker. Basic usage The warrior runs on Windows, OS X and Linux using a virtual machine. You'll need one of: VirtualBox (recommended) VMware workstation/player (free-gratis for personal use) See below for alternative virtual machines Partners with and contributes lots of archives to the Wayback Machine. Here's how you can help by contributing some bandwidth if you run an always-on box with an internet connection.
Gonzalo San Gil, PhD.

10 Tips to Push Your Git Skills to the Next Level - 1 views

www.sitepoint.com/10-tips-git-next-level

tips push git skills next level tutorial

shared by Gonzalo San Gil, PhD. on 21 Jun 14 - No Cached
  • Gonzalo San Gil, PhD. on 21 Jun 14
     
    " Published June 17, 2014 Tweet Subscribe Recently we published a couple of tutorials to get you familiar with Git basics and using Git in a team environment. The commands that we discussed were about enough to help a developer survive in the Git world. In this post, we will try to explore how to manage your time effectively and make full use of the features that Git provides."
  • Gonzalo San Gil, PhD. on 21 Jun 14
     
    " Published June 17, 2014 Tweet Subscribe Recently we published a couple of tutorials to get you familiar with Git basics and using Git in a team environment. The commands that we discussed were about enough to help a developer survive in the Git world. In this post, we will try to explore how to manage your time effectively and make full use of the features that Git provides."
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.

User Data Manifesto 2.0 - 0 views

userdatamanifesto.org

user data manifesto platform access knowledge rectification modification removal

shared by Gonzalo San Gil, PhD. on 06 Sep 15 - No Cached
  • Gonzalo San Gil, PhD. on 06 Sep 15
     
    "Defining basic rights for people to control their own data in the internet age"
  • Gonzalo San Gil, PhD. on 06 Sep 15
     
    "Defining basic rights for people to control their own data in the internet age"
Paul Merrell

W3C Standards Make Mobile Web Experience More Inviting - 0 views

www.w3.org/...mwbp-pressrelease

accessibility convergence devices mobile web profiles w3c xhtml basic

shared by Paul Merrell on 30 Jul 08 - Cached
  • W3C today announced new standards that will make it easier for people to browse the Web on mobile devices. Mobile Web Best Practices 1.0, published as a W3C Recommendation, condenses the experience of many mobile Web stakeholders into practical advice on creating mobile-friendly content.
  • Until today, content developers faced an additional challenge: a variety of mobile markup languages to choose from. With the publication of the XHTML Basic 1.1 Recommendation today, the preferred format specification of the Best Practices, there is now a full convergence in mobile markup languages, including those developed by the Open Mobile Alliance (OMA). The W3C mobileOK checker (beta), when used with the familiar W3C validator, helps developers test mobile-friendly Web content.
  • W3C is also developing resources to help authors understand how to create content that is both mobile-friendly and accessible to people with disabilities. A draft of Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG) is jointly published by the The Mobile Web Best Practices Working Group and WAI's Education & Outreach Working Group (EOWG).
  • anonymous on 02 Oct 13
     
    Most quality online stores. Know whether you are a trusted online retailer in the world. Whatever we can buy very good quality. and do not hesitate. Everything is very high quality. Including clothes, accessories, bags, cups. Highly recommended. This is one of the trusted online store in the world. View now www.retrostyler.com
Paul Merrell

W3C Helps Authors Go Mobile - 0 views

www.w3.org/...mobileok-pressrelease.html.en

devices validators web page validators W3C convergence

shared by Paul Merrell on 10 Dec 08 - Cached
  • http://www.w3.org/ -- 8 December 2008 -- Today, W3C has made it easier to create content designed to improve people's mobile experience using a broad range of devices. W3C invites the community to try the W3C mobileOK checker, which is based on the newly published standard, the mobileOK Basic Tests 1.0 Recommendation. "The new checker builds on the suite of quality assurance tools offered by W3C to help authors and authoring tool developers create clean content," said Tim Berners-Lee, W3C Director. "Clean content offers a number of benefits to authors and users alike. The mobileOK checker does a nice job helping you improve your content one step at a time. Your mobile audience will thank you each time you improve your score."
  • The mobileOK Basic tests are based on the part of the Mobile Web Best Practices that can be verified automatically with software. The checker makes use of the popular W3C validator to help improve content quality. In addition to the mobile-friendliness score, the checker offers tips for meeting the needs of people on the go.
Gonzalo San Gil, PhD.

Calendar - Internet Society - 0 views

connect.internetsociety.org/...calendar

calendar activities 2014 Internet Society internet society act do go participate share ideas

shared by Gonzalo San Gil, PhD. on 15 Oct 14 - No Cached
  • Gonzalo San Gil, PhD. on 15 Oct 14
     
    [E-Group Rules & Etiquette Thank you for being part of our community. To ensure the best possible experience for all members, we have established some basic guidelines for participation. ...]
  • Gonzalo San Gil, PhD. on 15 Oct 14
     
    [E-Group Rules & Etiquette Thank you for being part of our community. To ensure the best possible experience for all members, we have established some basic guidelines for participation. ...]
Gonzalo San Gil, PhD.

A basic encryption strategy for storing sensitive data | ITworld - 0 views

www.itworld.com/...trategy-storing-sensitive-data

basic encryption strategy storing sensitive data

shared by Gonzalo San Gil, PhD. on 21 Aug 14 - No Cached
  • Gonzalo San Gil, PhD. on 21 Aug 14
     
    "To safely store your data in a database, you'd start by generating a strong secret key value in a byte array. This is best generated programmatically. This single key can be used to encrypt all of the data you'd like to store. "
  • Gonzalo San Gil, PhD. on 21 Aug 14
     
    "To safely store your data in a database, you'd start by generating a strong secret key value in a byte array. This is best generated programmatically. This single key can be used to encrypt all of the data you'd like to store. "
Gonzalo San Gil, PhD.

Pass, an open source password manager | Opensource.com - 1 views

opensource.com/...ging-passwords-open-source-way

pass open source password manager

shared by Gonzalo San Gil, PhD. on 04 Jul 14 - No Cached
  • Gonzalo San Gil, PhD. on 04 Jul 14
     
    "It's basically a simple command-line utility that helps you manage passwords. It uses GnuPG-encrypted files to save and manage user passwords."
  • Gonzalo San Gil, PhD. on 04 Jul 14
     
    "It's basically a simple command-line utility that helps you manage passwords. It uses GnuPG-encrypted files to save and manage user passwords."
Gonzalo San Gil, PhD.

How to do fast, repeatable Linux installations | Opensource.com - 0 views

opensource.com/...automating-linux-install

how to #howto do fast repeatable Linux installations GNU_Linux tasks automation

shared by Gonzalo San Gil, PhD. on 28 Mar 15 - No Cached
  • Gonzalo San Gil, PhD. on 28 Mar 15
     
    Automate everything: Another lesson from the Linux philosophy "Some of my recent articles have been about the Linux philosophy and its impact on the daily activities of system administrators like myself. One of the basic tenets of the Linux philosophy is to use software leverage, and one of the important corollaries of that tenet is to automate everything."
  • Gonzalo San Gil, PhD. on 28 Mar 15
     
    Automate everything: Another lesson from the Linux philosophy "Some of my recent articles have been about the Linux philosophy and its impact on the daily activities of system administrators like myself. One of the basic tenets of the Linux philosophy is to use software leverage, and one of the important corollaries of that tenet is to automate everything."
Gonzalo San Gil, PhD.

Senate Passes CISA, The Surveillance Bill Masquerading As A Cybersecurity Bill; Here's Who Sold Out Your Privacy | Techdirt [# ! Key Note...] - 0 views

www.techdirt.com/...ho-sold-out-your-privacy.shtml

surveillance bill masquerade cybersecurity CISA

shared by Gonzalo San Gil, PhD. on 28 Oct 15 - No Cached
    • Gonzalo San Gil, PhD.
      Gonzalo San Gil, PhD. on 28 Oct 15
       
      # ! Between the ''No Neutrality' in Europe and the 'No Privacy' in US, what of the Society's Democratic Rights remain for the politics...? :(
  • Gonzalo San Gil, PhD. on 28 Oct 15
     
    "After rejecting all the good privacy amendments to CISA, the Senate has now officially passed the legislation by a 74 to 21 vote. About the only "good" news is that the vote is lower than the 83 Senators who voted for cloture on it last week. Either way, the Senate basically just passed a bill that will almost certainly be used mainly for warrantless domestic surveillance, rather than any actual cybersecurity concern. "
  • Gonzalo San Gil, PhD. on 28 Oct 15
     
    "After rejecting all the good privacy amendments to CISA, the Senate has now officially passed the legislation by a 74 to 21 vote. About the only "good" news is that the vote is lower than the 83 Senators who voted for cloture on it last week. Either way, the Senate basically just passed a bill that will almost certainly be used mainly for warrantless domestic surveillance, rather than any actual cybersecurity concern. "
Gonzalo San Gil, PhD.

The Red Hat/MS Agreement Molehill | FOSS Force - 0 views

fossforce.com/...red-hatms-agreement-molehill

Microsoft Red Hat agreement proprietary vs open source cloud

shared by Gonzalo San Gil, PhD. on 11 Nov 15 - No Cached
  • Gonzalo San Gil, PhD. on 11 Nov 15
     
    Larry Cafiero First, let me thank those who took the time to alert me last week to the agreement between Red Hat and Microsoft on holding hands in the cloud. All the concern shown in the emails and social media posts were completely welcome, and could be broken up into two basic sentiments: curiosity about my reaction and serving me some crow to eat.
  • Gonzalo San Gil, PhD. on 11 Nov 15
     
    Larry Cafiero First, let me thank those who took the time to alert me last week to the agreement between Red Hat and Microsoft on holding hands in the cloud. All the concern shown in the emails and social media posts were completely welcome, and could be broken up into two basic sentiments: curiosity about my reaction and serving me some crow to eat.
Alexandra IcecreamApps

Android vs. iPhone - Icecream Tech Digest - 0 views

icecreamapps.com/...android-vs-iphone

android vs iphone ios best smartphone mobile operating system os smartphones ssystem

shared by Alexandra IcecreamApps on 17 Dec 15 - No Cached
  • Alexandra IcecreamApps on 17 Dec 15
     
    Lately, smartphone users are divided into two groups: Android supporters and iPhone worshipers. Not mentioning Windows phones, basically the majority of all users tend to have either an Android phone or an iPhone. The Android vs. iPhone battle is a …
  • Alexandra IcecreamApps on 17 Dec 15
     
    Lately, smartphone users are divided into two groups: Android supporters and iPhone worshipers. Not mentioning Windows phones, basically the majority of all users tend to have either an Android phone or an iPhone. The Android vs. iPhone battle is a …
Gonzalo San Gil, PhD.

Configuring Linux for music recording and production | Opensource.com - 0 views

opensource.com/...for-music-recording-production

linux opensource music recording production fun art creativity configuration

shared by Gonzalo San Gil, PhD. on 15 Jan 16 - No Cached
  • Gonzalo San Gil, PhD. on 15 Jan 16
     
    Posted 13 Jan 2016 by Aaron Wolf "In this article, based on my talk at SCaLE 14x this year, we'll cover the basics of configuring your Linux system for music making, highlighting what works best and acknowledging the challenges with recommendations on how to find help."
  • Gonzalo San Gil, PhD. on 15 Jan 16
     
    Posted 13 Jan 2016 by Aaron Wolf "In this article, based on my talk at SCaLE 14x this year, we'll cover the basics of configuring your Linux system for music making, highlighting what works best and acknowledging the challenges with recommendations on how to find help."
1 - 20 of 85 Next › Last »
Showing 20▼ items per page