Re: [yaco-liaison-tool] The liaison tool: Status Update

Patrik Fältström <> Thu, 07 April 2011 08:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5FB383A6971 for <>; Thu, 7 Apr 2011 01:33:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jbwa4NucThbc for <>; Thu, 7 Apr 2011 01:33:03 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id A05163A69E7 for <>; Thu, 7 Apr 2011 01:33:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1712; q=dns/txt; s=iport; t=1302165287; x=1303374887; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=DzA0H7NWpbXrSEQFsbfV30X65w+FUlCr4WDS1jUXxyI=; b=c44D349fIMGCthnKySlstS4nZ6jv0/vKwtyZxsKMDa4rbzNw7cDTYmzG 0AF0QTXjggGFX/F3Zd7rBrpqVHUOZWpdwMlFL4iLMDRGo8Sg8TfCT9VTO iaROkdPidDZqJIbmz2TmvPl58fse9KvndW0Lmn7Vz554XbjB2Ir3A6SYC o=;
X-IronPort-AV: E=Sophos;i="4.63,315,1299456000"; d="scan'208";a="24784188"
Received: from ([]) by with ESMTP; 07 Apr 2011 08:34:46 +0000
Received: from ( []) by (8.14.3/8.14.3) with ESMTP id p378YkBT011741; Thu, 7 Apr 2011 08:34:46 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <>
In-Reply-To: <>
Date: Thu, 7 Apr 2011 10:34:45 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
To: Henrik Levkowetz <>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Thu, 07 Apr 2011 04:23:15 -0700
Cc:, Eliot Lear <>, Ray Pelletier <>
Subject: Re: [yaco-liaison-tool] The liaison tool: Status Update
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of the Yaco / Liaison Statement Management Tool Project details <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 07 Apr 2011 08:33:05 -0000

On 7 apr 2011, at 10.25, Henrik Levkowetz wrote:

> Hi Emilio,
> On 2011-04-06 16:03 "Emilio A. Sánchez" said:
> ...
>>    I don't understand what data want's to edit Patrik when he say 'who 
>> holds the action item'. If he refers to the person who can 'take care' 
>> of a liaison, this person is selected automatically.
> But if the SDO Liaison Manager is changing, then liaisons which still
> need to be taken care of will need to be updated, no?

Any individual that have a role that have edit access to certain liaisons (depending on whether the liaison is incoming, outgoing and what external organisation is involved) must be able to update the action date and responsible person (that holds the token of action).

I have also seen cases when for example responses of some kind of liaisons have been added without having "link to older liaison" has not been set, so that kind of "cleanup" must also be possible.

For example, as liaison to Unicode Consortium from IETF, I should have such edit rights on the liaisons that have to do with Unicode Consortium (in or out).

ITU-T liaison (Eliot) should have such edit rights to any ITU-T related liaison.

Normally otherwise, an individual only have edit rights to either liaisons they have posted, or liaisons they are token holders of.

Or something like that.

The important thing is to be able to update the liaisons. And we can trust our (IETF) liaisons, so to get fine-grained access rights is not so important. The ability to get things right in the database is. Having bad data in the database -- as now -- is not working in the long(er) run.