X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Injected-Via-Gmane: http://gmane.org/ To: geda-user AT delorie DOT com From: Kai-Martin Knaak Subject: Re: [geda-user] Data Sheets Date: Wed, 16 Jan 2013 21:13:29 +0100 Organization: Institut =?UTF-8?B?ZsO8cg==?= Quantenoptik Lines: 23 Message-ID: References: <87wqvhd4tw DOT fsf AT gmail DOT com> <20130115013756 DOT 9917 DOT qmail AT stuge DOT se> <50F4E4D1 DOT 3010802 AT ecosensory DOT com> <878v7uv4gl DOT fsf AT gmail DOT com> <50F58A89 DOT 1040004 AT ecosensory DOT com> <20130115172850 DOT GA5543 AT recycle DOT lbl DOT gov> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet AT ger DOT gmane DOT org X-Gmane-NNTP-Posting-Host: bibo.iqo.uni-hannover.de User-Agent: KNode/4.4.11 Reply-To: geda-user AT delorie DOT com Larry Doolittle wrote: > I recommend only storing meta-information about the datasheets: > upstream URL, Unfortunately, companies tend to change their datasheet repo every other year. Worse, some designs get transferred to other companies, the whole company seizes to exist, or it gets ingested by some bigger fish. A few months later all links become moot. E.g., this happened to all datasheets by national due to the acquisition by Texas Instruments. Since there is interlectual property involved, I see only these options: a) store the data sheet locally and keep the repo private. b) only store the name of the product. Include the essential numbers and data as rewritten text in the doc of the project. c) store a link to the search engine of a third party datasheet archive. At least in the last ten years, datasheet search engines were a much more stable source of information than any manufacturer. ---<)kaimartin(>---