Skip to main content

Home/ Future of the Web/ Group items tagged decades

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gonzalo San Gil, PhD.

YTS Reaches MPAA Deal But Dotcom Faces Decades in Jail? - TorrentFreak - 0 views

torrentfreak.com/m-faces-decades-in-jail-151108

YTS torrent site agreement MPAA vs Kim Dotcom facing years jail Intellectual Property enforceitics not culture nor copyright enforcement

shared by Gonzalo San Gil, PhD. on 09 Nov 15 - No Cached
  • Gonzalo San Gil, PhD. on 09 Nov 15
     
    " Andy on November 8, 2015 C: 79 Opinion How does YTS, one of the most organized and notorious public torrent sites, strike a deal with Hollywood despite being listed as a notorious market by the U.S. government? We're all curious to know more, but spare a thought for Kim Dotcom. He's in the same country as the YTS operator but faces decades behind bars."
Gonzalo San Gil, PhD.

Let's Encrypt May Improve Security for Regular People More Than Any Other Initiative Th... - 0 views

www.linux.com/...y-other-initiative-this-decade

Let's Encrypt encrypt security regular people initiative linux

shared by Gonzalo San Gil, PhD. on 05 Dec 15 - No Cached
  • Gonzalo San Gil, PhD. on 05 Dec 15
     
    "Let's Encrypt May Improve Security for Regular People More Than Any Other Initiative This Decade"
Gonzalo San Gil, PhD.

How The Sirius XM Ruling Upsets Decades Of Copyright Law Consensus | Techdirt - 1 views

www.techdirt.com/...-copyright-law-consensus.shtml

sirius upset decades copyright consensus

shared by Gonzalo San Gil, PhD. on 03 Oct 14 - No Cached
  • Gonzalo San Gil, PhD. on 03 Oct 14
     
    "from the activist-judges... dept We recently wrote about district court judge Philip Gutierrez ruling against Sirius XM on the issue of streaming pre-1972 recordings. As we noted at the time, the ruling appeared to upset what was considered more or less a settled issue. "
Gonzalo San Gil, PhD.

Analysis Of Pirated Oscar Movies Shows They're Almost All Available... In HD (And Not F... - 0 views

www.techdirt.com/...-almost-all-available-hd.shtml

analysis oscar movies shows avaailable P2P not piracy but promotion

shared by Gonzalo San Gil, PhD. on 26 Jan 15 - No Cached
  • Gonzalo San Gil, PhD. on 26 Jan 15
     
    "from the because-of-course dept As we've mentioned in the past, every year for over a decade, Andy Baio scours the internet to see what Oscar-nominated movies have been put online (the answer is usually almost all of them)."
  • Gonzalo San Gil, PhD. on 26 Jan 15
     
    "from the because-of-course dept As we've mentioned in the past, every year for over a decade, Andy Baio scours the internet to see what Oscar-nominated movies have been put online (the answer is usually almost all of them)."
Gonzalo San Gil, PhD.

SXSW 2015 on BitTorrent: 8.42 GB of Free Music | TorrentFreak - 0 views

torrentfreak.com/t-8-42-gb-of-free-music-150321

sxsw free music bittorrent culture is for share

shared by Gonzalo San Gil, PhD. on 23 Mar 15 - No Cached
  • Gonzalo San Gil, PhD. on 23 Mar 15
     
    " Ernesto on March 21, 2015 C: 0 News The South by Southwest (SXSW) music festival is one of the largest and most popular in the United States. For more than a decade SXSW has been sharing DRM-free songs of the performing artists, 55 GB worth so far. This year's release is the largest thus far with 1,291 tracks totaling more than eight gigabytes. "
  • Gonzalo San Gil, PhD. on 23 Mar 15
     
    " Ernesto on March 21, 2015 C: 0 News The South by Southwest (SXSW) music festival is one of the largest and most popular in the United States. For more than a decade SXSW has been sharing DRM-free songs of the performing artists, 55 GB worth so far. This year's release is the largest thus far with 1,291 tracks totaling more than eight gigabytes. "
Gonzalo San Gil, PhD.

