This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ncc-services-wg@ripe.net/
[ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
- Next message (by thread): [ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alex Le Heux
aleheux at kobo.com
Fri Mar 15 23:01:07 CET 2013
Hi, > The canonical and binding format of all documents is plain text in > UTF-8 encoding. > If a document can not reasonably be stored as plain text, > PDF/A-1a[1] will be used. > If any document exists in both plain text and PDF/A-1a, plain text is binding. > Any other form is considered non-binding as soon as a plain text or > PDF/A-1a variant exist. > All legacy documents which are still valid or relevant to current > policies will be transformed within a year of this proposal becoming > policy. > > > The reasoning behind this should be obvious: Ensure that all documents > will be in the most simple-to-parse format now and forever. For policy documents: +1 Other RIPE documents may be graphics-heavy, although most probably won't be. It would be good to have a provision for non-policy documents that just can't be represented in plain text. Alex
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
- Next message (by thread): [ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]