There is a standard schema for material properties, STEP AP235 "Materials
information for the design and verification of products", but it is not
widely implemented. The current version of the AP235 Express schema is
based on PLIB, and harmonized with AP 209ed2 for engineering analysis.
http://www.ap209.org/ap209-edition-2
The AP235 schema is available here
https://github.com/stepcode/stepcode/tree/master/data/ap235
STEPcode can parse the schema and generate class libraries, an API, and
file read/write executable. STEPcode provides a partial implementation of
10303-22, the Standard Data Access Interface, and does not yet include the
database aspects of 10303-22.
The BRL-CAD translator for STEP, based on STEPcode, could be expanded to
support the CAX-IF material identification capability, which can be a key
to material properties. Or one can use the generic STEP User Defined
Attribute functionality. Recommended practices and sample files can be
found at www.cax-if.org.
On Wed, Mar 19, 2014 at 2:15 PM, albert coder <eralbert9...@gmail.com>wrote:
> On Wed, Mar 19, 2014 at 8:32 PM, Christopher Sean Morrison
> <brl...@mac.com> wrote:
> > The potential is phenomenal as there is not much available in the open
> source community for material properties. To me, this project is all about
> providing an easy to use interface that application developers and
> researchers can use to look up material information. We'd like our tools
> (e.g., gqa and rtweight) to be a consumer of that data, so users can do
> things like say "this is birch plywood" and it will have the information
> needed to visualize and analyze, the latter being more important.
>
>
> I got your point but there are some issues or queries I would like to
> converse upon. I tried to approach you on the IRC but unluckily could
> not earn a fruitful discussion there. :) I intended to ask you about
> the desired number of traits of materials(20 40 or even more) because
> that would help in deciding about the initial layout of database
> schema like whether it would be beneficial to continue with the
> existing schema or should we better start afresh? Because the existing
> schema comprises of distinct tables for each trait of the material
> which would result in too many number of tables and that is a kind of
> laborious and cumbersome activity. So keeping extensibility in mind
> (gradually adding more and more traits) we would have to pre-plan it
> so that it does not impede the performance later.
>
> --
> Thanks
> Albert
> www.coderalbert.wordpress.com
> "If you really look closely, most overnight successes took a long
> time." -- Steve Jobs
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> BRL-CAD Developer mailing list
> brlcad-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
