Subject:
|
Re: Proposal: New Part *NAMING* System.
|
Newsgroups:
|
lugnet.db.brictionary
|
Date:
|
Mon, 29 Sep 2003 03:27:14 GMT
|
Viewed:
|
11072 times
|
| |
|
|
In lugnet.db.brictionary, Ray Sanders wrote:
> In lugnet.db.brictionary, Dan Boger wrote:
> > On Tue, Sep 23, 2003 at 12:12:09AM +0000, Ray Sanders wrote:
> > > I like the ideas proposed here. They are almost identical to something
> > > I've been tossing around for a while with some other folks. Anyone out
> > > there interested in being involved in creating a public catalog ?
> >
> > We're very interested in having a public system set up, and would love
> > working with one. It's something that we've been planning to do (with
> > LDraw) for quite some time now - we even posted back in the day, to try
> > and get some momentum going, but it never took off.
> >
> > What do you have in mind? How can we help?
> >
> > Dan
>
> This is a working draft of what I have in mind - Ray
Ray - this sounds like a very ambitious (and cool!) project :-) See some
questions inline.
> H) Every item in the catalog will be assigned an abstract number at the time it
> is added. These number will not have any relationship to mold numbers that may
> or may not be stamped on the part. If a part is added multiple time, then
> successive abstract numbers will be aliased back to the original, they should
> not be deleted or reused.
Why not block some numbers off for natural groupings of parts? Would say, a 1x2
brick with click hinge (2 prongs) and the same with 1 prong (that interface with
each other) have totally unrelated numbers?
One thing I like about the LDraw library is many (not all...) parts of similar
nature are grouped. At least paired - male/female hinges, etc.
> K) Decorated parts should have their own abstract number, but should also be
> related to the undecorated base part (which means adding the decorated part
> implies adding the undecorated base part if it does not already exist).
Again, why not a modifier of the part the decoration is printed on?
> P) The catalog will contain physical information about parts and sets (if
> possible). Physical information being weight (each or by 100s), dimensions
> (which is going to be difficult for irregular parts), clumping/nesting (a metric
> indicating the ability of the part to nest with like parts for
> storage/shipping).
Why information about sets? Couldn't this simply interface with a set inventory
somewhere else that used the numbering system?
> Q) The catalog will include information about instructions (multiple versions),
> catalogs and other Lego items which are not strictly speaking parts or sets.
> Examples of these would be promo toothbrushes, backpacks, watches, etc.
Not understanding this either. IMO, the important goal is to create a part
catalog, inventorying, promo databases, etc are separate efforts (in my mind).
Please take the questions in stride - I'm just trying to understand better. No
doubt you have very valid reasons for the points you outline, I'm just trying to
see what they are :-)
I'd love to see something come out of this that can bridge some of the gaps in
the various parts libraries out there.
-Tim
|
|
Message has 1 Reply:
 | | Re: Proposal: New Part *NAMING* System.
|
| Just to through my 2 cents in (even though I'm two weeks behind the rest of this thread ;-) )...I'm definitely interested in being a part of this project. (Being a data-organization junkie may have something to do with it.) Let me know what I need (...) (23 years ago, 13-Oct-03, to lugnet.db.brictionary)
|
Message is in Reply To:
| | Re: Proposal: New Part *NAMING* System.
|
| (...) This is a working draft of what I have in mind - Ray ===...=== Conceptural Outline for a Public Parts Catalog A) The results of the effort will be held under a public content license (such as Open Content or Creative Commons). The results will (...) (23 years ago, 28-Sep-03, to lugnet.db.brictionary)
|
11 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
|
|
|
|
