Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > sci.electronics.design > #453254
| From | Don Y <blockedofcourse@foo.invalid> |
|---|---|
| Newsgroups | sci.electronics.design |
| Subject | Re: big drives |
| Date | 2017-03-23 12:25 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <ob17ag$ars$1@dont-email.me> (permalink) |
| References | (4 earlier) <m536dcl3u2tkkrd6qv5mnu534bpim00uqb@4ax.com> <oav6et$5nr$1@dont-email.me> <slh6dctp51cj813bmi4lqrvlu8pqr7qqfo@4ax.com> <oavni1$6d0$1@dont-email.me> <ajp7dct3fku9ffums7nc03pulmhhguef0s@4ax.com> |
On 3/23/2017 8:27 AM, John Larkin wrote:
> On Wed, 22 Mar 2017 22:50:33 -0700, Don Y
> <blockedofcourse@foo.invalid> wrote:
>
>>> What happens when you email a file to someone else? Or put together a
>>> separate project folder, like to a contract manufacturer or a
>>> consultant? You can't include the database.
>>
>> Will that contract manufacturer be able to recognize your "augmented"
>> file system?
>
> It's not a special file system; it's properly documented files. If
> it's a readable file, open it and read. If it's not a human-readable
> format, open the README file in the same folder.
See below
>> That's why you include a MANIFEST file in any package of electronic objects.
>> There's no portable way to examine files of varying formats for "comments"
>> embedded within. How do you examine the revision, date, author, etc. of
>> a photograph? Of an AutoCAD 3D model? Of a DSO capture? etc.
>
> You'd send a manifest file to a CM or consultant? How do you generate
> that? What does it look like? How does it reference or name individual
> files?
>
> I recent sent design files to a CM, for a product that we license to
> another company. It's a ZIP file, and the first thing you see is a
> nice README.TXT file, with everything explained in direct English. I
> doubt that any automatic database app can write clear English.
A file called "MANIFEST" contains ASCII TEXT describing the contents of the
"document package" of which it is a part. It doesn't say anything about
how the package is to be used, etc. but, rather, just describes the
contents.
manifest, (noun):
+ a list of the cargo carried by a ship, made for the use of various
agents and officials at the ports of destination.
+ a list or invoice of goods transported by truck or train.
A "README" can have more varied uses and content. A MANIFEST only describes
the contents of the "document package":
32322.abc Schematic DASH-Strides 6 format
43243.lmn PCB layout in OrCAD Layout 9 format
55555.* Artwork in Gerber Photoplot layers
12345.xyz Bill of Material as ASCII text
94949.rrr Firmware image in binary form
60945.qqq Assembly instructions as ASCII text
etc.
[File naming conventions obviously vary so the recipient need not expect
a "foo.doc" file to be a MSWord file, etc.]
How *I* would generate it is by creating a report from the appropriate
fields associated with the file objects as named in the database.
E.g., if I was preparing a brochure, the MANIFEST might include:
abcdefg.raw Cover image, Adobe DNG format
434534.300 verso page imagery, JPEG2000 format
brochure.txt Instructions, ASCII text
contact.inf contact information, ASCII text
Back to sci.electronics.design | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-21 10:21 -0700
Re: big drives bitrex <bitrex@de.lete.earthlink.net> - 2017-03-21 13:47 -0400
Re: big drives George Herold <gherold@teachspin.com> - 2017-03-21 12:42 -0700
Re: big drives dagmargoodboat@yahoo.com - 2017-03-21 12:55 -0700
Re: big drives George Herold <gherold@teachspin.com> - 2017-03-21 13:37 -0700
Re: big drives bill.sloman@ieee.org - 2017-03-21 21:51 -0700
Re: big drives George Herold <gherold@teachspin.com> - 2017-03-22 07:26 -0700
Re: big drives Winfield Hill <hill@rowland.harvard.edu> - 2017-03-22 03:38 -0700
Re: big drives Don Kuenz <g@crcomp.net> - 2017-03-22 14:23 +0000
Re: big drives David Brown <david.brown@hesbynett.no> - 2017-03-22 16:43 +0100
Re: big drives Don Kuenz <g@crcomp.net> - 2017-03-22 18:35 +0000
Re: big drives David Brown <david.brown@hesbynett.no> - 2017-03-23 10:24 +0100
Re: big drives Don Kuenz <g@crcomp.net> - 2017-03-23 16:11 +0000
Re: big drives krw@notreal.com - 2017-03-23 13:05 -0400
Re: big drives Don Kuenz <g@crcomp.net> - 2017-03-23 17:39 +0000
Re: big drives krw@notreal.com - 2017-03-23 21:05 -0400
Re: big drives Don Kuenz <g@crcomp.net> - 2017-03-24 03:01 +0000
Re: big drives krw@notreal.com - 2017-03-23 23:09 -0400
Re: big drives Don Kuenz <g@crcomp.net> - 2017-03-24 04:15 +0000
Re: big drives krw@notreal.com - 2017-03-24 22:34 -0400
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-22 12:25 -0700
Re: big drives dplatt@coop.radagast.org (Dave Platt) - 2017-03-22 13:57 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-22 16:03 -0700
Re: big drives krw@notreal.com - 2017-03-22 20:29 -0400
Re: big drives tabbypurr@gmail.com - 2017-03-22 04:36 -0700
Re: big drives Spehro Pefhany <speffSNIP@interlogDOTyou.knowwhat> - 2017-03-22 08:57 -0400
Re: big drives Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2017-03-22 11:59 -0400
Re: big drives krw@notreal.com - 2017-03-22 13:23 -0400
Re: big drives Jon Elson <jmelson@wustl.edu> - 2017-03-22 16:38 -0500
Re: big drives krw@notreal.com - 2017-03-22 20:31 -0400
Re: big drives gray_wolf <g_wolf@nospam.com> - 2017-03-23 20:59 -0500
Re: big drives gray_wolf <g_wolf@nospam.com> - 2017-03-23 21:00 -0500
Re: big drives Robert Baer <robertbaer@localnet.com> - 2017-03-23 22:21 -0800
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-22 07:51 -0700
Re: big drives krw@notreal.com - 2017-03-22 13:23 -0400
Re: big drives Robert Baer <robertbaer@localnet.com> - 2017-03-23 22:19 -0800
Re: big drives tabbypurr@gmail.com - 2017-03-24 04:26 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-24 08:38 -0700
Re: big drives Jon Elson <jmelson@wustl.edu> - 2017-03-22 16:37 -0500
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-22 16:07 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-22 16:21 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-22 16:45 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-22 23:21 -0700
Re: big drives John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-03-24 13:06 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 16:56 -0700
Re: big drives John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-03-24 17:35 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 21:47 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-22 16:19 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-22 16:50 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-22 17:58 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-22 21:00 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-22 22:50 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-23 08:27 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-23 12:25 -0700
Re: big drives tabbypurr@gmail.com - 2017-03-24 04:31 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 06:38 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-24 08:41 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 11:38 -0700
Re: big drives John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-03-24 13:55 -0700
Re: big drives tabbypurr@gmail.com - 2017-03-24 17:14 -0700
Re: big drives John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-03-24 17:41 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 18:00 -0700
Re: big drives Joerg <news@analogconsultants.com> - 2017-03-23 09:35 -0700
Re: big drives "Michael A. Terrell" <mike.terrell@earthlink.net> - 2017-03-23 18:38 -0400
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-23 16:18 -0700
Re: big drives Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2017-03-23 18:29 -0400
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-23 18:38 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-23 18:54 -0700
Re: big drives pcdhobbs@gmail.com - 2017-03-23 19:16 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-23 19:28 -0700
Re: big drives pcdhobbs@gmail.com - 2017-03-23 19:55 -0700
Re: big drives krw@notreal.com - 2017-03-23 23:04 -0400
Re: big drives pcdhobbs@gmail.com - 2017-03-23 22:00 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-24 08:46 -0700
Re: big drives krw@notreal.com - 2017-03-24 22:38 -0400
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-23 22:22 -0700
Re: big drives pcdhobbs@gmail.com - 2017-03-23 23:08 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 00:21 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-24 09:00 -0700
Re: big drives David Brown <david.brown@hesbynett.no> - 2017-03-24 17:14 +0100
Re: big drives tabbypurr@gmail.com - 2017-03-24 09:19 -0700
Re: big drives David Brown <david.brown@hesbynett.no> - 2017-03-24 17:47 +0100
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 12:01 -0700
Re: big drives Jasen Betts <jasen@xnet.co.nz> - 2017-03-24 20:30 +0000
Re: big drives John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-03-24 14:06 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 11:55 -0700
Re: big drives "Michael A. Terrell" <mike.terrell@earthlink.net> - 2017-03-25 04:00 -0400
Re: big drives upsidedown@downunder.com - 2017-03-24 22:18 +0200
Re: big drives John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-03-24 14:15 -0700
Re: big drives Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2017-03-25 13:21 +0200
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-25 07:54 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-25 10:53 -0700
Re: big drives upsidedown@downunder.com - 2017-03-25 23:11 +0200
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-25 15:14 -0700
Re: big drives upsidedown@downunder.com - 2017-03-26 12:18 +0300
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-26 03:33 -0700
Re: big drives Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2017-03-26 16:36 -0400
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-26 14:13 -0700
Re: big drives Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2017-03-25 21:04 +0200
Re: big drives pcdhobbs@gmail.com - 2017-03-24 19:03 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-24 08:53 -0700
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 12:12 -0700
Re: big drives John Larkin <jjlarkinxyxy@highlandtechnology.com> - 2017-03-24 14:20 -0700
Re: big drives krw@notreal.com - 2017-03-24 22:43 -0400
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-24 20:10 -0700
Re: big drives krw@notreal.com - 2017-03-24 23:23 -0400
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-24 22:25 -0700
Re: big drives Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2017-03-25 13:23 +0200
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-23 19:36 -0700
Re: big drives upsidedown@downunder.com - 2017-03-24 10:14 +0200
Re: big drives Don Y <blockedofcourse@foo.invalid> - 2017-03-24 01:31 -0700
Re: big drives John Larkin <jjlarkin@highlandtechnology.com> - 2017-03-23 16:21 -0700
Re: big drives "Michael A. Terrell" <mike.terrell@earthlink.net> - 2017-03-24 08:54 -0400
csiph-web