[LSC] File Format Restrictions for Official Parts

[Chris Dee]

Sorry to interject here (as I guess I’m only supposed to be a listener on
this group). 

 

The version of 82359 in the official library is Tore’s 1999-02 version. The
POV code was put in later and has not been released in an official update.
In any case Chuck Sommerville has not affirmed the CA, so this version
cannot be release as it currently stands.

 

Anyone who suffers rendering degradation will have been using the unofficial
PT version and could suffer all sorts of other problems.

 

Chris

 

   _____  

From: lsc-bounces at ldraw.org [mailto:lsc-bounces at ldraw.org] On Behalf Of
Travis Cobbs
Sent: 16 November 2007 18:32
To: LDraw Standards Committee
Subject: Re: [LSC] File Format Restrictions for Official Parts

 

Take a look at the comments in this part's header:

HYPERLINK
"http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/82359.dat"http://wwwldra
w.org/cgi-bin/ptdetail.cgi?f=parts/82359.dat

I'm pretty sure this type of situation is what William is talking about,
both for parts that are already official and get an update, and for parts
that were put on the tracker under the old rules. 

I'm somewhat ambivalent about the whole thing.  The main problem is that if
we say now that this part has to have the inline POV stripped, then anyone
who is using this part in a model will suddenly see their renders go down in
quality after an official update.  They're not going to be happy about that,
and they'll have good reason to be upset.  On the flip side, since it was
decided that inline POV code shouldn't be in the official library, it's bad
to allow it. 

--Travis

On Nov 16, 2007 10:08 AM, Orion Pobursky <HYPERLINK
"mailto:orion at ldraw.org"orion at ldraw.org> wrote:

William Howard wrote:

>> William Howard wrote:

>>> The official stance is given here

>>> HYPERLINK "http://www.ldraw.org/Article479.html"

\nhttp://www.ldraw.org/Article479.html - which only says that it is

>>> undesirable and not forbidden.

>>>

>>> Old files do matter, as old files quite frequently come back onto the

>>> tracker.  Any parts library specification needs to allow for 

>>> pre-existing files that contain pov-ray code (one such part is the

>>> skelton minifig head), so we need a clause which says that parts

>>> already containing such statements are allowed to keep them, but new 

>>> parts are not allowed to include them.  I shall add something to that

>>> effect.

>>

>> My stance on already official files not conforming to our set

>> restrictions is that they don't need to be fixed right away. However, 

>> if they rotate onto the PT for any reason then they need to been fixed.

>>

>> -Orion

>>



> Even if that means removing pov-ray code - which has been decided by the 

> PT Admins that it can (and should) stay?

>

> W


Maybe we're talking about 2 different things here.  I'm referring to
parts that have already been officially released.  Are you talking about 
parts that are certified but not released?

Basically I see 2 different types of parts: Officially released parts
and those on the PT.  Are far as Parts Standards for Official Parts (or
whatever we decide to call it) document is concerned, the only parts 
that apply are those currently on the PT or any future part submitted to
the PT (this includes Officially Released parts that are submitted to
the PT to be revised or fixed).  In other words, I feel that if it's on 
the PT, then it need to conform to our standards, period.  If it's not
on the PT then it's OK until such time as it is on the PT.


-Orion

--
We don't stop playing because we grow old; 
we grow old because we stop playing
-George Bernard Shaw
_______________________________________________
LSC mailing list
HYPERLINK "mailto:LSC at ldraw.org"LSC at ldraw.org
HYPERLINK "http://five.pairlist.net/mailman/listinfo/lsc"
\nhttp://five.pairlist.net/mailman/listinfo/lsc

 

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.15.34/1134 - Release Date: 16/11/2007
09:52


No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.503 / Virus Database: 269.15.34/1134 - Release Date: 16/11/2007
09:52
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://five.pairlist.net/pipermail/lsc/attachments/20071116/b154fa30/attachment.html>