Why do we need working resource ids ?

From: Edgar@EdgarSchwarz.de
Date: Mon, May 22 2000

  • Next message: Tim Ellison/OTT/OTI: "Re: Section 5"

    From: Edgar@EdgarSchwarz.de
    Date: Tue, 23 May 2000 00:04:11 +0200
    Message-Id: <200005222204.AAA22310@msheas02.msh.de>
    To: ietf-dav-versioning@w3.org
    Cc: Edgar@EdgarSchwarz.de
    Subject: Why do we need working resource ids ?
    
    Hello,
    a CHECKOUT returns a working resource id. Wouldn't it be possible
    to drop that ?
    Normally a CHECKOUT works in the context of a workspace (explicit
    or implicit). So I expect a server to give me the working resource
    if I later GET and specify versioned resource and workspace.
    
    BTW, the introduction to workspaces in 7.1 is too technical IMHO.
    It should describe what we want to achieve with it. E.g. that it
    is a filter or view which can help authors to coordinate their work.
    Also I think a workspace server shouldn't define a 'request workspace',
    but a 'user workspace' if no workspace header is given for a request.
    
    Cheers, Edgar
    
    
    
    -- 
    edgar@edgarschwarz.de                    http://www.edgarschwarz.de
    *          DOSenfreie Zone.        Running Native Oberon.         *
    Make it as simple as possible, but not simpler.     Albert Einstein