[Discuss] [Open Manufacturing] Re: Open Source Hardware Documentation Jam, New York City, April 26-28
Charlie
stirk at costvision.com
Thu Mar 7 22:54:15 UTC 2013
To add to what Bryan already said, which I largely agree with, there are
some other things that you may want to consider. For instance, many items
in the OSHW Documentation Taxonomy have already been defined in ISO 10303
(a.k.a. Standard for the Exchange of Product models a.k.a. STEP). There
are industry-led efforts going on that use ISO 10303 and related standards
for hardware documentation.
www.rassc.org
www.lotar-international.org
http://www.asd-ssg.org/asd-ils-suite-of-specifications
LOTAR is advancing STEP AP242, which contains mechanical CAD geometry and
associated product manufacturing information such as Geometric Dimensioning
and Tolerancing according to ASME 14.41. For non-shape information such
as Product Data Management (BOM) and archiving Meta-data, LOTAR is using
AP239 Product Life Cycle Support (PLCS). The AP242 schema is freely
available from the CAX-IF, which develops recommended practices for
implementers and conducts test rounds for translators. There is a legacy
standard for Technical Data Packaging, AP232, but that is being largely
superseded by AP239 implementations. The AIA/ASD Integrated Logistics
Support (ILS) S-series specifications cover related information for product
support. Most of the S-series specifications that are in development are
using PLCS.
OpenCascade is challenging, but the FreeCAD, OpenPLM, and IfcOpenShell
projects have been able to build usable open source tools based on it.
While I agree that BRL-CAD source code is better managed, both could be
useful for open source hardware documentation development, as can
commercial tools.
Charlie
On Thursday, March 7, 2013 1:48:33 PM UTC-7, Catarina Mota wrote:
>
> Excellent! We're collecting links and info about all existing efforts
> regarding documentation and will bundle them together in a format
> accessible to everyone - probably a list with brief descriptions and links.
>
> On Thu, Mar 7, 2013 at 3:43 PM, Bryan Bishop <kan... at gmail.com<javascript:>
> > wrote:
>
>> On Thu, Mar 7, 2013 at 2:29 PM, Catarina Mota
>> <cata... at openmaterials.org <javascript:>> wrote:
>> > Great, link please?
>>
>> Here's one about the skdb format:
>>
>> http://gnusha.org/skdb/package_spec.html
>> http://gnusha.org/skdb/
>>
>> The biggest hold-ups for this were two-fold:
>>
>> 1) not enough people have opted to review it, suggesting edge cases,
>> proposing alternatives, etc. I think perhaps the best reviewer was
>> Smári McCarthy, because he went off to instead build tangiblebit since
>> he disliked python a great deal... and then he stopped working on
>> that. This was one step ahead of "use dpkg for everything!" and it
>> seemed to work, at least a little.
>>
>> 2) CAD integration, which, in retrospect, is a big project to chew
>> off. I ended up with piles of code for nurbs manipulation that doesn't
>> work, and then lots of opencascade junk laying around. Thankfully, the
>> brlcad crew has been working very hard with the STEP format lately
>> through Step Code Library (an ISO 10303-2xx implementation) and also
>> on their nurbs support. So that's nice progress..
>>
>> The advantage of this is that there is code available in git
>> repositories. I wouldn't mind scrapping it, if there was a better
>> alternative.
>>
>> >> Open source hardware packaging formats like tangiblebit, skdb, mcad
>> (which
>> >> had a slight packaging aspect, although that wasn't the original goal),
>> >> thingdoc, thingscrap, thingzip, cern's repository format, that
>> >> thing/javascript/repo mirror format, and a long list of others have a
>> >> suspicious absence in any of these email threads and it is perplexing.
>> >> Naturally, these formats aren't complete solutions and still need
>> review and
>> >> more contributors, but either propose an alternative (even a proof of
>> >> concept) or submit patches... right? what's the hold up?
>> >
>> > Can you share a document with us with a list and links to everything you
>> > have (or know of) so we can bring those into the discussion?
>>
>> Here are some links to some email threads all the way back to 2008
>> discussing hardware packaging formats:
>>
>> http://heybryan.org/om.html which were collected from
>> https://groups.google.com/group/openmanufacturing
>>
>> as for individual projects:
>>
>> tangiblebit - http://diyhpl.us/cgit/tangiblebit
>> thingdoc - https://github.com/josefprusa/ThingDoc
>> thingzip - http://spec.makerbot.com/ (which seems to be down, I guess
>> they aren't interested in maintaining it)
>> skdb - http://gnusha.org/skdb and
>> http://gnusha.org/skdb/package_spec.html
>> https://github.com/kanzure/skdb
>> thingscrap output format - https://github.com/grevaillot/thingscrap
>> cern - http://www.ohwr.org/projects/bpm-dbe/repository (oops, i was
>> wrong, they have no specification document)
>>
>> I don't remember the other urls.
>>
>> - Bryan
>> http://heybryan.org/
>> 1 512 203 0507
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.oshwa.org/pipermail/discuss/attachments/20130307/3563bb84/attachment-0001.html>
More information about the discuss
mailing list