[urn] Re: Registration for `c2pa` URN

Peter Saint-Andre <[email protected]> Mon, 3 Feb 2025 09:41:26 -0700
Newsgroups gmane.ietf.urn
Message-ID <[email protected]>
My apologies - apparently sending a note to IANA totally slipped my 
mind. I'll take care of this today.

On 2/2/25 10:46 PM, Leonard Rosenthol wrote:
> Hey folks.
> 
> I thought this was all put to bed and approved, but it was pointed out 
> to me that our URN isn’t on the list at https://www.iana.org/ 
> assignments/urn-namespaces/urn-namespaces.xhtml <https://www.iana.org/ 
> assignments/urn-namespaces/urn-namespaces.xhtml>
> 
> Did I forget to do something after this message to make it final???   
> What else needs to be done?
> 
> Thanks,
> 
> Leonard
> 
> *From: *Leonard Rosenthol <[email protected]>
> *Date: *Saturday, August 17, 2024 at 1:13 AM
> *To: *Peter Saint-Andre <[email protected]>, Dale R. Worley 
> <[email protected]>
> *Cc: *[email protected] <[email protected]>
> *Subject: *Re: [urn] Re: Registration for `c2pa` URN
> 
> Thanks.  Updated ABNF. (we had too many `:`s coming up in conjunction 
> with the optional values.
> 
> c2pa_urn = c2pa-namespace UUID [claim-generator [version-reason]]
> 
> c2pa-namespace = "urn:c2pa:"
> 
> ; this definition is taken from RFC 9562
> 
> UUID     =  4hexOctet "-"
> 
>                                                  2hexOctet "-"
> 
>                                                  2hexOctet "-"
> 
>                                                  2hexOctet "-"
> 
>                                                  6hexOctet
> 
> hexOctet = HEXDIG HEXDIG
> 
> DIGIT    = %x30-39
> 
> HEXDIG   = DIGIT / "A" / "B" / "C" / "D" / "E" / "F"
> 
> ; ASCII, but not Control Characters or Graphic Characters
> 
> visible-char-except-space = %x21-7E / %x80-FF
> 
> ; claim-generator-identifier is a string of 0 to 32 visible-char-except- 
> space characters
> 
> ; this means that an empty string is valid
> 
> claim-generator = ":" claim-generator-identifier
> 
> claim-generator-identifier = 0*32visible-char-except-space
> 
> ; version-reason is a string consisting of a positive integer
> 
> ; followed by an underscore and a positive integer
> 
> version-reason = ":" version "_" reason
> 
> version = 1*DIGIT
> 
> reason = 1*DIGIT
> 
> *From: *Peter Saint-Andre <[email protected]>
> *Date: *Friday, August 16, 2024 at 10:03 AM
> *To: *Leonard Rosenthol <[email protected]>, Dale R. Worley 
> <[email protected]>
> *Cc: *[email protected] <[email protected]>
> *Subject: *Re: [urn] Re: Registration for `c2pa` URN
> 
> EXTERNAL: Use caution when clicking on links or opening attachments.
> 
> 
> Feel free to send only the ABNF.
> 
> On 8/16/24 6:41 AM, Leonard Rosenthol wrote:
>> We did find a few issues with the ABNF, so I have an update to that.
>>
>> Should I send a full update or just the changes?
>>
>> Thanks,
>>
>> Leonard
>>
>> *From: *Dale R. Worley <[email protected]>
>> *Date: *Tuesday, August 13, 2024 at 3:25 PM
>> *To: *Leonard Rosenthol <[email protected]>
>> *Cc: *[email protected] <[email protected]>
>> *Subject: *Re: [urn] Registration for `c2pa` URN
>>
>> EXTERNAL: Use caution when clicking on links or opening attachments.
>>
>>
>> Leonard Rosenthol <[email protected]> writes:
>>> Here is the revised registration proposal.   The links to 2.1 will be
>>> live tomorrow (2-Aug-2024).
>>>
>>> Leonard
>>> Namespace Identifier:  c2pa
>>>
>>> Version:  1
>>>
>>> Date:  2024-07-30
>>
>> It all looks good to me.  The only comment I have is that the ABNF
>> allows the version to have leading 0's, though the text makes clear that
>> the *value* 0 is not permitted.  But as long as C2PA is OK with that,
>> that's fine.
>>
>> Dale
>>
>>
>> _______________________________________________
>> urn mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
> 

_______________________________________________
urn mailing list -- [email protected]
To unsubscribe send an email to [email protected]