That's a reasonable goal for a complete listing.  That would
depend on the exact materials and parts sources still being available.
Otherwise you are redesigning it some.
None of SKDB is complete to the level of tested with real materials and designs yet.

Kurt and Bryan,

Excellent job with the formats.   I have added the first cut of
parts.xml as an import format for bomfire.com.  I like the friendly
readability of the yaml, but there doesn't seem to be any formal
structure for the parts section so I couldn't add it as readily.

I do have a couple suggestions for parts.xml: Reference Designators,
Substitutions and Subassemblies. I'd be glad to team up for that
section if you are amiable to adding more power to it.

1. Reference Designators (aka part names) such as R1, C1, M1, etc are
pretty common practice for communicating about parts so those would be
a good field.
Example:
<part designator="R1" ></part>
or
<part name="R1"></part>

2. Substitutions are part of a maturing project.  The driver for
substitutions may be different (different product configurations,
robust part availability, cost, whatever), but in all cases expressing
them unambiguously in a parts list should clarify things to some
otherwise confused people.
Example:
<parts name="hamburger">
<substitutions name="type of bun" criteria="manual" default="white">
<sub name="white">
<part>1 top bun</part>
<part>1 button bun </part>
</sub>
<sub name="low carb">
</sub>
</substitutions>
</parts>

3. Subassemblies.   Say you have a circuit board controlling an
electromechanical beast of burden.  Both the circuit board and the
beast of burden are almost complete projects in their own right and
having some sort of hierarchy will help organize them logically.
Basically, parts should be able to be included inside parts.
Example:

<parts>
<parts name="Circuit Board">
<part>Microcontroller+</part>
</parts>
<parts name="Beast of Burden">
<part>Induction Motor+</part>
</parts>
<parts>

or a little cleaner version without direct nesting:

<parts>
<part="Circuit Board"/>
<part="Beast of Burden"/>
</parts>

<parts name="Circuit Board">
<part>Microcontroller+</part>
</parts>
<parts name="Beast of Burden">
<part>Induction Motor+</part>
</parts>

Thanks,
Matt Bond
bomfire.com

On Aug 6, 2012, at 10:50 PM, Matt Bond wrote:

Begin forwarded message:

From: Kurt Tomlinson <k...@openhardwarehub.com>
Subject: Re: [OH Updates] oProject: Open Source Hardware Project Format
Date: August 4, 2012 8:02:30 AM MST
To: John Griessen <j...@industromatic.com>
Cc: upda...@lists.openhardwaresummit.org

Oh okay. My bad. I thought the point of being able to "download"
hardware was that the process would be almost entirely independent of
the user. I was just hoping for a little magic ;-)

Best,
Kurt

_______________________________________________
updates mailing list
upda...@lists.openhardwaresummit.org
http://lists.openhardwaresummit.org/listinfo.cgi/updates-openhardware...

--
- Bryan
http://heybryan.org/
1 512 203 0507