Travis Cobbs Wrote:
-------------------------------------------------------
> Please note, Allen, that only LSC members can post
> to the LSC forum, so if you need a response from
> someone else, you need to post in another forum.
It's hard to know where to ask!
>
I happily endorse what Chris suggests.
However, I still don't know why this needs the review of the LSC. The LDraw.org Official Library Header Specification does not spell out exactly what {RealName} values are permitted, which would imply that any RealName is permissible. For example, the string "The LEGO Universe Team" is nowhere to be found in the specification, although Chris attests it is currently in use. Presumably, "LEGO Digital Designer" will likewise not appear in the specification. Thus I am not sure why LSC approval is necessary here.
I ask all this because I would hate to see parts get bogged down on the Tracker because of the LSC. In this case, as long as the part is following the header specification, I think it's fine.
Allen
-------------------------------------------------------
> Please note, Allen, that only LSC members can post
> to the LSC forum, so if you need a response from
> someone else, you need to post in another forum.
It's hard to know where to ask!
>
Chris Dee Wrote:> I am asking about (a), but not "if" they should
> have attribution in the history, but "how" that
> attribution should appear:
> We use "0 !HISTORY YYYY-MM-DD {The LEGO Universe
> Team} Original part shape" for LEGO Universe parts
> and would like the LSC to rule on the suggestion
> of
> "0 HISTORY YYYY-MM-DD {LEGO Digital Designer}
> Original part shape" for LDD derived parts.
>
> Your opinion (as a member of the LSC) matters
> because the LSC controls the Official Library
> Header Specification.
>
I happily endorse what Chris suggests.
However, I still don't know why this needs the review of the LSC. The LDraw.org Official Library Header Specification does not spell out exactly what {RealName} values are permitted, which would imply that any RealName is permissible. For example, the string "The LEGO Universe Team" is nowhere to be found in the specification, although Chris attests it is currently in use. Presumably, "LEGO Digital Designer" will likewise not appear in the specification. Thus I am not sure why LSC approval is necessary here.
I ask all this because I would hate to see parts get bogged down on the Tracker because of the LSC. In this case, as long as the part is following the header specification, I think it's fine.
Allen