[rfc-dist] RFC 9517 on A URN Namespace for the Data Documentation Initiative (DDI)

rfc-editor@rfc-editor.org Tue, 16 January 2024 23:09 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07629C14F68D; Tue, 16 Jan 2024 15:09:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2ZzjKadXlwQ; Tue, 16 Jan 2024 15:09:37 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55028C14F61E; Tue, 16 Jan 2024 15:09:37 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 3D746197AB3A; Tue, 16 Jan 2024 15:09:37 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240116230937.3D746197AB3A@rfcpa.amsl.com>
Date: Tue, 16 Jan 2024 15:09:37 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/i2oqcgxVyzX_g6ui3ZmrUxfhI3A>
Subject: [rfc-dist] RFC 9517 on A URN Namespace for the Data Documentation Initiative (DDI)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jan 2024 23:09:41 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9517

        Title:      A URN Namespace for the 
                    Data Documentation Initiative (DDI) 
        Author:     J. Wackerow
        Status:     Informational
        Stream:     Independent
        Date:       January 2024
        Mailbox:    joachim.wackerow@posteo.de
        Pages:      18
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-urn-ddi-06.txt

        URL:        https://www.rfc-editor.org/info/rfc9517

        DOI:        10.17487/RFC9517

This document describes the Namespace Identifier (NID) "ddi" for
Uniform Resource Names (URNs) used to identify resources that conform
to the standards published by the Data Documentation Initiative (DDI)
Alliance.

The DDI Alliance is not affiliated with the Internet Engineering Task
Force (IETF) or Internet Society (ISOC).  This Independent Submission
is not a standard nor does it have IETF community consensus.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC