[Extended for PWG MIB references, not supported in previous version]
Hi John Crandall, Thursday (9 March 2006)
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 the infixed _dot_ in
the document number.
Modelled on the existing format for mapping strings for IETF standards
and IETF MIBs, I propose the following ABNF for PWG mapping strings
(using productions from RFC 4234 'ABNF'):
pwg-ms = pwg-std / ; PWG Standard Reference
pwg-mib ; PWG MIB Reference
pwg-std = DQUOTE pwg-num "." "PWG" "|" pwg-text DQUOTE
pwg-num = "PWG" "51" 2digit "-" 1*digit
pwg-text = *(SP / VCHAR)
pwg-mib = DQUOTE "MIB.PWG" "|" pwg-mod "." pwg-obj DQUOTE
pwg-mod = 1*(VCHAR) ; MIB module name from BEGIN
pwg-obj = 1*(VCHAR) ; object name from OBJECT-TYPE
Examples using this format:
MappingStrings { "PWG5101-1.PWG|Section 4 Media Color Names" }
MappingStrings {
"MIB.PWG|PWG-IMAGING-COUNTER-MIB.icMonitorCompletedJobs" }
Note that 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