Re: [GNAP] Terminology PR
Adrian Gropper <agropper@healthurl.com> Wed, 06 January 2021 21:52 UTC
Return-Path: <agropper@gmail.com>
X-Original-To: txauth@ietfa.amsl.com
Delivered-To: txauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1615B3A12C6 for <txauth@ietfa.amsl.com>; Wed, 6 Jan 2021 13:52:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level:
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Cg8I3CLSlZI for <txauth@ietfa.amsl.com>; Wed, 6 Jan 2021 13:52:02 -0800 (PST)
Received: from mail-vs1-f48.google.com (mail-vs1-f48.google.com [209.85.217.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C3453A12BE for <txauth@ietf.org>; Wed, 6 Jan 2021 13:52:02 -0800 (PST)
Received: by mail-vs1-f48.google.com with SMTP id s85so2593428vsc.3 for <txauth@ietf.org>; Wed, 06 Jan 2021 13:52:02 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=skenW4qrCzSsS5xPAwhW6h4INXfO5T0/yHMeWO40OEo=; b=ZhCm/6zRohMDrPmBo8Jjyru8yc9XjmmLFllokqGk3pE37XlAj9yMJ45jjJJUFl9H4e qXXfVUWBmoigRVFuZGE31XKqT39dhZgQteZ6/26kdkRKZ/C+xHQE7wtHm5Ykn/Gip8mI TsNJTAIUlJOBRrx5BuVXxTeHaM0MFWssj3QPEHGMRx2KKYd/l+0w/Kkq5DcRYOT79wxU 5NZ2AhO+RAWmD2HfeNyhqTD7b08BWqGaOKjJkQ3kSX9l2E+5cLQ6cbGdA+BlNR3zidzy sb0tj6928fTJGDEi+yQaDFe8c0HBzrXg5IuhjUbU0HDbg947Vr2d0deY+Npt68Js3+Mz yXgA==
X-Gm-Message-State: AOAM532KnS9djHcPZg3dWRBKGpv4/gLXsfWJIVprnQ2UU3y4Ne/QvrWV 1ajI1lqTfo6EzfJlTljhrHTGOBsCEPRcZs9v7/Q=
X-Google-Smtp-Source: ABdhPJxPQYp2DhA/1e5umw34pNOysSmuCpejlnYQmB/zbXDPlblWbc7wzpa0xR6BDf580/I4y2+klqdvzrJwqM3Z0OI=
X-Received: by 2002:a67:2e16:: with SMTP id u22mr5252733vsu.12.1609969921220; Wed, 06 Jan 2021 13:52:01 -0800 (PST)
MIME-Version: 1.0
References: <CAM8feuQyd6o_7zcs_O1KEbFkni1-c8BGdC57vQbukgVYavE5-Q@mail.gmail.com> <DAB2E8D3-DC9F-4502-8D6E-5BE2066AEF88@openconsent.com> <CAM8feuSaSeiSe7_T8BGEyQYDAd3PvUa-uO-rEDLcZPkos7KPbg@mail.gmail.com> <CAK2Cwb5J-hg7jEa78rRHgj68=tj5H5M6aW6JFYGsCG+SG5D52Q@mail.gmail.com>
In-Reply-To: <CAK2Cwb5J-hg7jEa78rRHgj68=tj5H5M6aW6JFYGsCG+SG5D52Q@mail.gmail.com>
From: Adrian Gropper <agropper@healthurl.com>
Date: Wed, 06 Jan 2021 16:51:50 -0500
Message-ID: <CANYRo8i6uNTfaSb=tiMeaDKO_83m2EGtH0xr=sgkEHeOYyKCZw@mail.gmail.com>
To: Tom Jones <thomasclinganjones@gmail.com>
Cc: Fabien Imbault <fabien.imbault@gmail.com>, Mark Lizar <mark@openconsent.com>, GNAP Mailing List <txauth@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000040e73f05b84255f6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/IWMFUaMU1gUBsULqj30xPXtGZ7g>
Subject: Re: [GNAP] Terminology PR
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: GNAP <txauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/txauth>, <mailto:txauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/txauth/>
List-Post: <mailto:txauth@ietf.org>
List-Help: <mailto:txauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/txauth>, <mailto:txauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 21:52:04 -0000
I'm new to the GNAP list so please forgive me as I get up to speed. RO is a role and the 'subject' of a piece of data is not. I don't see any problem in keeping this distinction straight throughout the spec. - Adrian On Wed, Jan 6, 2021 at 4:27 PM Tom Jones <thomasclinganjones@gmail.com> wrote: > Right - the correct term should be *subjects' information* as there are > potentially two subjects, the RO and the "end-user" (really terribly > confusing name). If you consider the case where the end-user is the parent > of a child, or of their spouse, both subjects will be asked to supply > information in order to be authenticated. > Peace ..tom > > > On Wed, Jan 6, 2021 at 5:20 AM Fabien Imbault <fabien.imbault@gmail.com> > wrote: > >> Hi Mark, >> >> Thanks for the feedback. >> >> The original requirement for "subject" comes from the reference to >> https://tools.ietf.org/html/draft-ietf-secevent-subject-identifiers-06 >> (used in the main text). The objective was to try to avoid various terms >> which are synonyms. >> >> You're right, it's close to a legal entity, except from the fact that it >> is defined more broadly (person, organization or device), which is >> something we can encounter for the RO for instance. >> >> For instance we had previous discussions where the RO was defined as : >> "personal or organizational entity" >> which I replaced in the latest draft by >> "subject entity" (since it is defined) >> >> For "Subject Information", the question whether this refers to the >> end-user or the RO is currently left open. >> >> Please let me know your thoughts. >> >> Cheers >> Fabien >> >> On Tue, Jan 5, 2021 at 8:38 PM Mark Lizar <mark@openconsent.com> wrote: >> >>> Hi Fabien, et al, >>> >>> Great start!! >>> >>> Could you clarify the use and application of the term subject, as the >>> term is used in some legal standards for semantics and I wonder if this is >>> related to the legal semantic attribution of data subject. >>> >>> In the glossary, it also seems the Subject Entity is referring to what >>> is commonly know as legal entity. And the term subject can refer to a few >>> things at this technical level.— e.g. a semantic term referencing in >>> general the *topic* of the resource or is it the* legal entity >>> / credential *that corresponds to the accountable controller of a >>> resource ? >>> >>> - Mark >>> >>> On 5 Jan 2021, at 08:04, Fabien Imbault <fabien.imbault@gmail.com> >>> wrote: >>> >>> Hi everyone, >>> >>> I wish you all a happy new year. >>> >>> I just created a PR ( >>> https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/155) that takes >>> into account the various feedbacks. The automatic build process is not >>> working, but you can see the diffs and build the html locally if you >>> prefer. The definitions have also been updated on the wiki ( >>> https://github.com/ietf-wg-gnap/gnap-core-protocol/wiki/Terminology) if >>> you prefer to check there. >>> >>> Feedbacks welcome before we move to pending merge later on. >>> >>> Cheers >>> Fabien >>> -- >>> TXAuth mailing list >>> TXAuth@ietf.org >>> https://www.ietf.org/mailman/listinfo/txauth >>> >>> >>> -- >> TXAuth mailing list >> TXAuth@ietf.org >> https://www.ietf.org/mailman/listinfo/txauth >> > -- > TXAuth mailing list > TXAuth@ietf.org > https://www.ietf.org/mailman/listinfo/txauth >
- [GNAP] Terminology PR Fabien Imbault
- Re: [GNAP] Terminology PR Mark Lizar
- Re: [GNAP] Terminology PR Fabien Imbault
- Re: [GNAP] Terminology PR Fabien Imbault
- Re: [GNAP] Terminology PR Tom Jones
- Re: [GNAP] Terminology PR Adrian Gropper
- Re: [GNAP] Terminology PR Tom Jones
- Re: [GNAP] Terminology PR Fabien Imbault
- Re: [GNAP] Terminology PR Tom Jones
- Re: [GNAP] Terminology PR Fabien Imbault
- Re: [GNAP] Terminology PR Denis
- Re: [GNAP] Terminology PR Fabien Imbault
- Re: [GNAP] Terminology PR Denis
- Re: [GNAP] Terminology PR Fabien Imbault
- Re: [GNAP] Terminology PR Fabien Imbault