X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=eyQbpYBcUnmf9g7WWJhZU6Yu4goWAm+1aQjAtJFDGrA=; b=ytoeeYjPBZIkyxeNu+QJGNLn9yhpKkf+E//l0EtZqmj9MsKxivlqrlVaZTnWrHMVOm hvTgSfxn09qTjzDeGa2TPNXVcWIvrFj0avro12tdXm0BGhfNdAc1K+DbltPguXsaktbi LCV+ud0av1I0enDc5uvHJhX3b/Lcsp9EKpmtmoKKYFuVdoj2Jc/IXtJgMtbtvZMD3Ch3 c0HlUUbSyvhrffDgM/IdoDIeTBzZkbhn/bbnrrObvV2Av14gWqjrHlX+TVJsPbaX9Knf j7Y9/S7+o/PaOW8YPpn6J18j3IeE1SALMco/Uml9Kx3f9zs/e/KU0yMHrW7SkKx46yxo +7Tg== X-Received: by 10.28.146.18 with SMTP id u18mr22300829wmd.72.1450738069524; Mon, 21 Dec 2015 14:47:49 -0800 (PST) Date: Mon, 21 Dec 2015 23:47:44 +0100 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] Proposing a New Hierarchical Data Structure? Message-Id: <20151221234744.458a2113f928cc0e85cf998b@gmail.com> In-Reply-To: References: <20151221030451 DOT 02399163eb3e40f21c622c41 AT gmail DOT com> <20151221203331 DOT 20837 DOT qmail AT stuge DOT se> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Mon, 21 Dec 2015 22:21:41 +0000 "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" wrote: > Unless anyone can present decent augments as to why its approach is > fundamentally different, or flawed, I think it would be silly to ignore > (whilst trying to replicate) the _MANY_ man years of design effort captured > in STEP AP210 and related standards. > > Ultimately, the complexity and size of that data model is because it aims > to capture an entire design life cycle, taking into account all the nuances > and aspects of an incredibly wide scope and representing it in a way that > has a defined semantic interpretation. This is useful, reusable, > transferable data which in many ways stands alone from the tools > manipulating it. I still believe the concept to start thin with a simple sketch and add more information over time is a good approach. If this is possible with AP210 I do not know.