- From: Ian B. Jacobs <ij@w3.org>
- Date: Wed, 03 Jan 2007 19:07:21 +0000
- To: "Cruikshank, David W" <david.w.cruikshank@boeing.com>
- Cc: Lofton Henderson <lofton@rockynet.com>, Janet Daly <janet@w3.org>, W3C Comm Team <w3t-comm@w3.org>, WebCGM WG <public-webcgm-wg@w3.org>
- Message-Id: <1167851241.10297.76.camel@localhost>
On Wed, 2007-01-03 at 10:38 -0800, Cruikshank, David W wrote: > Ian, > > You wrote on Jan 2: > "Although it is not strictly required that we sync up the publication > and the press release, it is strongly preferred. I have a record of > Thierry Michel indicating (on 17 Nov) that the WG agreed to do the > publication of the Recommendation at the same time as the press release > (in January 2007). Our current plan, based on other work at W3C, is to > issue the Recommendation and press release on 30 January." > > While I'm sympathetic with the "strongly preferred" practice of having > the publication and press release coincide, I think the requirement of a > large user constinuency (ATA and ASD) should be enough to allow us to > work within the parameters of the process. > > I would propose we pick a date (20070130 is fine with me) and make sure > that the publication date is the same date. Hi David, I agree that we should aim for 30 January for the publication (and press release). Unforeseen circumstances aside, we should have no problem publishing on that date. _ Ian > Whether the press release > exactly coincides with that date is of little consequence to the users > who are relying on being able to reference WebCGM 2.0. > > As I said before I need to get references into both iSpec2200 and S1000D > as soon as possible and waiting until early February is not an option. > Both of these industry specification are passed the date where editing > changes are allowed, but I've been able to put in placeholders for > WebCGM 2.0. S1000D has two reference sections that are not hyperlinked > that reference W3C documents of the form REC-yyyymmdd-etc and one > hyperlinked reference to the actual specification to define the profile. > iSpec2200 has a single hyperlinked reference to WebCGM in the profile > definition. Both specification are subject to contractual terms, so > using "latest version" hyperlinks is not recommended. > > Let's see if we can't work something out on setting a publication date > that we can reference. > > Thx...Dave Cruikshank > > Technical Fellow - Graphics/Digital Data Interchange > Boeing Commercial Airplane > 206.544.3560, fax 206.662.3734 > david.w.cruikshank@boeing.com -- Ian Jacobs (ij@w3.org) http://www.w3.org/People/Jacobs Tel: +1 718 260-9447
Received on Wednesday, 3 January 2007 19:07:32 UTC