Hi,
PWG format for CIM MOF references was not processed at today's
DMTF CIM Core concall, apparently, but John Crandal says below
that he will "get back by Monday".
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald at sharplabs.com
-----Original Message-----
From: John Crandall [mailto:jcrandal at Brocade.COM]
Sent: Friday, February 03, 2006 12:35 PM
To: McDonald, Ira
Cc: wims at pwg.org; wg-cimcore at dmtf.org
Subject: RE: Proposed format for PWG mapping strings in CIM MOFs
Sorry I did not see this. I will check the spec and get back by Monday.
John
-----Original Message-----
From: McDonald, Ira [mailto:imcdonald at sharplabs.com]
Sent: Monday, January 23, 2006 12:31 PM
To: John Crandall; McDonald, Ira
Cc: 'wims at pwg.org'; 'wg-cimcore at dmtf.org'
Subject: Proposed format for PWG mapping strings in CIM MOFs
Hi John,
Some background. The PWG is a member organization of
the IEEE-ISTO. The PWG standards-track has only two
levels, Candidate Standard and Standard. All current
PWG standards-track documents are at the first level.
Each PWG standards-track document is assigned a
permanent document number when it reaches Candidate
Standard level, of the form "PWG 51xy.z", e.g., PWG
5105.1 is the PWG Semantic Model. Note that _dot_
infixed in the document number.
I suggest the following ABNF for PWG mapping strings
(using productions from RFC 4234 'ABNF'):
pwg-ms = DQUOTE pwg-num "." "PWG" "|" pwg-text DQUOTE
pwg-num = "PWG" "51" 2digit "-" 1*digit
pwg-text = *(SP / VCHAR)
For example, using this format:
MappingStrings { "PWG5101-1.PWG|Section 4 Media Color Names" }
The pesky infixed dot has been converted to a hyphen.
Comments?
Cheers,
- Ira (editor of PWG CIM refresh white paper)
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald at sharplabs.com