| |
In lugnet.admin.database, Steve Bliss writes:
> And it's not actually part names, but a parts identification database,
> right? Having standard/prefered names is good, but it's the pictures (and
> maybe schematics) that actually identify the part.
Steve, I totally agree what is needed is a complete classification/taxonomy
system so you can find a part. The naming component is useful and interesting
but this project should be a parts database not just a name database.
If the classification is structured correctly not only should you be easily
able to find a given part but it should be easy to see similar parts oe see the
progression of a given part type from its most basic form to its most complex
form. something like this would help a pretty wide viriety of users.
Jim
hughesj@one.net
|
|
Message has 2 Replies:
Message is in Reply To:
 | | Re: Newsgroup for this (was Re: The Bricktionary project)
|
| (...) Sounds good. Right place in the hierarchy. (...) And it's not actually part names, but a parts identification database, right? Having standard/prefered names is good, but it's the pictures (and maybe schematics) that actually identify the (...) (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general, lugnet.admin.general)
|
80 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in Database
|
|
|
|
|
|