What's your vision for the FSF? Fill out our survey - Free Software Foundation - workin... - 1 views

www.fsf.org/...-the-fsf-fill-out-our-survey-1

free software foundation FSF free software foundation future your people participation survey free working vision software

shared by Gonzalo San Gil, PhD. on 17 Jan 16 - No Cached
  • Gonzalo San Gil, PhD. on 17 Jan 16
     
    [ by Zak Rogoff - Published on Jan 08, 2016 08:01 PM 2015 was the Free Software Foundation's (FSF) thirtieth year defending and advancing computer users' rights. The free software community has sustained the Foundation throughout these decades and been deeply involved in our work. We continue to rely on the expertise of the free software movement to inform our initiatives and strategies. Taking the first step into our next thirty years, we want to hear your feedback, your suggestions, and your vision for the future of the FSF. Fill out the survey now!]
  • Gonzalo San Gil, PhD. on 17 Jan 16
     
    [ by Zak Rogoff - Published on Jan 08, 2016 08:01 PM 2015 was the Free Software Foundation's (FSF) thirtieth year defending and advancing computer users' rights. The free software community has sustained the Foundation throughout these decades and been deeply involved in our work. We continue to rely on the expertise of the free software movement to inform our initiatives and strategies. Taking the first step into our next thirty years, we want to hear your feedback, your suggestions, and your vision for the future of the FSF. Fill out the survey now!]
Gonzalo San Gil, PhD.

