As part of the Sad Face <https://www.thingiverse.com/thing:1350837/#comments> discussions, there is mention of watermarking your photos. I' like to talk about the equivalent for your mesh files. Export currently flags STL files with, "solid OpenSCAD_Model" AMF files with, " <metadata type="producer">OpenSCAD 2016.02.09 (git 9950e6a)</metadata>" I haven't checked the other formats. I did a check of some other STLs, and found (for B:inary & A:SCII) these in the wild: A:solid t231461 ak47 netfabb (repaired) B:binary stl file B:STL File created by netfabb - http://www.netfabb.com UNITS=MM A:solid Default B:MESHMIXER-STL-BINARY-FORMAT---------------------------------------------------- B:File exported by Artec Group 3D Scanning Solutions, www.artec-group.com B:Exported from Blender-2.74 (sub 0) B:solid Bag Handle v1-5 Slim B:COLOR= ...,MATERIAL=... ;SOLID While STL and AMF are ASCII there is no problem, they can be manually edited. However there has been discussion on introducing binary/compressed files which make that harder. I think some feature to add other meta-data to the export would be good. Binary STL seems to be the limiting factor, 80 character header. If we want to keep the OpenSCAD branding then we need to reserve some of that for OpenSCAD. Given the AMF string is ~30 chars, that could reserve the first 40 chars for branding, and allow user meta-data to use the last 40 chars. You could fit a copyright symbol, a short form CC tag and a bit.ly etc URL, or the like. Thoughts? ----- Admin - PM me if you need anything, or if I've done something stupid... Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above. The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out! -- View this message in context: http://forum.openscad.org/Ability-to-specify-contents-of-exported-header-tp16214.html Sent from the OpenSCAD mailing list archive at Nabble.com.

TLDR; I think that the metadata should be a set of name/value pairs, as that's what's most appropriate for the 7 file formats that we currently export. Most modern file formats support metadata in the form of name/value pairs, which means you aren't supposed to jam all the metadata into a single short string without any tagging of the components. Binary STL is an exception, but we don't support that yet, and there are significant technical problems with binary STL support that might delay it indefinitely, or place limitations on how well it works. Maybe binary STL will be the one format for which metadata isn't supported. Eg, PNG supports the Extensible Metadata Platform, which is a superset of the Dublin Core metadata, which has the tags Title, Creator, Subject, Description, Publisher, Contributor, Date, Type, Format, Identifier, Source, Language, Relation, Coverage and Rights. The AMF standard reserves a number of metadata types; the following are the ones relevant to us: * name - The alphanumeric label of the entity, to be used by the interpreter if interacting with the user. * description - A description of the content of the entity * url - A link to an external resource relating to the entity * author - Specifies the name(s) of the author(s) of the entity * company - Specifying the company generating the entity * cad - specifies the name of the originating CAD software and version * revision - specifies the revision of the entity * tolerance - specifies the desired manufacturing tolerance of the entity in entity’s unit system We should be using "cad" instead of "producer" for the OpenSCAD version. Different metadata types should be used for other information. The 3MF file format supports any of the metadata types in the Open Packaging Conventions/Core Properties. Same idea, a set of name/value pairs, but there's a longer list of standard types, including creation time, modification time, search keywords, thumbnail images. And so on. For old ascii formats like ascii STL and OFF, we can put name/value metadata pairs into comments, one pair per line. On 22 February 2016 at 23:46, MichaelAtOz <oz.at.michael@gmail.com> wrote: > As part of the Sad Face > <https://www.thingiverse.com/thing:1350837/#comments> discussions, there > is mention of watermarking your photos. > I' like to talk about the equivalent for your mesh files. > > Export currently flags > STL files with, "solid OpenSCAD_Model" > AMF files with, " <metadata type="producer">OpenSCAD 2016.02.09 (git > 9950e6a)</metadata>" > > I haven't checked the other formats. > > I did a check of some other STLs, and found (for B:inary & A:SCII) these in > the wild: > > A:solid t231461 ak47 netfabb (repaired) > B:binary stl file > B:STL File created by netfabb - http://www.netfabb.com UNITS=MM > A:solid Default > > B:MESHMIXER-STL-BINARY-FORMAT---------------------------------------------------- > B:File exported by Artec Group 3D Scanning Solutions, www.artec-group.com > B:Exported from Blender-2.74 (sub 0) > B:solid Bag Handle v1-5 Slim > B:COLOR= ...,MATERIAL=... ;SOLID > > While STL and AMF are ASCII there is no problem, they can be manually > edited. > However there has been discussion on introducing binary/compressed files > which make that harder. > > I think some feature to add other meta-data to the export would be good. > > Binary STL seems to be the limiting factor, 80 character header. If we want > to keep the OpenSCAD branding then we need to reserve some of that for > OpenSCAD. Given the AMF string is ~30 chars, that could reserve the first > 40 > chars for branding, and allow user meta-data to use the last 40 chars. > > You could fit a copyright symbol, a short form CC tag and a bit.ly etc > URL, > or the like. > > Thoughts? > > > > ----- > Admin - PM me if you need anything, or if I've done something stupid... > > Unless specifically shown otherwise above, my contribution is in the > Public Domain; to the extent possible under law, I have waived all > copyright and related or neighbouring rights to this work. Obviously > inclusion of works of previous authors is not included in the above. > > The TPP is no simple “trade agreement.” Fight it! > http://www.ourfairdeal.org/ time is running out! > -- > View this message in context: > http://forum.openscad.org/Ability-to-specify-contents-of-exported-header-tp16214.html > Sent from the OpenSCAD mailing list archive at Nabble.com. > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >

