kicad-developers team mailing list archive

[Vesa Solonen <vesa.solonen@xxxxxxxx>]

08/06/15, 16:06, Chris Pavlina kirjoitti:
> Also keep in mind that the standard is pay-to-access. That's not fit for 
> an open-source project. I rather suspect it would be frowned upon if we 
> were to buy a copy and then put it into the documentation for all to 
> access - and if we don't, how can we follow it?
> 
> Forget the damn standard. Make our own, if need be.
> 
> On Mon, Jun 08, 2015 at 08:58:50AM -0400, Wayne Stambaugh wrote:
>> Let's not get too hung up on EN60617-3.  I really don't care if KiCad is
>> compliant to some standard other than exporting to third party file
>> formats.  What I do care about is the user experience.  If the goal is
>> to make it obvious to the user (IMO a good thing) that a schematic
>> connection is or is not made, then I would rather do what makes the best
>> user experience rather than follow some standard generated by government
>> body and/or committee.
>>
>> On 6/8/2015 8:25 AM, Chris Pavlina wrote:
>>> 60617-3 allows a dotless junction (as in 03-02-06), but the same 
>>> connection can be represented with two 03-02-05; it is not a violation of 
>>> the standard to always use dots.

I generally agree with both of you, but if Kicad wants to be a serious
tool for documentation it has to support EN60617 pretty well.

No company can use it for official documentation and certainly some one
guy design offices will lose bids if they can not fullfill customer
requirement of EN60617 compliant schematics...

It certainly will be frowned upon if we copied the standard, but making
a component library or software functionality according to one is
certainly not copying, but implementing the standard.

I havent read the fine print regarding implementation fee, but somehow I
suspect every screw made to DIN913 has to pay either.

-Vesa