I assure you that this is not the way it works;

Sorry, but this is a subject I know a little about so you'll excuse me if I don't take your word for this. Just because your local autoparts shop has made some attempt at deriving a table of cross-manufacturer equivalences, doesn't mean that they knew what they were doing when the did so. Having been burned (expensively) with just such a "Yeah! That'll do the job" assurance...I'm twice shy!

plugs with different operating parameters get a different part number.

Yes, within any given manufacturers range. But, as the presence of two or more 'equivalent' parts within a single manufacturers range testifies, the ranges can overlap. So, for example, you might have: 

Cylinder Temp: low----A--B-------C-------D-----------high
ManA
  plug1        ********** 
  plug2             **************
ManB
  plug1          *********************
  plug2                   *********************

[download]

For a vehicle requiring C, ManA.plug2 and ManB.plug2 are interchangable.

But using that equivalence to suggest fitting ManA.plug2s to a vehicle D, specified as taking ManB.plug2 could be costly.

This is why all the manufacturers ask for the application in order to recommend the plugs in their range.

You might want to read this, paying particular attention to the last paragraphs on pages 2 and 3.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^5: Organizing and presenting a cross-reference by BrowserUk
in thread Organizing and presenting a cross-reference by oko1

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.