Anti-Piracy Group FACT Expands Reach Beyond Hollywood - TorrentFreak [# ! Note] - 0 views

torrentfreak.com/-reach-beyond-hollywood-161110

group fact reach hollywood beyond copyright troll trolling business

shared by Gonzalo San Gil, PhD. on 10 Nov 16 - No Cached
  • Gonzalo San Gil, PhD. on 10 Nov 16
     
    Andy on November 10, 2016 C: 9 News The Federation Against Copyright Theft says that it will branch out into new areas of IP enforcement. For decades the anti-piracy group has relied on Hollywood for much of its business but with that work now being carried out by the MPA and others, FACT will offer services to companies outside the audio-visual sector.
Gonzalo San Gil, PhD.

Comcast's deal with Netflix makes network neutrality obsolete - 0 views

www.washingtonpost.com/...es-network-neutrality-obsolete

neutrality netneutrality network Internet howto works

shared by Gonzalo San Gil, PhD. on 24 Feb 14 - No Cached
  • Gonzalo San Gil, PhD. on 24 Feb 14
     
    "For the past two decades, the Internet has operated as an unregulated, competitive free market. Given the tendency of networked industries to lapse into monopoly-think of AT&T's 70-year hold over telephone service, for example-that's a minor miracle. But recent developments are putting the Internet's decentralized architecture in danger."
Gonzalo San Gil, PhD.

RIAA Now Bullying Fully Licensed, Zero Revenue Music Site | TorrentFreak - 1 views

torrentfreak.com/zero-revenue-music-site-140719

riaa bullying licensed music site copyright enforcement discredit

shared by Gonzalo San Gil, PhD. on 20 Jul 14 - No Cached
  • Gonzalo San Gil, PhD. on 20 Jul 14
     
    " Andy on July 19, 2014 C: 11 Breaking Earlier this week it was reported how the RIAA had decided to turn the licensing thumbscrews on a site offering decades-old radio archives for download. Now another archival site, one that pays thousands of dollars in license fees to BMI, ASCAP and SoundExchange yet makes not a cent, is now in the RIAA spotlight."
Gonzalo San Gil, PhD.

About Grant "Journalistic Truth" (h. 15 Ago 2014) - 0 views

grant-jt.com/about-grant

grant truth journalism crimes against peace mine is cuture censorship

shared by Gonzalo San Gil, PhD. on 22 Jul 14 - No Cached
  • Gonzalo San Gil, PhD. on 22 Jul 14
     
    "Material Evidence Founder: art-project «Material Evidence» Area: Journalism Submission of the applications until the 15 August Subject: crimes against peace Aim: To support journalists all around the world who are ready to prepare unique and truthful material about the situation in the countries which go through the civil conflict. During the last few decades the world's community is observing new, misrespresented democracy rules forced up by the political dictators. The development of democracy should result in the minimization of conflicts and collisions. Nevertheless, a lot of countries unwittingly involved in the complicated game become victims of the geopolitical aggression. We can see now in Syria, Ukraine, Iraq. Art-project «Material Evidence» announces grant for the journalists - Journalistic truth. Any journalist who don't want to stay unaffected by the fate to the countries involved in the world's conflicts are welcome to take part in."
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.

Studios Fed Up With Funding The MPAA: Changes May Be Coming | Techdirt - 0 views

www.techdirt.com/...aa-changes-may-be-coming.shtml

studios fed up funding MPAA so who they work for changes coming let's see

shared by Gonzalo San Gil, PhD. on 29 Jun 15 - No Cached
  • Gonzalo San Gil, PhD. on 29 Jun 15
     
    "from the about-time dept A few years ago, the major record labels finally started to realize that, perhaps, shoveling many millions of dollars to the RIAA was a waste of good money, and they severely cut back funds. You may have noticed that, while the RIAA had taken the lead on the copyright front in the first decade of the new century"
Gonzalo San Gil, PhD.

David Guetta: Piracy Brings Fans to My Concerts | TorrentFreak - 0 views

torrentfreak.com/ngs-fans-to-my-concerts-150706

David Guetta DJ artist piracy brings fans concerts

shared by Gonzalo San Gil, PhD. on 06 Jul 15 - No Cached
  • Gonzalo San Gil, PhD. on 06 Jul 15
     
    " Ernesto on July 6, 2015 C: 17 News For more than a decade piracy has been a hot topic in the music industry. While some of the major labels have tried to eliminate the problem by taking pirates to court, others prefer a more positive approach. DJ and producer David Guetta says that the industry should embrace piracy, noting that it helps him to sell out concerts."
Gonzalo San Gil, PhD.

Xfce: Seven Reasons It's Popular - Datamation - 1 views

www.datamation.com/...seven-reasons-its-popular.html

Xfce GNU_Linux desktop reasons rise popular ity

shared by Gonzalo San Gil, PhD. on 10 Aug 15 - No Cached
  • Gonzalo San Gil, PhD. on 10 Aug 15
     
    "Xfce has a long history of being the third most popular Linux desktop. For over a decade, it trailed behind GNOME and KDE. Then, a few years ago, during the revolts against GNOME and Unity, it became a major contender, "
Gonzalo San Gil, PhD.

Design flaw in Intel processors opens door to rootkits, researcher says | ITworld - 0 views

www.itworld.com/...-rootkits-researcher-says.html

design flaw intel processors opens door rootkits warning research measures now

shared by Gonzalo San Gil, PhD. on 08 Aug 15 - No Cached
  • Gonzalo San Gil, PhD. on 08 Aug 15
     
    "A design flaw in the x86 processor architecture dating back almost two decades could allow attackers to install a rootkit in the low-level firmware of computers, a security researcher said Thursday. Such malware could be undetectable by security products."
Gary Edwards

The Future of the Desktop - ReadWriteWeb by Nova Spivak - 0 views

www.readwriteweb.com/...future_of_the_desktop.php

desktop webos webkit

shared by Gary Edwards on 19 Feb 09 - Cached
  • Gary Edwards on 19 Feb 09
     
    Excellent commentary from Nova Spivak; about as well thought out a discussion as i've ever seen concerning the future of the desktop. Nova sees the emergence of a WebOS, most likely based on JavaScript. This article set off a fire storm of controversy and discussion, but was quickly lost in the dark days of late August/September of 2008, where news of the subsequent collapse of the world financial system and the fear filled USA elections dominated everything. Too bad. this is great stuff. ..... "Everything is moving to the cloud. As we enter the third decade of the Web we are seeing an increasing shift from native desktop applications towards Web-hosted clones that run in browsers. For example, a range of products such as Microsoft Office Live, Google Docs, Zoho, ThinkFree, DabbleDB, Basecamp, and many others now provide Web-based alternatives to the full range of familiar desktop office productivity apps. The same is true for an increasing range of enterprise applications, led by companies such as Salesforce.com, and this process seems to be accelerating. In addition, hosted remote storage for individuals and enterprises of all sizes is now widely available and inexpensive. As these trends continue, what will happen to the desktop and where will it live?" .... Is the desktop of the future going to just be a web-hosted version of the same old-fashioned desktop metaphors we have today? ..... The desktop of the future is going to be a hosted web service ..... The Browser is Going to Swallow Up the Desktop ...... The focus of the desktop will shift from information to attention ...... Users are going to shift from acting as librarians to acting as daytraders. ...... The Webtop will be more social and will leverage and integrate collective intelligence ....... The desktop of the future is going to have powerful semantic search and social search capabilities built-in ....... Interactive shared spaces will replace folders ....... The Portable Desktop ........ The Sma
Gary Edwards

The WHATWG Blog » Blog Archive » The Road to HTML 5: character encoding - 0 views

blog.whatwg.org/d-to-html-5-character-encoding

character-encoding html5 whatwg

shared by Gary Edwards on 13 Feb 09 - Cached
  • Gary Edwards on 13 Feb 09
     
    To sum up: character encoding is complicated, and it has not been made any easier by several decades of poorly written software used by copy-and-paste-educated authors. You should always specify a character encoding on every HTML document, or bad things will happen. You can do it the hard way (HTTP Content-Type header), the easy way ( declaration), or the new way ( attribute), but please do it. The web thanks you. Good post, lots of links to other "MUST READ" commentaries and explanations of character encoding. Including Joel Spolsky and Tim Bray.
Gary Edwards

Convergence of Web, Mobile and Desktop Apps is the Next Phase: AJAX World RIA with Jere... - 0 views

ajax.sys-con.com/576815

Jeremy-Chone ria webkit nexaweb

shared by Gary Edwards on 06 Nov 08 - Cached
  • For SOA applications, the best way to modernize is to componentize and extend the user experience aspect of the application that will in turn enable the applications composition and mashup.
  • While there are many ways that companies measure productivity, Nexaweb has found that the three key criteria for enabling the productivity driven enterprise are based on 1) cost savings resulting from reduced development time and application maintainability; 2) extending the value of existing applications with a future-proof architecture (adding RIA without breaking existing enterprise architecture); and 3) faster time to market by providing a consistent user experience across the various interfaces available throughout the organization.
  • Gary Edwards on 06 Nov 08
     
    While the last decade was focused on the Web, the next phase in the evolution of our industry will be on the convergence of Web, mobile and desktop applications and the ability to extend existing applications with these new technologies for a consistent user experience regardless of how and where the information is viewed,' says Nexaweb CTO Jeremy Chone
