Ah, now I understand. I still think it would be good if we could use
public links to the drafts going forward so I stick by my comment that
we should point this out to the full TC and ask that they use the proper
link format.
On the CD2 point specifically, I think that the current CD2 link is
tagged as "candidate" so I didn't want to use that one. I though our TC
administrator was going to put the CD at the proper location which was
why there isn't a just CD02 link in Kavi other than the candidate link.
So that was the link I was waiting for. I guess I know what it's going
to be so I could do an optimistic update.
Marc Goodner
Technical Diplomat
Microsoft Corporation
Tel: (425) 703-1903
Blog: http://spaces.msn.com/mrgoodner/
-----Original Message-----
From: Anish Karmarkar [mailto:]
Sent: Monday, February 20, 2006 4:50 PM
To: Marc Goodner
Cc: Doug Davis; ; Patil, Sanjay; Paul
Fremantle
Subject: Re: [ws-rx-editors] next CD? (or how to translate a member-only
doc URL to a public doc URL)
Marc,
I did not mean to imply that you (or anyone) should scrub the current
issues list of member-only links. I thought you were waiting for the CD
2 draft to be public and I was merely point out (and sharing my
experience with KAVI public/member-only URL behavior) that it already
was public, given the weirdness of KAVI.
-Anish
--
Marc Goodner wrote:
> Anish,
>
> I have been using the public urls for the mail links for a long time.
It
> is rare I mess that up anymore. The doc ones, honestly I use whatever
> I'm given.
>
> Can the chair this week please ask the TC to use the public links when
> referring to TC docs from now on to help in this? It would be good to
> capture Anish's notes below on this in the minutes to aid the members
in
> following through with this.
>
> I'm not going to go through the issue list and scrub out member only
> links, there just isn't any return on the investment of that time. If
> someone else wants to, have at it. Just let me know when you are going
> to do it so we don't step on each other's edits.
>
> I'm editing the issue list right now. I expect it will get updated
> today.
>
> It would be much better if the staff would fix Kavi. I can't even
begin
> to comment on how stupid it is to have a protected link that is also
> public that just introduces problems rather than solving any. See the
> above and the TC Process document for more details on how asinine
Kavi's
> behavior in this regard is.
>
> Marc Goodner
> Technical Diplomat
> Microsoft Corporation
> Tel: (425) 703-1903
> Blog: http://spaces.msn.com/mrgoodner/
>
>
> -----Original Message-----
> From: Anish Karmarkar [mailto:]
> Sent: Monday, February 20, 2006 4:12 PM
> To: Marc Goodner
> Cc: Doug Davis; ; Patil, Sanjay;
Paul
> Fremantle
> Subject: Re: [ws-rx-editors] next CD? (or how to translate a
member-only
> doc URL to a public doc URL)
>
> Marc,
>
> I have noticed that like the email archive, every document in KAVI (at
> least in WSRX) has a member-only URL and a public URL.
>
> The member only URLs are typically:
>
http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/<some-nu
> meric-id>/<doc-name>
>
> The public URLs are typically:
>
http://www.oasis-open.org/committees/download.php/<some-numeric-id>/<doc
> -name>
>
> If you see a member-only URL for a doc you can translate the URL to a
> public URL be using the appropriate prefix (replace
> "apps/org/workgroup/ws-rx" with "committees" in the URL)
>
> For example the member-only CD2 URLs are:
>
http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/16271/ws
> rm-1.1-spec-cd-02.pdf
>
http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/16273/ws
> rmp-1.1-spec-cd-02.pdf
>
> The equivalent public URLs are:
>
http://www.oasis-open.org/committees/download.php/16271/wsrm-1.1-spec-cd
> -02.pdf
>
http://www.oasis-open.org/committees/download.php/16273/wsrmp-1.1-spec-c
> d-02.pdf
>
> In fact the only important thing is the <some-numeric-id> everything
> else is irrelevant.
>
> The URLs:
>
http://www.oasis-open.org/committees/download.php/16271/wsrm-1.1-spec-cd
> -02.pdf
>
http://www.oasis-open.org/committees/download.php/16271/complete-garbage
>
http://www.oasis-open.org/committees/download.php/16271/really-important
>
> all return the same document.
>
> Not sure if you are waiting for public URLs for updating the issues
> list, but thought I would mention. All of this doesn't help if things
> need to happen on http://docs.oasis-open.org.
>
> -Anish
> --
>
> Marc Goodner wrote:
>
>>Also, it isn't our fault (that I can tell) but it sure would be nice
>
> if
>
>>the CD2 could get posted before we get to CD3. How long have we been
>>waiting on an answer now on that? Are we going to get to PR before any
>
>
>>of our approved CDs get posted? Honestly I've been sitting on a bunch
>
> of
>
>>the "done" issues that need to be changed to "closed" so that I can
>
> add
>
>>a remark pointing to the CD2 doc that closes them. This is really
>>starting to hurt.
>>
>>
>>
>>Sanjay or Paul, have you guys heard anything yet?
>>
>>
>>
>>Marc Goodner
>>
>>Technical Diplomat
>>
>>Microsoft Corporation
>>
>>Tel: (425) 703-1903
>>
>>Blog: http://spaces.msn.com/mrgoodner/
>>
>>
>
>
------------------------------------------------------------------------
>
>>*From:* Marc Goodner [mailto:]
>>*Sent:* Monday, February 20, 2006 1:32 PM
>>*To:* Doug Davis;
>>*Subject:* RE: [ws-rx-editors] next CD?
>>
>>
>>
>>I have plans to review today, at least as a first pass. I expect I'll
>>get though a deeper review at the latest tomorrow afternoon.
>>
>>
>>
>>Was a CD3 candidate asked for by the TC? Seems premature if not, I
>>suggest bringing this up on Thursday's call and being ready to post it
>
>
>>afterwards. Not that I'm opposed, I'm actually inclined to think we
>>should do a CD before the F2F.
>>
>>
>>
>>Marc Goodner
>>
>>Technical Diplomat
>>
>>Microsoft Corporation
>>
>>Tel: (425) 703-1903
>>
>>Blog: http://spaces.msn.com/mrgoodner/
>>
>>
>
>
------------------------------------------------------------------------
>
>>*From:* Doug Davis [mailto:]
>>*Sent:* Monday, February 20, 2006 1:13 PM
>>*To:*
>>*Subject:* [ws-rx-editors] next CD?
>>
>>
>>
>>
>>All,
>> I just did a quick scan of the diffs between the last CD and the WDs
>
>
>>we have available. I found two minor typos in the core spec but
>
> nothing
>
>>serious enough to regen everything. Has anyone else looked at 'em
>>(aside from Anish) - I'd like to post 'em to the TC today as candidate
>
>
>>CD 3.
>>thanks
>>-Doug
>>
>
>
