Toolleeo's links
A Data Package consists of:
- Metadata that describes the structure and contents of the package
- Resources such as data files that form the contents of the package
- The Data Package metadata is stored in a "descriptor". This descriptor is what makes a collection of data a Data Package. The structure of this descriptor is the main content of the specification below.
In addition to this descriptor a data package will include other resources such as data files. The Data Package specification does NOT impose any requirements on their form or structure and can therefore be used for packaging any kind of data.
The data included in the package may be provided as:
- Files bundled locally with the package descriptor
- Remote resources, referenced by URL
- "Inline" data (see below) which is included directly in the descriptor
pngquant is a command-line utility and a library for lossy compression of PNG images.
The conversion reduces file sizes significantly (often as much as 70%) and preserves full alpha transparency. Generated images are compatible with all web browsers and operating systems.
Pngquant is a free, open source and cross-platform command-line lossy PNG compressor. It is based on a portable libimagequant library and is written in C99. It reduces the file size significantly by converting the PNG image to more efficient 8-bit PNG format and preserves full alpha transparency. As you may already know, 8-bit PNG files are often 60-80% smaller than 24/32-bit PNG files. The images compressed using Pngquant are fully-compatible with all web browsers and operating systems. Pngquant can compress one or multiple images at once.
BibJSON is a convention for representing bibliographic metadata in JSON; it makes it easy to share and use bibliographic metadata online.
It is a form of JSON - a simple, useful and common way of representing data on the web; we use it to shift information around between our apps.
- A BibJSON record is a JSON object
- A BibJSON collection is a JSON object containing "metadata" followed by "records"
- The "records" key in a collection points to a list of BibJSON records (JSON objects)
- The collection and the records both have the "collection" key, and their value should be the same
- Each record should have a "cid" - an identifier unique within the parent collection
- Each record should have a "type" - such as "article", "book", or even "author"
- Record type places no constraint on what can be placed in the record
- The default set of keys are based on the bibtex keys
- BibJSON keys are lowercase, no spaces, and usually singular
- The keys can point to strings, lists, or objects
- Any thing that is a simple string should remain so
- Where object complexity is required, make it an object
- Where additional keys are namespaced, include a "namespace" declaration in the collection "metadata"
- BibJSON APIs may return other metadata relevant to the parent app; developers can identify such metadata by prefixing the key with "_"; just ignore what is not useful to you
A community driven open source initiative to create a JSON based standard for resumes.
Why?
- It makes it easier to understand the structure of JSON files.
- The output is valid JavaScript which can be used directly in code.
- It's very helpful when writing queries for tools like jq.
FCL stands for Fuzzy Control Language, which is a standard for Fuzzy Control Programming published by the International Electrotechnical Commission (IEC). The specifications for the FCL syntax can be found in IEC document 61131-7.
I'm generating a PDF document with pdflatex (more precisely, latexmk invoked from TexMaker 3.4. My LaTeX install is TeXLive 20120719). I can read the document fine in Okular and Gmail's attachment preview, but a colleague that runs Acrobat Reader on Windows reports: "There was a problem reading this document (131)".