Skip to main content

Home/ Future of the Web/ Group items tagged 4

Rss Feed Group items tagged

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

Internet Users in OECD Countries - 2016 - 0 views

www.internetworldstats.com/stats16.htm

internet users oecd countries OCDE

shared by Gonzalo San Gil, PhD. on 18 Sep 16 - No Cached
  • Gonzalo San Gil, PhD. on 18 Sep 16
     
    "NOTES: (1) OECD Countries Internet User Statistics were updated for June 30, 2016. (2) Growth percentage represents the increase in the number of Internet users between the years 2000 and 2016. (3) The most recent user information comes from data published by Facebook, International Telecommunications Union, official country telecom reports, and other trustworthy research sources. (4) Data from this site may be cited, giving the due credit and establishing a link back to www.internetworldstats.com. Copyright © 2016, Miniwatts Marketing Group. All rights reserved worldwide."
Gonzalo San Gil, PhD.

Anti-Piracy Outfits Caught Fabricating Takedown Notices - TorrentFreak - 1 views

torrentfreak.com/cating-takedown-notices-160918

antipiracy outfits caught fabrication piracy links takedown notices boycott Internet Old Media

shared by Gonzalo San Gil, PhD. on 18 Sep 16 - No Cached
  • Gonzalo San Gil, PhD. on 18 Sep 16
     
    " Ernesto on September 18, 2016 C: 4 Opinion Not all anti-piracy vendors play fair when it comes to removing copyright-infringing content from the Internet. In fact, there is clear and convincing evidence that several companies 'make up' links that have never even existed, perhaps in part to boost their own numbers."
Gonzalo San Gil, PhD.