Gary Edwards

The Next Battle for the Desktop : Portable RiA Runtime Engines - 0 views

ajax.sys-con.com/548350

ria

shared by Gary Edwards on 06 Nov 08 - Cached
  • The choices for desktop runtimes will be more flexible and will largely be driven by the type of applications rather than the type of platform. It’s likely that desktop computers will eventually ship with two or three different runtimes and that consumers will be more or less ignorant of which one they are using. What will determine the success of one desktop runtime over others will be the execution and development environment. Desktop runtimes that provide the most processing power, speed of execution, and security will dominate. In this scenario the end-user is no longer the customer, it's independent software developers and Integrated Software Vendors that are of primary importance. It’s the developers who will choose the platform on which they create cross-platform applications – the consumer will be largely ignorant of the choices made.  With the exception of download and install differences, the applications will look the same to end-users.
    • Gary Edwards
      Gary Edwards on 06 Nov 08
       
      "It's independent application developers and integrated software vendors that determine which RiA platforms will prevail. Will this group value "cross-platform" RiA? Or will they go for integrated cloud services designed to drive down the cost of development and implementation? Integration into existing business systems i think will trump cross-platform concerns. For sure Microsoft is betting the farm on this.
  • Gary Edwards on 06 Nov 08
     
    The computer desktop - as was the case with newspapers before there was radio and radio before there was television - has become the high ground from which empires are built. While dominance of the desktop has been maintained for the last decade or more by Microsoft, which at one point represented 95% of the desktops used by all consumers, the future is less certain.it will not be a single operating system that prevails. In the end it will be desktop runtimes that become the most important platforms A desktop runtime is a platform that provides a consistent runtime environment regardless of the underlying operating system. Desktop runtimes are already extending beyond their primary target platform, the desktop, to the Fourth Screen - smart phones.
