Here's the latest draft. Discuss!! (Note: there is a quote bug that's removing the text between <>. Be aware of that and restore the text if needed)
--
The Offical Model Repository Specification
Version: 0.3 (will turn 1.0.0 upon ratification by the LSC)
Author: Orion Pobursky

Purpose:
--------
The Official Model Repository (OMR) is a database of file in the LDraw File Format describing models that are released as sets by Lego®.

For consistency between models and ease of indexing by software, a standard for the file headers, names, and hierarchy in the OMR is needed. This document will outline the extra requirements (in addition to those set forth in the current LDraw File Format specification) for a model to be included in the OMR

Base Requirements:
------------------
All files in the model will conform to the current LDraw File Format

Base File Naming:
-----------------
Each model in the OMR will consist of several files that are packaged together into a single MPD file. For sets that include instructions for multiple models, each model will have its own MPD file. Each MPD for the set will be named in the following manner:

<Set Number>( <Optional Specifier> )-[main or alt<Number>]

Where:
<Set Number>: the number assigned on the container of the set
<Optional Specifier>: Sometimes different sets with the same number are released, the specifier will be a single digit number, in parentheses, that is different between different sets, to distinguish these sets from one another.
[main or alt<Number>]: The main model of the instructions (i.e. the model featured on the cover of the container) will have the word "main". For sets that feature more than one model on the front of the container (e.g. the Creator line), the largest or most prominent model is the main model. For alternate models that are detailed in instructions, the word "alt" and a single digit number starting at 1 will be used. For playsets or other sets where there are multiple models that are part of an integral whole, all of the submodels will be contained in the main model MPD.

Example:
Set 4896 - Roaring Roadsters. This creator set has 3 models in the instructions. The roadster is featured prominently on the box. 4896 is the only set with that number. Therefore:
Roadster MPD: 4896-main.mpd
Dragster MPD: 4896-alt1.mpd
etc...

MPD File Structure:
-------------------
The MPD will conform to the MPD File Specification.

The naming of the individual files in the MPD wis up to the discretion of the author with the following guidance:
- A logical nameing scheme is highly desired.
- Individual models in the set (e.g a vehicle or minifig) shall have thier own separate file inside the MPD.
- Minifig file name should have the name of the character, if known
- The <MPD Filename> is reqired to be prepended to the file name of each indiviual file in the MPD

The unofficial parts are allowed to be used. The filename of the unoffical part is subject to the naming rulles above (e.g. 33056.dat would be renamed to <MPD Filename> - 33956.dat). It is highly encouraged that any parts created for use in a OMR file be submitted to the LDraw.org Parts Tracker.

If a part is unavailable both officially or on the LDraw.org Parts Tracker. a suitible substitution may be made. If the unavailable part is a patterned part with an unpatterned version available use the unpatterned version. A comment should be inserted stating that a subtitution has been made or, if no substitution is available/suitable, that a piece has been omitted. Reference the step and page number of the instructions if possible.

Example:
0 // The next peice should have the Star Wars Hatch pattern per step X on page Y
or
0 // Bionicle piece X should ge here per step Y on page Z

File Headers:
-------------
Each individual model file in the MPD must have a standard header format.

Standard Header:
0 FILE <MPD Filename> - <Filename>.ldr
0 <MPD Filename> - <File Desciption>
0 Name: <MPD Filename> - <Filename>.ldr
0 Author: <Author Name>
0 !LDRAW_ORG Official Model Repository
0 !LICENSE Redistributable under CCAL version 3.0 : see CAreadme.txt

0 !THEME Theme name
0 !KEYWORDS words, more words,…,
0 !KEYWORDS words in second row, …, final words

0 !HISTORY YYYY-MM-DD [<Author Name>] Free text description of change. This can wrap to a
0 !HISTORY YYYY-MM-DD [<Author Name>e] second row with the same date if necessary. However authors should lean toward writing longer
0 !HISTORY YYYY-MM-DD [<Author Name>e] single !HISTORY lines(and not feel constrained to the historic 80-character limit on line length)

Where:
<MPD Filename>: The name of the containing MPD
<Filename>: The name of the file
<Author Name>: The name of the author. Real full name are highly desired but not required. If the full name is not provided, a first or last name, with or with out initials, is requested.

Optional commands are !THEME, !KEYWORDS, and !HISTORY

Example:
To Be Inserted Later

META commands:
--------------
All META commands are allowed in the model file but not specifically required except as specified for the header. If included, any META commands used should enable any instructions generated to be as close to the official instructions as possible.

This topic for Publishing here tutorials for Pov-Ray rendering.
Koyan Tutorial - This is old tutorial may be useful for people, who begin to teach pov-ray.
But there is few problems.
This tutorial is made for L3p 1,3 if you use 1,4 you have manually copy colors definitions from files.
Also we can here share lightprobes and other.

how to make the pieces connect like in LDD?

Is it just my? All posts are threaded at:

http://forums.ldraw.org/list.php?19

but the sticky posts at the top aren't.

w.

Orion Pobursky Wrote:
-------------------------------------------------------
> Interesting. I'd go with 0 !FILE_TYPE. This may clear up a few issue but,
> as we saw with ldconfig.ldr, a new meta depends on support for the
> program authors.

The more I think of it, the better I like 0 !LDRAW.
For example:
0 !LDRAW Unofficial Moonbase Module Model
where "!LDRAW" and "Model" are mainly interesting for the programs, (but yet somewhat interesting for the human user)
and where "Unofficial Moonbase Module" is interesting for the user. (but could maybe also be of interest for a sorting/categorizing software???)

Why "0 !LDRAW"?
* It's good to have the information that it's a file in LDraw format, even for files that aren't directly affliated with ldraw.org. Or else, many private files without "0 LDRAW_ORG" will not even have LDraw mentioned anywhere.
* It's shorter than most of the other metas suggested. Keep in mind that this will probably be typed by hand by the user in most cases.
* !LDRAW_ORG is already used for similar information on file type and more. I believe a similar name for similar information could make sense.

/Tore

Hi all,

I kinda sparked a discussion about how to determine if a file is a part or not in

http://forums.ldraw.org/showthread.php?tid=503,503

Resulting of that I think there is a need for a way of indicating the goal of a document similar to the !LDRAW_ORG meta, but for private or 3rd party documents instead. This meta can then be used by software to do goal depended preparations.

Maybe something like:

0 !NATURE < model | part | shortcut | alias >

or

0 !HINT [ docNature=<model | part | shortcut | alias> ]

The second one is more advanced / generic and opens the door to adding more stuff in the future.

I know the first one has overlap with !LDRAW_ORG but like tore said in the above mentioned thread, it suggests 'ldraw.org owns this' which isn't very friendly if it's your own private creation.

It's also possible to get the information from keywords and or comment lines in the header, but that isn't fool proof parsing wise imho.

What do you think?

Hi folks,

in sync with "Section 6.08: Appointed Key Positions" of the LDraw Bylaws the LDraw Steering Committee has appointed Scott Wardlaw as LDraw Colormaster.

Scott has maintained the LDraw color file LDConfig.ldr since 2009 and will be from now on officially responsible for corrections and additions.

Congratulations!

Willy Tschager
On behalf of the LDraw SteerCo

Hi all, I've been playing around with datsville.

But somehow I thought it was bigger, I'm using the version from datsville.googlecode.com.

Anyone has a newer / bigger version?

Also why is everything stuffed in a gigantic MPD (33000 lines!) Not very efficient for use in svn.

Here's the latest draft. Discuss!! (Note: there is a quote bug that's removing the text between <>. Be aware of that and restore the text if needed)
--
The Offical Model Repository Specification
Version: 0.2 (will turn 1.0.0 upon ratification by the LSC)
Author: Orion Pobursky