Spotify takes an early weekend, has outage on Friday afternoon [# ! Alternatives Down...?] - 0 views

mashable.com/...-goes-down-on-friday-afternoon

spotify outage Industry sabotage ? #HollywoodvsSiliconValley again alternatives Big Media #Big Labels down back future

shared by Gonzalo San Gil, PhD. on 16 Oct 16 - No Cached
  • Gonzalo San Gil, PhD. on 16 Oct 16
     
    "It has been a long week, and we all deserve to take off a little early. Spotify knows that feel. Its service went down in various part of the U.S. and Europe on Friday afternoon. An outage indicator showed problems that began a little after 4:00 P.M. EST."
Gonzalo San Gil, PhD.

Ten Years in Jail For UK Internet Pirates: How the New Bill Reads - TorrentFreak - 0 views

torrentfreak.com/-how-the-new-bill-reads-161204

jail internet pirates bill reads

shared by Gonzalo San Gil, PhD. on 05 Dec 16 - No Cached
  • Gonzalo San Gil, PhD. on 05 Dec 16
     
    " By Andy on December 4, 2016 C: 102 News The Digital Economy Bill is currently at the report stage. It hasn't yet become law and could still be amended. However, as things stand those who upload any amount of infringing content to the Internet could face up to 10 years in jail. With the latest bill now published, we take a look at how file-sharers could be affected."
Gonzalo San Gil, PhD.

4 tips for creating a Wikipedia article | Opensource.com - 2 views

opensource.com/...ips-creating-wikipedia-article

How Towriting tips #HowTo write wikipedia article contribute open source global knowledge

shared by Gonzalo San Gil, PhD. on 24 Nov 16 - No Cached
  • Gonzalo San Gil, PhD. on 24 Nov 16
     
    "It is human nature to want to share the enthusiasm you have for a subject or project with others. Wikipedia is a great place for that, where you can record your expertise and create a fact-based touchpoint for your interest. "
Gonzalo San Gil, PhD.

Pirate Blocking Injunctions Could Be Abused, Researchers Say - TorrentFreak - 0 views

torrentfreak.com/-abused-researchers-say-160704

pirate sites blocking abuses piracy

shared by Gonzalo San Gil, PhD. on 04 Jul 16 - No Cached
  • Gonzalo San Gil, PhD. on 04 Jul 16
     
    " By Andy on July 4, 2016 C: 19 News Researchers at Western Sydney University and King's College London have published a paper comparing various 'pirate' blocking mechanisms around the world. While all have shortcomings, the regime in the UK is highlighted as being open to potential future abuse."
Gonzalo San Gil, PhD.

How to integrate Git into your everyday workflow | Opensource.com - 0 views

opensource.com/...graphical-tools-git

how to integration git your daily workflow Revision Control System RCS

shared by Gonzalo San Gil, PhD. on 03 Aug 16 - No Cached
  • Gonzalo San Gil, PhD. on 03 Aug 16
     
    "Read: Part 1: What is Git? Part 2: Getting started with Git Part 3: Creating your first Git repository Part 4: How to restore older file versions in Git Part 5: 3 graphical tools for Git"
Gonzalo San Gil, PhD.

U.N. passes landmark resolution condemning internet shutdowns - Access Now - 1 views

www.accessnow.org/-condemning-internet-shutdowns

UN passes landmark resolution access Human Rights Internet shutdown condemn

shared by Gonzalo San Gil, PhD. on 09 Jul 16 - No Cached
  • Gonzalo San Gil, PhD. on 09 Jul 16
     
    "1 July 2016 | 4:48 am Tweet Share GENEVA - Today the United Nations Human Rights Council agreed by consensus to a resolution supporting human rights online, despite efforts by hostile states to eliminate key provisions in the text. The landmark document specifically condemns internet shutdowns and renews 2012 and 2014 resolutions that declared, unequivocally, that human rights apply online just as they do offline."
Gonzalo San Gil, PhD.

U.S. military official: Internet shutdowns don't help during conflict - Access Now - 0 views

www.accessnow.org/ternet-shutdowns-isis-conflict

internet shutdown no help during armed conflicts war freedom of expression freedom of access Human Rights democracy supreme VALUE

shared by Gonzalo San Gil, PhD. on 25 Jun 16 - No Cached
  • Gonzalo San Gil, PhD. on 25 Jun 16
     
    "22 June 2016 | 4:49 pm Today the U.S. military gave a resounding rebuke to U.S. presidential candidate Donald Trump's call to shut down the internet in the fight against the Islamic State of Iraq and the Levant (ISIL). Politico reports from a House Armed Services Committee hearing that Acting Assistant Defense Secretary Thomas Atkins testified:"
Gonzalo San Gil, PhD.

ACTA: Total Victory for Citizens and Democracy! | La Quadrature du Net - 0 views

www.laquadrature.net/...ory-for-citizens-and-democracy

acta citizens victory net democracy Internet

shared by Gonzalo San Gil, PhD. on 06 Jul 12 - No Cached
  • Gonzalo San Gil, PhD. on 06 Jul 12
     
    [Submitted on 4 Jul 2012 - 10:40 ACTA Karel De Gucht press release Printer-friendly version Send by email Français Strasbourg, July 4th 2012 - The European Parliament rejected ACTA1 by a huge majority, killing it for good. This is a major victory for the multitude of connected citizens and organizations who worked hard for years, but also a great hope on a global scale for a better democracy. On the ruins of ACTA we must now build a positive copyright reform2, taking into account our rights instead of attacking them. The ACTA victory must resonate as a wake up call for lawmakers: Fundamental freedoms as well as the free and open Internet must prevail over private interests. ...]
Gonzalo San Gil, PhD.

EUROPA - PRESS RELEASES - Press release - Lack of choice driving demand for film downloads - 0 views

europa.eu/...press-release_IP-14-120_en.htm

europa lack choice driving demand film downloads

shared by Gonzalo San Gil, PhD. on 14 Feb 14 - No Cached
  • Gonzalo San Gil, PhD. on 14 Feb 14
     
    "Lack of choice driving demand for film downloads Nearly 70% of Europeans download or stream films for free, whether legally or illegally, according to a new European Commission study on audience behaviour. It also finds that 40% of smartphone owners and more than 60% of tablet owners watch films on their devices. The study finds that this is not surprising because, while the public takes a lot of interest in films as a whole, the nearest cinema is often some distance from them and the choice on screen is frequently rather limited. It suggests that the European film industry can increase revenues by exploiting different types of profit-making online platforms to increase the availability of films and reach new audiences. The audience behaviour study is based on research, analysis and interviews with audiences in 10 Member States - the UK, France, Italy, Spain, Germany, Poland, Croatia, Romania, Lithuania and Denmark. Nearly 5 000 people aged from 4-50 were asked about their film habits and preferences."
Gonzalo San Gil, PhD.

EU high court strikes down metadata collection law | Ars Technica - 1 views

arstechnica.com/...s-down-metadata-collection-law

court strikes down metadata collection law Europe legas precedent set

shared by Gonzalo San Gil, PhD. on 08 Apr 14 - No Cached
  • Gonzalo San Gil, PhD. on 08 Apr 14
     
    "Citizens made to feel that they "are the subject of constant surveillance." by Cyrus Farivar - Apr 8 2014, 4:25pm CEST"
  • Paul Merrell on 09 Apr 14
     
    Just finished reading the court's opinion. I can only wish that the U.S. government had such fine-tuned respect for civil rights Not quoted in the linked article, but opinion paragraph 68 is very bad news for U.S. service providers: "In the second place, it should be added that that directive does not require the data in question to be retained within the European Union, with the result that it cannot be held that the control, explicitly required by Article 8(3) of the Charter, by an independent authority of compliance with the requirements of protection and security, as referred to in the two previous paragraphs, is fully ensured. Such a control, carried out on the basis of EU law, is an essential component of the protection of individuals with regard to the processing of personal data (see, to that effect, Case C-614/10 Commission v Austria EU:C:2012:631, paragraph 37).". The Court is holding, in other words, that an E.U. network *must* be created that can prevent user's data from being transported outside the E.U., that user's data retained for law enforcement or national defense purposes cannot be transmitted or stored outside the E.U. It will take awhile for this to be transposed into national laws. But this is very good news for folks in the E.U. and for civil libertarians globally.
Gonzalo San Gil, PhD.

UK Police: Enforcement Won't Work Against Piracy | TorrentFreak - 0 views

torrentfreak.com/ont-work-against-piracy-140615

UK police IP enforcement does not work against piracy new business model

shared by Gonzalo San Gil, PhD. on 15 Jun 14 - No Cached
  • Gonzalo San Gil, PhD. on 15 Jun 14
     
    " By Andy on June 15, 2014 C: 33 News The Commissioner of City of London Police admitted this week that just 4% to 10% of sites shut down when contacted by the new Intellectual Property Crime Unit. Alongside odd comments about the threat of "BitNet" and Tor making up "90% of the Internet", Leppard noted that enforcement will not provide a way out of the piracy problem. cityoflondonpoliceThis week's IP Enforcement Summit in London"
Gonzalo San Gil, PhD.

Oxford Journals | Social Sciences | Community Development Journal - 0 views

cdj.oxfordjournals.org

community development journal

shared by Gonzalo San Gil, PhD. on 12 May 14 - Cached
  • Gonzalo San Gil, PhD. on 12 May 14
     
    "View Current Issue (Volume 49 Issue 2 April 2014) Advance AccessBrowse the ArchiveView all Supplements Published 4 times a year and circulated in more than 80 countries, the leading international journal in its field, covering a wide range of topics, reviewing significant developments and providing a forum for cutting-edge debates about theory and practice. It adopts a broad definition of community development to include policy, planning and action as they impact on the life of communities. It seeks to publish critically focused articles which challenge received wisdom, report and discuss innovative practices, and relate issues of community development to questions of social justice, diversity and environmental sustainability."
Gonzalo San Gil, PhD.

WordPress 4.0 Designed for Improved Security, Usability, Stability - 1 views

www.eweek.com/...urity-usability-stability.html

wordpress security usability stability improved SSL

shared by Gonzalo San Gil, PhD. on 08 Sep 14 - No Cached
  • Gonzalo San Gil, PhD. on 08 Sep 14
     
    "Provides user enhancements and tightens SSL security."
  • Gonzalo San Gil, PhD. on 08 Sep 14
     
    "rovides user enhancements and tightens SSL security."
Gonzalo San Gil, PhD.

Internet piracy traffic - Havocscope [# ! + Note] - 0 views

www.havocscope.com/internet-piracy-traffic

free download Internet 1 out of 4 culture advance industry shift

shared by Gonzalo San Gil, PhD. on 29 Apr 15 - No Cached
    • Gonzalo San Gil, PhD.
      Gonzalo San Gil, PhD. on 29 Apr 15
       
      # ! perhaps 1 of every 4 Dollars/Users from Internet Busines -for the ISPs included- comes from such 'pirates'... (# ! that's what can be named as 'A #Culture'... # ! ... to be '#Protected...)
  • Gonzalo San Gil, PhD. on 29 Apr 15
     
    [n Counterfeit Goods Piracy on the Internet of movies, music, video games and television shows make up to 24 percent of all Internet traffic worldwide. Source: Gautham Nagesh, "Study: 24 percent of Web traffic involves piracy," Hillicon Valley Blog, The Hill, February 1, 2011. ]
  • Gonzalo San Gil, PhD. on 29 Apr 15
     
    [n Counterfeit Goods Piracy on the Internet of movies, music, video games and television shows make up to 24 percent of all Internet traffic worldwide. Source: Gautham Nagesh, "Study: 24 percent of Web traffic involves piracy," Hillicon Valley Blog, The Hill, February 1, 2011. ]
Gary Edwards

» 21 Facts About NSA Snooping That Every American Should Know Alex Jones' Inf... - 0 views

www.infowars.com/hat-every-american-should-know

NSA-Patriot-Act-NDAA NSA-Whistleblower PRISM Echelon-SIGINT

shared by Gary Edwards on 19 Jun 13 - No Cached
  • Gary Edwards on 19 Jun 13
     
    NSA-PRISM-Echelon in a nutshell.  The list below is a short sample.  Each fact is documented, and well worth the time reading. "The following are 21 facts about NSA snooping that every American should know…" #1 According to CNET, the NSA told Congress during a recent classified briefing that it does not need court authorization to listen to domestic phone calls… #2 According to U.S. Representative Loretta Sanchez, members of Congress learned "significantly more than what is out in the media today" about NSA snooping during that classified briefing. #3 The content of all of our phone calls is being recorded and stored.  The following is a from a transcript of an exchange between Erin Burnett of CNN and former FBI counterterrorism agent Tim Clemente which took place just last month… #4 The chief technology officer at the CIA, Gus Hunt, made the following statement back in March… "We fundamentally try to collect everything and hang onto it forever." #5 During a Senate Judiciary Oversight Committee hearing in March 2011, FBI Director Robert Mueller admitted that the intelligence community has the ability to access emails "as they come in"… #6 Back in 2007, Director of National Intelligence Michael McConnell told Congress that the president has the "constitutional authority" to authorize domestic spying without warrants no matter when the law says. #7 The Director Of National Intelligence James Clapper recently told Congress that the NSA was not collecting any information about American citizens.  When the media confronted him about his lie, he explained that he "responded in what I thought was the most truthful, or least untruthful manner". #8 The Washington Post is reporting that the NSA has four primary data collection systems… MAINWAY, MARINA, METADATA, PRISM #9 The NSA knows pretty much everything that you are doing on the Internet.  The following is a short excerpt from a recent Yahoo article… #10 The NSA is suppose
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.

Most Aussie Pirates Are the Industry's Best Customers - TorrentFreak - 0 views

torrentfreak.com/ndustrys-best-customers-150722

aussie pirates best industry customers sharing promotion

shared by Gonzalo San Gil, PhD. on 22 Jul 15 - No Cached
  • Gonzalo San Gil, PhD. on 22 Jul 15
     
    " Andy on July 22, 2015 C: 4 Breaking A survey commission by the Australian government has found that more than a quarter of all local Internet users consume content illegally online. Interestingly, while 7% of the population were found to be hardcore pirates who spend nothing on legitimate content, those who pirate and also buy legally are the industry's best customers"
« First ‹ Previous 61 - 80 of 177 Next › Last »
Showing 20▼ items per page