OASIS Key Management Interoperability Protocol (KMIP) TC

Expand all | Collapse all

[Fwd: Re: [kmip] Clarification for document categories]

  • 1.  [Fwd: Re: [kmip] Clarification for document categories]

    Posted 05-14-2009 13:27
      |   view attached

    Attachment(s)

    vcf
    matthew_ball.vcf   330 B 1 version


  • 2.  Re: [Fwd: Re: [kmip] Clarification for document categories]

    Posted 05-14-2009 14:29
    On the topic of creating names folders for storing TC-related KMIP
    documents, here's a small consideration that may ease the burden
    of (perceived) need to get the design exactly right:
    
    The Kavi document repository system supports the use of folders
    that are visible to the TC members, but are not visible to users
    that access documents via the public interface [1].
    
    These Kavi folders are merely virtual - that is, they serve visually to
    separate documents into groups under a folder name, but the
    document URI itself does not reflect a current folder assignment.  This
    means you can move documents from one folder to another, or
    (accounting for other considerations), create new folders at any
    time and re-organize the documents in a new way.  Radical revision
    might have negative consequences for usability ("I can't see the
    document I'm looking for under FOO Folder any more!") -- but you
    can do it.  So, compared to the consequences of stashing documents
    in a static hierarchical file system (where the URIs become perma-
    bound at that moment to the resource at a published location),
    the assignment to Kavi folders involves less commitment.
    
    Example:
    
    The file "Sun 32-bit Binary Alignment Proposal.pdf" committed to
    the KMIP Kavi repository by Matt Ball on 2009-04-30 has these
    URIs:
    
    private: http://www.oasis-open.org/apps/org/workgroup/kmip/download.php/32244/Sun%20KMIP%20Alignment%20Proposal.pdf
    public: http://www.oasis-open.org/committees/download.php/32244/Sun%20KMIP%20Alignment%20Proposal.pdf
    
    But assignment of that document to the "Meeting Notes" folder (current
    as of 2009-05-14 10:18 AM ET) is ephemeral: that document can be moved
    to any other folder at will.
    
    Many of you will have noted that the key identifier portion in a Kavi
    document URI is just the 5-digit number.  All these are equivalent from
    the POV of fetching the resource:
    
    http://www.oasis-open.org/committees/download.php/32244/
    http://www.oasis-open.org/committees/download.php/32244/Matt-2009-04-30
    http://www.oasis-open.org/committees/download.php/32244/FooBard
    
    Citation Hygiene Best Practice Note:
    
    Please try to always cite the *public* URI for TC resources when
    giving URI references in documents that will become public.  OASIS
    rules require that all materials (documents, ballots, email messages)
    be publicly readable, so the private URIs are bad when they appear
    in public places (members of the public won't know how to concoct
    a public-URI variant, and may conclude that OASIS documents are
    locked behind password access controls.  It's unfortunate that Kavi
    creates the private URIs at all: we should avoid using them.
    
    - Robin Cover
    
    [1] http://www.oasis-open.org/committees/documents.php?wg_abbrev=kmip
    
    Robin Cover
    OASIS, Director of Information Services
    Editor, Cover Pages and XML Daily Newslink
    Email: robin@oasis-open.org
    Staff bio: http://www.oasis-open.org/who/staff.php#cover
    Cover Pages: http://xml.coverpages.org/
    Newsletter: http://xml.coverpages.org/newsletterArchive.html
    Tel: +1 972-296-1783
    
    ------------------------------------------------------------------------
    
    On Thu, 14 May 2009, Matt Ball wrote:
    
    > Hi Folks,
    > 
    > For completeness, here are the responses I sent to Rob Philpott...
    > 
    > Cheers,
    > -Matt
    > 
    >