>and there are significant technical problems with binary STL support that might delay it indefinitely I think it is simply a matter of writing binary records instead of ASCII. The issue of keeping it manifold after truncating the values is common to ASCII floats and binary floats. I.e. if we simply change the output format we are no worse off than we are now with ASCII STLs. Possibly slightly better as it removes the conversion to string and back again that can change the value slightly unless it is done very carefully. >For old ascii formats like ascii STL and OFF, we can put name/value metadata pairs into comments, one pair per line. I don't think STL files have comment lines do they? On 23 February 2016 at 14:48, doug moen <doug@moens.org> wrote: > TLDR; I think that the metadata should be a set of name/value pairs, as > that's what's most appropriate for the 7 file formats that we currently > export. Most modern file formats support metadata in the form of name/value > pairs, which means you aren't supposed to jam all the metadata into a > single short string without any tagging of the components. > > Binary STL is an exception, but we don't support that yet, and there are > significant technical problems with binary STL support that might delay it > indefinitely, or place limitations on how well it works. Maybe binary STL > will be the one format for which metadata isn't supported. > > Eg, PNG supports the Extensible Metadata Platform, which is a superset of > the Dublin Core metadata, which has the tags Title, Creator, Subject, > Description, Publisher, Contributor, Date, Type, Format, Identifier, > Source, Language, Relation, Coverage and Rights. > > The AMF standard reserves a number of metadata types; the following are > the ones relevant to us: > > * name - The alphanumeric label of the entity, to be used by the > interpreter if interacting with the user. > > * description - A description of the content of the entity > > * url - A link to an external resource relating to the entity > > * author - Specifies the name(s) of the author(s) of the entity > > * company - Specifying the company generating the entity > > * cad - specifies the name of the originating CAD software and version > > * revision - specifies the revision of the entity > > * tolerance - specifies the desired manufacturing tolerance of the entity > in entity’s unit system > > We should be using "cad" instead of "producer" for the OpenSCAD version. > Different metadata types should be used for other information. > > The 3MF file format supports any of the metadata types in the Open > Packaging Conventions/Core Properties. Same idea, a set of name/value > pairs, but there's a longer list of standard types, including creation > time, modification time, search keywords, thumbnail images. > > And so on. For old ascii formats like ascii STL and OFF, we can put > name/value metadata pairs into comments, one pair per line. > > On 22 February 2016 at 23:46, MichaelAtOz <oz.at.michael@gmail.com> wrote: > >> As part of the Sad Face >> <https://www.thingiverse.com/thing:1350837/#comments> discussions, >> there >> is mention of watermarking your photos. >> I' like to talk about the equivalent for your mesh files. >> >> Export currently flags >> STL files with, "solid OpenSCAD_Model" >> AMF files with, " <metadata type="producer">OpenSCAD 2016.02.09 (git >> 9950e6a)</metadata>" >> >> I haven't checked the other formats. >> >> I did a check of some other STLs, and found (for B:inary & A:SCII) these >> in >> the wild: >> >> A:solid t231461 ak47 netfabb (repaired) >> B:binary stl file >> B:STL File created by netfabb - http://www.netfabb.com UNITS=MM >> A:solid Default >> >> B:MESHMIXER-STL-BINARY-FORMAT---------------------------------------------------- >> B:File exported by Artec Group 3D Scanning Solutions, www.artec-group.com >> B:Exported from Blender-2.74 (sub 0) >> B:solid Bag Handle v1-5 Slim >> B:COLOR= ...,MATERIAL=... ;SOLID >> >> While STL and AMF are ASCII there is no problem, they can be manually >> edited. >> However there has been discussion on introducing binary/compressed files >> which make that harder. >> >> I think some feature to add other meta-data to the export would be good. >> >> Binary STL seems to be the limiting factor, 80 character header. If we >> want >> to keep the OpenSCAD branding then we need to reserve some of that for >> OpenSCAD. Given the AMF string is ~30 chars, that could reserve the first >> 40 >> chars for branding, and allow user meta-data to use the last 40 chars. >> >> You could fit a copyright symbol, a short form CC tag and a bit.ly etc >> URL, >> or the like. >> >> Thoughts? >> >> >> >> ----- >> Admin - PM me if you need anything, or if I've done something stupid... >> >> Unless specifically shown otherwise above, my contribution is in the >> Public Domain; to the extent possible under law, I have waived all >> copyright and related or neighbouring rights to this work. Obviously >> inclusion of works of previous authors is not included in the above. >> >> The TPP is no simple “trade agreement.” Fight it! >> http://www.ourfairdeal.org/ time is running out! >> -- >> View this message in context: >> http://forum.openscad.org/Ability-to-specify-contents-of-exported-header-tp16214.html >> Sent from the OpenSCAD mailing list archive at Nabble.com. >> >> _______________________________________________ >> OpenSCAD mailing list >> Discuss@lists.openscad.org >> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >> > > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org > >

