Re: [xcbf] Ways forward

["jmessing" <jmessing@law-on-line.com>]

As a newcomer who may be called upon to contribute, may I get clarification of what occurred on the call, please? I had understood from the call after Phil disconnected that the following was agreed upon by consensus.

1. The XCBF spec will use Base64 encoding in preference to Hex. There were perceived technical advantages that were also recognized in another standards group which was moving to adopt the same or a similar change. Some members expressed having no preference either way, including Ed Day. All members who expressed an opinion agreed to Base64 encoding over Hex. No one championed using Hex in the XCBF spec.

2. A non-normative footnote will be added at an appropriate point in the standard explaining that the Base64 encoding was in anticipation (rather than deviation) of such changes in another, related standard.

3. John Larmouth will develop the text changes as editor.

4. I will be available for wordsmithing if others feel my input may be useful.

5. The XCBF spec will then move forward to Oasis without further delay once agreement on the textual changes was reached.

Did I miss or misunderstand something?

---------- Original Message ----------------------------------
From: "Ed Day" <eday@obj-sys.com>
Date:  Fri, 25 Apr 2003 10:48:34 -0400

>As mentioned on the phone conference, I would provide an E-mail indicating what I believe are acceptable ways forward on the current state of the XCBF document.  All of these are acceptable alternatives:
>
>1. Change the base64 encoding to hex to provide full compliance with XER as it stands today, 
>
>2. Indicate in the text that the encodings are XER compilant with minor deviations, namely the use of base64 in certain fields.  Indicate in an Appendix the current plans for the future XER standard with guidelines as to what is going to be provided so that implementors can plan to make changes to their products to be compilant with the new standard.  Only the part of the new XER standard that affects the XCBF standard needs to be disclosed.
>
>3. Delay the XCBF standard until the EXTENDED-XER standard is available and can be referenced.
>
>Regards, 
>
>Ed Day
>Objective Systems, Inc.
>REAL WORLD ASN.1 AND XML SOLUTIONS
>Tel: +1 (484) 875-9841 
>Fax: +1 (484) 875-9830 
>Toll-free: (877) 307-6855 (USA only)
>mailto:eday@obj-sys.com
>http://www.obj-sys.com
>
>
>
>