Purpose:
--------
The Official Model Repository (OMR) is a database of file in the LDraw File Format describing models that are released as sets by Lego®. For consistency between models and ease of indexing by software, a standard for the file headers, names, and hierarchy in the OMR is needed. This document will outline the extra requirements (in addition to those set forth in the current LDraw File Format specification) for a model to be included in the OMR

Base Requirements:
------------------
All files in the model will conform to the current LDraw File Format

Base File Naming:
-----------------
Each model in the OMR will consist of several files that are packaged together into a single MPD file. For sets that include instructions for multiple models, each model will have its own MPD file. Each MPD for the set will be named in the following manner:

<Set Number>( <Optional Specifier> )-[main or alt<Number>]

Where:
<Set Number>: the number assigned on the container of the set
<Optional Specifier>: Sometimes different sets with the same number are released, the specifier will be a single digit number, in parentheses, that is different between different sets, to distinguish these sets from one another.
[main or alt<Number>]: The main model of the instructions (i.e. the model featured on the cover of the container) will have the word "main". For sets that feature more than one model on the front of the container (e.g. the Creator line), the largest or most prominent model is the main model. For alternate models that are detailed in instructions, the word "alt" and a single digit number starting at 1 will be used. For playsets or other sets where there are multiple models that are part of an integral whole, all of the submodels will be contained in the main model MPD.

Example:
Set 4896 - Roaring Roadsters. This creator set has 3 models in the instructions. The roadster is featured prominently on the box. 4896 is the only set with that number. Therefore:
Roadster MPD: 4896-main.mpd
Dragster MPD: 4896-alt1.mpd
etc...

MPD File Structure:
-------------------
The MPD will conform to the MPD File Specification.

The naming of the individual files in the MPD is up to the discretion of the author with the following guidance:
- A logical naming scheme is highly desired.
- Individual models in the set (e.g a vehicle or minifig) shall have their own separate file inside the MPD.
- Minifig file name should have the name of the character, if known
- The <MPD Filename> is required to be prepended to the file name of each individual file in the MPD

The only unofficial parts allowed to be referenced in the model files are those currently residing on the LDraw.org Parts Tracker. No part files shall be contained in the MPD.

File Headers:
-------------
Each individual model file in the MPD must have a standard header format.

Standard Header:
0 FILE <MPD Filename> - <Filename>.ldr
0 <MPD Filename> - <File Desciption>
0 Name: <MPD Filename> - <Filename>.ldr
0 Author: <Author Name>
0 !LDRAW_ORG Official Model Repository
0 !LICENSE Redistributable under CCAL version 2.0 : see CAreadme.txt

0 !THEME Theme name
0 !KEYWORDS words, more words,…,
0 !KEYWORDS words in second row, …, final words

0 !HISTORY YYYY-MM-DD [<Author Name>] Free text description of change. This can wrap to a
0 !HISTORY YYYY-MM-DD [<Author Name>e] second row with the same date if necessary. However authors should lean toward writing longer
0 !HISTORY YYYY-MM-DD [<Author Name>e] single !HISTORY lines(and not feel constrained to the historic 80-character limit on line length)

Where:
<MPD Filename>: The name of the containing MPD
<Filename>: The name of the file
<Author Name>: The name of the author. Real full name are highly desired but not required. If the full name is not provided, a first or last name, with or with out initials, is requested.

Optional commands are !THEME, !KEYWORDS, and !HISTORY

META commands:
--------------
The only META commands allowed in the model file are those associated with the header, 0 FILE (for MPD support) and 0 STEP. STEP commands not specifically required but they are highly desired. If included, the step commands should follow the instructions as closely as possible.

http://forums.ldraw.org/showthread.php?t...493#pid493

As Tore points out the failure of the forum to include parts in '<>' while quoting a post isn't too good. Anyone else noticed similar behaviour with other terms?

Tim