Toolleeo's links
JSON manipulation and transformation tool. Contribute to ldn-softdev/jtc development by creating an account on GitHub.
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
(JSON Query?) is sed-like processor for JSON data; can be used to process JSON files and data streams and perform operations such as those allowed by cat, sed, grep and awk on regular text files.
A minimal clone of Wunderlist, with 30% of its features. GTD oriented. It stores the task list in a hidden JSON file in the home directory, making it easy to backup or share them.
Todo manager with advanced features; dedicated synchronization server available; many plugins and related tools; healthy software project.
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.
json incremental digger. Contribute to simeji/jid development by creating an account on GitHub.
JSON has taken over the world. Today, when any two applications communicate with each other across the internet, odds are they do so using JSON.
The article describes the history of JSON starting from the aim at having a common information exchange format from XML and beyond.
by Stian Eikeland
Python script to parse bookmarks exported from ffox in JSON format in the html format used by emacs-w3m, optionally merging with an existing emacs-w3m bookmark file. Note that nested folders in the fffox bookmarks are flattened, as emacs-w3m bookmark categories are all on one level.
Will cope with the current (Nov 2009) bug in ffox which exports badly formed JSON, but if other parse errors occur run the JSON through a validator.