Gary Edwards

The real reason Google is making Chrome | Computerworld Blogs - 0 views

blogs.computerworld.com/reason_google_is_making_chrome

chrome msoffice ria webkit

shared by Gary Edwards on 08 Sep 08 - Cached
  • Gary Edwards on 08 Sep 08
     
    Good analysis by Stephen Vaughan-Nichols. He gets it right. Sort of. Stephen believes that Chrome is desinged to kill MSOffice. Maybe, but i think it's way too late for that. IMHO, Chrome is designed to keep Google and the Open Web in the game. A game that Microsoft is likely to run away with. Microsoft has built an easy to use transiton bridge form MSOffice desktop centric "client/server" computing model to a Web centirc but proprietary RiA-WebStack-Cloud model. In short, there is an on going great transtion of traditional client/server apps to an emerging model we might call client/ WebStack-Cloud-RiA /server computing model. As the world shifts from a Web document model to one driven by Web Applications, there is i believe a complimentary shift towards the advantage Micorsoft holds via the desktop "client/server" monopoly. For Microsoft, this is just a transtion. Painful from a monopolist profitability view point - but unavoidably necessary. The transition is no doubt helped by the OOXML <> XAML "Fixed/flow" Silverlight ready conversion component. MS also has a WebStack-Cloud (Mesh) story that has become an unstoppable juggernaut (Exchange/SharePoint/SQL Server as the WebSTack). WebKit based RiA challengers like Adobe Apollo, Google Chrome, and Apple SproutCore-Cocoa have to figure out how to crack into the great transition. MS has succeeded in protecting their MSOffice monopoly until such time as they had all the transtion pieces in place. They have a decided advantage here. It's also painfully obvious that the while the WebKit guys have incredible innovation on their side, they are still years behind the complete desktop to WebStack-RiA-Cloud to device to legacy servers application story Microsoft is now selling into the marketplace. They also are seriously lacking in developer tools. Still, the future of the Open Web hangs in the balance. Rather than trying to kill MSOffice, i would think a better approach would be that of trying to
  • Gary Edwards on 08 Sep 08
     
    There are five reasons why Google is doing this, and, if you read the comic book closely - yes, I'm serious - and you know technology you can see the reasons for yourself. These, in turn, lead to what I think is Google's real goal for Chrome.
  • Paul Merrell on 09 Sep 08
     
    I'm still keeping the door open on a suspicion that Microsoft may have planned to end the life of MS Office after the new fortress on the server side is ready. The code base is simply too brittle to have a competitive future in the feature wars. I can't get past my belief that if Microsoft saw any future in the traditional client-side office suite, it would have been building a new one a decade ago. Too many serious bugs too deeply buried in spaghetti code to fix; it's far easier to rebuild from the ground up. Word dates to 1984, Excel to 1985, Powerpoint to 1987, All were developed for the Mac, ported years later to Windows. At least Word is still running a deeply flawed 16-bit page layout engine. E.g., page breaks across subdocuments have been broken since Word 1.0. Technology designed to replace yet still largely defined by its predecessor, the IBM Correcting Selectric electro-mechanical typewriter. Mid-80s stand-alone, non-networked computer technology in the World Wide Web era? Where's the future in software architecture developed two decades ago, before the Connected World? I suspect Office's end is near. Microsoft's problem is migrating their locked-in customers to the new fortress on the server side. The bridge is OOXML. In other words, Google doesn't have to kill Office; Microsoft will do that itself. Giving the old cash cow a face lift and fresh coat of lipstick? That's the surest sign that the old cow's owner is keeping a close eye on prices in the commodity hamburger market while squeezing out the last few buckets of milk.
1 - 20 of 68 Next › Last »
Showing 20▼ items per page