attachment

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>CIM> CIM Core discussion about MappingString format</TITLE> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> <META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD> <BODY> <DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN class=310594818-27032006>Huh?  I'm puzzled.  </SPAN></FONT></DIV> <DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN class=310594818-27032006></SPAN></FONT> </DIV> <DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN class=310594818-27032006>- The "Section 4" example in your email was entirely correct, and they will agree as soon as we send them a couple words of context.</SPAN></FONT></DIV> <DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN class=310594818-27032006></SPAN></FONT> </DIV> <DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN class=310594818-27032006>- MIB references in MappingStrings are explicitly different.  The examples in the CIM Infrastructure Spec and dozens of MOFs use exactly the syntax you want, also, that is</SPAN></FONT></DIV> <DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN class=310594818-27032006>    MIB.IETF|Printer-MIB.prtCurrentLocalization</SPAN></FONT></DIV> <DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN class=310594818-27032006></SPAN></FONT> </DIV> <DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN class=310594818-27032006>- MIFs also have a special format.  Fortunately we don't have to deal with any of those.  (Harry rescued printers from MIFness many years ago, thank you Harry.)  </SPAN></FONT></DIV> <DIV><FONT face=Arial color=#0000ff></FONT> </DIV> <DIV><FONT face=Arial color=#0000ff><SPAN class=310594818-27032006>After reading the actual so-called rules on this topic, in the CIM Infrastructure Spec (DSP0004), sections 2.5.5 and 2.5.6, I was very confused.  However, after looking at many dozens of citations in the existing MOFs, I find that there is much consistency.  And the formats you proposed match nicely.  </SPAN></FONT></DIV> <DIV><FONT face=Arial color=#0000ff><SPAN class=310594818-27032006></SPAN></FONT> </DIV> <DIV><FONT face=Arial color=#0000ff><SPAN class=310594818-27032006>Let's declare victory and move on.  </SPAN></FONT></DIV> <DIV><FONT face=Arial color=#0000ff></FONT> </DIV> <DIV><SPAN class=310594818-27032006><FONT face=Arial color=#0000ff>rick</FONT></SPAN></DIV> <DIV><BR></DIV> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left> <HR tabIndex=-1> <FONT face=Tahoma><B>From:</B> McDonald, Ira [mailto:imcdonald@sharplabs.com] <BR><B>Sent:</B> Friday, March 24, 2006 16:15<BR><B>To:</B> Landau, Richard; wims@pwg.org<BR><B>Cc:</B> Bumpus, Winston<BR><B>Subject:</B> RE: WIMS> CIM> CIM Core discussion about MappingString format<BR></FONT><BR></DIV> <DIV></DIV> <DIV><SPAN class=284321022-24032006><FONT face=Arial color=#0000ff>Hi Rick</FONT></SPAN></DIV> <DIV><SPAN class=284321022-24032006><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV><SPAN class=284321022-24032006><FONT face=Arial color=#0000ff>They're all wet - they don't know their own IETF MIB reference syntax!</FONT></SPAN></DIV> <DIV><SPAN class=284321022-24032006><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV><SPAN class=284321022-24032006><FONT face=Arial color=#0000ff>Quoting verbatim from CIMv2.11 'CIM_BGPProtocolEndpoint.mof':</FONT></SPAN></DIV> <DIV><SPAN class=284321022-24032006><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV><SPAN class=284321022-24032006><FONT face=Arial color=#0000ff>  MappingStrings { "MIB.IETF|BGP4-MIB.bgpConnectRetryInterval" }]</FONT></SPAN></DIV> <DIV><SPAN class=284321022-24032006><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV><SPAN class=284321022-24032006><FONT face=Arial color=#0000ff>Note, none of this pseudo-pipe syntax - THOUSANDS of examples</FONT></SPAN></DIV> <DIV><SPAN class=284321022-24032006><FONT face=Arial color=#0000ff>in the above syntax in CIMv2.11.  These guys should read their</FONT></SPAN></DIV> <DIV><SPAN class=284321022-24032006><FONT face=Arial color=#0000ff>own stuff.</FONT></SPAN></DIV> <DIV><SPAN class=284321022-24032006><FONT face=Arial color=#0000ff></FONT></SPAN> </DIV> <DIV><SPAN class=284321022-24032006><FONT face=Arial color=#0000ff>Cheers,</FONT></SPAN></DIV> <DIV><SPAN class=284321022-24032006><FONT face=Arial color=#0000ff>- Ira</FONT></SPAN></DIV> <DIV> </DIV> <P>Ira McDonald (Musician / Software Architect)<BR>Blue Roof Music / High North Inc<BR>PO Box 221  Grand Marais, MI  49839<BR>phone: +1-906-494-2434<BR>email: imcdonald@sharplabs.com </P> <BLOCKQUOTE dir=ltr style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma>-----Original Message-----<BR><B>From:</B> owner-wims@pwg.org [mailto:owner-wims@pwg.org]<B>On Behalf Of </B>Richard_Landau@Dell.com<BR><B>Sent:</B> Friday, March 24, 2006 3:57 PM<BR><B>To:</B> wims@pwg.org<BR><B>Cc:</B> Winston_Bumpus@Dell.com<BR><B>Subject:</B> WIMS> CIM> CIM Core discussion about MappingString format<BR><BR></FONT></DIV> <P><FONT face=Arial>Went well.  Not perfectly, which is my fault but easily fixed.  Discussion points:</FONT> </P> <P><FONT face=Arial>- MIB.PWG okay.  </FONT></P> <P><FONT face=Arial>- Hyphen instead of dot okay.  The only reasonable alternative is %2E or some such, which is much more hostile to humans.  </FONT></P> <P><FONT face=Arial>- "Section 4" was questioned.  I, unfortunately, could not get the doc (PWG5101.1) open in time to look at the section, and I didn't remember it.  The group's statement was If there is a table or data structure containing a property, one should use pipe syntax, e.g., </FONT></P> <P><FONT face=Arial>    doc.authority | structurename | propertyname.  </FONT><BR><FONT face=Arial>See examples in the new association CIM_SCSIInitiatorTargetLogicalUnitPath, which is, horrors, a three-way association, but includes several examples of this syntax, e.g., </FONT></P> <P><FONT face=Arial>    MP_API.SNIA|MP_PATH_LOGICAL_UNIT_PROPERTIES|deviceFileName </FONT></P> <P><FONT face=Arial>HOWEVER, that doesn't apply to the PWG5101.1 "Section 4 Media Color Names" case, anyway.  As I read it, Section 4 is a textual convention, one of three in the doc, which might be specified as a syntactic restriction on any number of properties in other specifications.  There is no property name within a structure to be cited.  I assume that the same reasoning would apply to any other textual convention if there were no other formal syntax to apply.  The IANA textual conventions that we cite do have a reasonable structure because they are defined in MIBs, so that case is not comparable.  Conclusion: no problem.  </FONT></P> <P><FONT face=Arial>I closed off the debate by saying that we would take a look at it and send a revised email with context so that they could understand the "Section 4" case, however we resolved it.  We should send a very simple revised message (again to wg-cimcore), with wording about textual conventions but not in formal MIB or other syntax, and maybe an extract of Section 4 from the document, declare victory, and move on.  Ira, can you make the slight additions?</FONT></P> <P><FONT face=Arial>Also, a nit, I found a minor typo in PWG5101.1 when I was looking at our friend Section 4: the first para ends with "...as defined in Table ."  It should say "Table 1."</FONT></P> <P><FONT face=Arial>Have a good weekend, all.</FONT> </P> <P><FONT face=Arial>rick</FONT> </P> <P><FONT face=Arial>----------------------</FONT> <BR><FONT face=Arial>Richard_Landau(at)dell(dot)com, Stds & System Mgt Arch, CTO Office</FONT> <BR><FONT face=Arial>+1-512-728-9023, One Dell Way, RR5-3 MS 8509, Round Rock, TX 78682</FONT> </P><BR> <P>--<BR>No virus found in this incoming message.<BR>Checked by AVG Free Edition.<BR>Version: 7.1.385 / Virus Database: 268.3.1/291 - Release Date: 3/24/2006<BR></P></BLOCKQUOTE><BR> <P>--<BR>No virus found in this outgoing message.<BR>Checked by AVG Free Edition.<BR>Version: 7.1.385 / Virus Database: 268.3.1/291 - Release Date: 3/24/2006<BR></P></BODY></HTML>