- The channel debated whether SKDB’s open-source hardware package system needs RDF/semantic-web features; proponents claimed SPARQL over rich ontologies would enable queries like “show me every version of X I can build with my inventory,” while skeptics argued that YAML + Python already supports dependency resolution and any query layer can be added later.

- SKDB’s current design uses a metadata.yaml for dependencies and a data.yaml catalog of parts; parts are Python objects (e.g., Screw("3M")) and CAD geometry is lazy-loaded to conserve memory.

- A proposed “inventory wizard” web form would let users paste ad-hoc lists of tools and parts (“blowtorch”, “24-in drum sander”), map them to canonical SKDB packages, and then recommend buildable projects based on actual stock.

- Lego was used as a compatibility example: interfaces like “stud” and “anti-stud” are stored symbolically in grammar.yaml so the system can answer queries such as “find all packages that need a 2×4 brick” without loading CAD files.

- Participants discussed exposing SKDB bill-of-materials (BOM) data as RDF/URIs to link parts to manufacturer pages, currency converters, and commercial alternatives on the web, while keeping Python objects as the canonical representation and YAML as serialization only.

- Links shared included a quick YAML demo script (http://adl.serveftp.org/~bryan/quick_yaml_demo.py), a HOWTO for turning Python setup.py projects into Debian packages (http://ghantoos.org/2008/10/19/creating-a-deb-package-from-a-python-setuppy/), and the CDBS build-helper docs (http://build-common.alioth.debian.org/cdbs-doc.html).

- A public SKDB presentation outline was posted at http://adl.serveftp.org/skdb/doc/presentations/hplus-summit-2009/outline.

- QuantumG plans to attach a new GPS tracker to a weather balloon and will drive inland to avoid ocean loss.

- Innovation-spotting sites Springwise (http://springwise.com/) and Let’s Evo (http://letsevo.com/) were shared as resources for tracking emerging technologies.