CAP-12-e: TRANSP has misleading ABNF comments
[email protected] Wed, 19 May 2004 10:50:12 -0400
| Newsgroups | gmane.ietf.calendar |
|---|---|
| Message-ID | <OFB547212B.AA3E3A23-ON85256E99.0050871C-85256E99.005140E9@notesdev.ibm.com> |
In looking up something I noticed what appears to be incorrect/misleading
text in Section 8.37 TRANSP Property. In particular the comments in the
ABNF:
transp = "TRANSP" other-params ":" transvalue CRLF
transvalue
= "OPAQUE" ;Blocks or opaque on busy time searches.
/ "TRANSPARENT" ;Transparent on busy time searches.
/ "TRANSPARENT-NOCONFLICT" ; Transparent on busy time
; searches and no other OPAQUE or OPAQUE-NOCONFLICT objects
; can overlap it.
/ "OPAQUE-NOCONFLICT" ; Opaque on busy time
; searches and no other OPAQUE or OPAQUE-NOCONFLICT objects
; can overlap it.
;
;Default value is OPAQUE
According to the comments for TRANSPARENT-NOCONFLICT and
OPAQUE-NOCONFLICT, it would allowable for an object with
TRANSPARENT-NOCONFLICT to overlap. Clearly this is not what we intended
to say. Especially given intention of the -NOCONFLICT bit no matter the
busytime opacity and the text of Section 4.2.1 Access Control and
NOCONFLICT:
The "TRANSP" property can take on values "TRANSPARENT-NOCONFLICT" and
"OPAQUE-NOCONFLICT" that prohibit other components from overlapping
it.
The fix (for Dougs edification) is simple, change relevant the ABNF to:
/ "TRANSPARENT-NOCONFLICT" ; Transparent on busy time
; searches and no other OPAQUE or OPAQUE-NOCONFLICT or
; TRANSPARENT-NOCONFLICT objects can overlap it.
/ "OPAQUE-NOCONFLICT" ; Opaque on busy time
; searches and no other OPAQUE or OPAQUE-NOCONFLICT or
; TRANSPARENT-NOCONFLICT objects can overlap it.
Bruce
===========================================================================
Bruce Kahn INet:
[email protected]
Messaging & Collaboration Phone: 978.399.6496
IBM Software Group FAX: and nothing but the FAX...
Standard disclaimers apply, even where prohibited by law...