W3C home > Mailing lists > Public > public-webplatform@w3.org > February 2014

Re: [mdn-compat-importer] Phase 1 modelisation "first stab"

From: Renoir Boulanger <renoir@w3.org>
Date: Tue, 4 Feb 2014 14:06:27 -0500
Cc: List WebPlatform public <public-webplatform@w3.org>
Message-Id: <6A03D03D-3765-4905-8C22-9151070E373D@w3.org>
To: Pat Tressel <ptressel@myuw.net>, David Kirstein <frozenice@frozenice.de>
Hi all!

Here is an update about the project.

Doug and me discussed about the conversion work and here are some notes to describe what we are doing.

Some links to help you analyze:
-  See “CONVERSION STEPS” in [3] for more details about conversion steps:
-  Work is commited in githu within webplatform/mdn-compat-importer in the ‘internal-is-object’ branch [0]
-  At any time, you can see the latest import result change [1] and the data it is using [2]


A short summary of the conversion steps
0. Rework array
    - Make an array of objects
    - origin property gives link to source document
    - category property comes a section within the origin URL and “slugified” (lower case, removing spaces, etc)
    - slug is the last part of the origin URL, “slugified” 
1. Step 1
    - Harmonize browser name strings
    - Invert feature compat data key name and value

  [0]: https://github.com/webplatform/mdn-compat-importer/tree/internal-js-object
  [1]: https://github.com/webplatform/mdn-compat-importer/blob/internal-js-object/data/compat-mdn.json
  [2]: https://gist.github.com/renoirb/8746058
  [3]: https://github.com/webplatform/mdn-compat-importer/blob/internal-js-object/lib/EntityConverter.js#L17


Received on Tuesday, 4 February 2014 19:06:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:13:58 UTC