Recently, at a Mobile Monday event, I heard about DiCoDE, a framework developed by Fabian Tilmant.

I immediately noticed some similiarities between DiCoDE and my eReading Reference Architecture (eRRA) method. The "eReading content life cycle" can be mapped to the DiCoDE model. In the eRRA methodology we also work on 2 additional topics the level of the Business Goals and on the Entreprise/ICT Architecture.

DiCoDE complements the architecture by providing a kind of generic Media Business Process Template.

I might sound a little bit "Chinese" but it isn't. These are just methods to make sure your new Media initiatives will succeed

• Achieve your business goals as a Media company
• Make sure you will reach the Consumer by a set of channels
• Develop a plan in terms of resources (IT Systems, People, Data, Entreprise/IT Architecture...)

Combinig DiCoDE and eRRA could achieve great results. Here would be a possible modus-operandi :

1. Defining the business goals (eRRA Methodology, KAOS or GOESIR Method)
2. Analysing the future Content Value Chain with DiCoDE
3. Determine the architecture required to implement the value chain (ex: new Portal, new Production Process...) and document them over the 4 eReading Tiers (Archimate Notation). This provides a TO-BE Architectural overview.
4. Compare the TO-BE Architectural overview with the AS-IS (what elements of the value chain do we have today ?) to provide a project plan

(Note the eRRA methodology can be applied on all kind of Media, not only on eReading. If the "eReader" is a Tablet, there is much more to do than read on the eReader Tier.)

In order to illustrate a litle bit step 3 I have translated DiCoDE in an Architectural Overview over the 4 eRRA tiers.

If you want to give it a try (DiCoDE and/or eRRA), just contact us:

• Fabian Tilmant
• Jean-François Declercq

If you immediately want to know mode about the eRRA, you can get the eBook here :

http://www.appepaper.com/ereading

The DiCoDE ebook is not ready yet, so you'll have to point your browser here :

http://dicodethebook.wordpress.com/dicode-the-model/

With my ebooks I thought I would have a 70% royalty. Amazon gave me only 35%.

I didn't get it until I saw this at the bottom of my KDP reports page:

"Note: 70% royalty option is only available for sales in the US, UK, Canada and Germany. Sales outside the US, UK, Canada and Germany receive 35% royalty. Please see Terms & Conditions for more details on how royalty payments are made."

Source : Foletto - https://github.com/Simbul/baker/issues/13#issuecomment-524407

Current HPub Draft 0.9 [2010-11-21]

1. Abstract

The HPub (HTML Publication) standard is a file format designed to release rich content books in a simple and manageable package.

2. The principles

We want a digital publishing format that:

1. Allows great designs
2. Allows both pixel-perfect and flexible reflowable publications
3. Is simple for authors
4. Is simple for parsers

3. The Spec

1. An HPub publication is a normal .zip file with ".hpub" extension. Unpacked books are allowed.
2. The content format must be HTML5.
3. It must contain at least one HTML file with extension "html".
4. If more than one HTML file are included, the pagination order must be alphabetical.
5. Any HTML file contained in subfolders must be excluded from the pagination order.
6. All the assets (CSS, images, JS, ...) must be included in the package and referenced relatively from the HTML5 files.