Oops you are correct. No comment lines in STL. Maybe could still use "solid tag1=val1; tag2=val2; ..." in ASCII stl. On Tuesday, 23 February 2016, nop head <nop.head@gmail.com> wrote: > >and there are significant technical problems with binary STL support that > might delay it indefinitely > > I think it is simply a matter of writing binary records instead of ASCII. > The issue of keeping it manifold after truncating the values is common to > ASCII floats and binary floats. I.e. if we simply change the output format > we are no worse off than we are now with ASCII STLs. Possibly slightly > better as it removes the conversion to string and back again that can > change the value slightly unless it is done very carefully. > > >For old ascii formats like ascii STL and OFF, we can put name/value > metadata pairs into comments, one pair per line. > > I don't think STL files have comment lines do they? > > > On 23 February 2016 at 14:48, doug moen <doug@moens.org > <javascript:_e(%7B%7D,'cvml','doug@moens.org');>> wrote: > >> TLDR; I think that the metadata should be a set of name/value pairs, as >> that's what's most appropriate for the 7 file formats that we currently >> export. Most modern file formats support metadata in the form of name/value >> pairs, which means you aren't supposed to jam all the metadata into a >> single short string without any tagging of the components. >> >> Binary STL is an exception, but we don't support that yet, and there are >> significant technical problems with binary STL support that might delay it >> indefinitely, or place limitations on how well it works. Maybe binary STL >> will be the one format for which metadata isn't supported. >> >> Eg, PNG supports the Extensible Metadata Platform, which is a superset of >> the Dublin Core metadata, which has the tags Title, Creator, Subject, >> Description, Publisher, Contributor, Date, Type, Format, Identifier, >> Source, Language, Relation, Coverage and Rights. >> >> The AMF standard reserves a number of metadata types; the following are >> the ones relevant to us: >> >> * name - The alphanumeric label of the entity, to be used by the >> interpreter if interacting with the user. >> >> * description - A description of the content of the entity >> >> * url - A link to an external resource relating to the entity >> >> * author - Specifies the name(s) of the author(s) of the entity >> >> * company - Specifying the company generating the entity >> >> * cad - specifies the name of the originating CAD software and version >> >> * revision - specifies the revision of the entity >> >> * tolerance - specifies the desired manufacturing tolerance of the entity >> in entity’s unit system >> >> We should be using "cad" instead of "producer" for the OpenSCAD version. >> Different metadata types should be used for other information. >> >> The 3MF file format supports any of the metadata types in the Open >> Packaging Conventions/Core Properties. Same idea, a set of name/value >> pairs, but there's a longer list of standard types, including creation >> time, modification time, search keywords, thumbnail images. >> >> And so on. For old ascii formats like ascii STL and OFF, we can put >> name/value metadata pairs into comments, one pair per line. >> >> On 22 February 2016 at 23:46, MichaelAtOz <oz.at.michael@gmail.com >> <javascript:_e(%7B%7D,'cvml','oz.at.michael@gmail.com');>> wrote: >> >>> As part of the Sad Face >>> <https://www.thingiverse.com/thing:1350837/#comments> discussions, >>> there >>> is mention of watermarking your photos. >>> I' like to talk about the equivalent for your mesh files. >>> >>> Export currently flags >>> STL files with, "solid OpenSCAD_Model" >>> AMF files with, " <metadata type="producer">OpenSCAD 2016.02.09 (git >>> 9950e6a)</metadata>" >>> >>> I haven't checked the other formats. >>> >>> I did a check of some other STLs, and found (for B:inary & A:SCII) these >>> in >>> the wild: >>> >>> A:solid t231461 ak47 netfabb (repaired) >>> B:binary stl file >>> B:STL File created by netfabb - http://www.netfabb.com UNITS=MM >>> A:solid Default >>> >>> B:MESHMIXER-STL-BINARY-FORMAT---------------------------------------------------- >>> B:File exported by Artec Group 3D Scanning Solutions, >>> www.artec-group.com >>> B:Exported from Blender-2.74 (sub 0) >>> B:solid Bag Handle v1-5 Slim >>> B:COLOR= ...,MATERIAL=... ;SOLID >>> >>> While STL and AMF are ASCII there is no problem, they can be manually >>> edited. >>> However there has been discussion on introducing binary/compressed files >>> which make that harder. >>> >>> I think some feature to add other meta-data to the export would be good. >>> >>> Binary STL seems to be the limiting factor, 80 character header. If we >>> want >>> to keep the OpenSCAD branding then we need to reserve some of that for >>> OpenSCAD. Given the AMF string is ~30 chars, that could reserve the >>> first 40 >>> chars for branding, and allow user meta-data to use the last 40 chars. >>> >>> You could fit a copyright symbol, a short form CC tag and a bit.ly etc >>> URL, >>> or the like. >>> >>> Thoughts? >>> >>> >>> >>> ----- >>> Admin - PM me if you need anything, or if I've done something stupid... >>> >>> Unless specifically shown otherwise above, my contribution is in the >>> Public Domain; to the extent possible under law, I have waived all >>> copyright and related or neighbouring rights to this work. Obviously >>> inclusion of works of previous authors is not included in the above. >>> >>> The TPP is no simple “trade agreement.” Fight it! >>> http://www.ourfairdeal.org/ time is running out! >>> -- >>> View this message in context: >>> http://forum.openscad.org/Ability-to-specify-contents-of-exported-header-tp16214.html >>> Sent from the OpenSCAD mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> OpenSCAD mailing list >>> Discuss@lists.openscad.org >>> <javascript:_e(%7B%7D,'cvml','Discuss@lists.openscad.org');> >>> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >>> >> >> >> _______________________________________________ >> OpenSCAD mailing list >> Discuss@lists.openscad.org >> <javascript:_e(%7B%7D,'cvml','Discuss@lists.openscad.org');> >> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >> >> >