During my time at Ooligan, I have been told by multiple people that XML coding is the portion of the Ooligan workflow that they are most unfamiliar with and therefore most anxious about volunteering for. It’s not hard to see why XML seems daunting or confusing: the work is done by the editorial department, but it requires coding tags one would expect to see in the digital department, and the product is used exclusively by the design department. It’s easy to get lost in all of that. If the work requires coding, why isn’t it done in the digital department? If the product is only used by the design department, why don’t they do the work? To help clarify, here’s a crash course in XML.
What started as a clause in the Digital Millennium Copyright Act of 1998 to protect the infringement of copyrighted works, such as movies, books and music, has blossomed into a full-fledged debate on who owns, who can modify, and who can repair the products consumers purchase. These products can range from cell phones and cars to children’s toys and ebooks, making it almost a certainty that everyone has at least one DRM-protected product in their home. The companies who place the DRM on these products can control who uses, modifies, and distributes the copyrighted works and products.
Over the last year of taking classes in the publishing program, I’ve developed a drinking game to gauge technophobia. It’s best to play this game on the first day of the term, when we’re all introducing ourselves and stating why we’re here. Drink every time: Someone zealously praises a book as an “artifact” or an […]
If you had told me last summer that by this summer I would be the Ooligan digital manager, I would have been like . . . Bock-bock-ba-what? Like many other word-lovers who have been forever entrenched in the humanities and social sciences, the idea of anything computery seems out of line. My identity revolved around […]