Re: [urn] FW: Submission of "URN Namespace for Metaverse Standards Forum Resources"

[Peter Saint-Andre <[e-mail]>]

Thomas, when you are ready, please send to this list an updated 
registration request that conforms to RFC 8141.

Also, I concur with Dale Worley's note that the NID is very long, likely 
without necessity. As he suggested, shortening it to "metaverse" or 
"mso" seems appropriate.

Peter

On 12/20/23 11:27 AM, Peter Saint-Andre wrote:
> Hi Thomas,
> 
> Overall this appears to be a fine use of URNs.
> 
> The registration in the Internet-Draft follows the template in RFC 2141, 
> not RFC 8141, so please make sure to update it.
> 
> An Internet-Draft is not necessary, since we can directly submit the 
> registration to IANA; feel free to send the updated registration to this 
> discussion list so that other members of the expert review team can 
> provide their feedback.
> 
> With that said, if you wish to pursue publication as an RFC, it's likely 
> that the Independent Stream would be most appropriate. I would be happy 
> to discuss this with you offlist.
> 
> Peter
> 
> On 12/20/23 1:40 AM, Thomas Stockhammer wrote:
>> Dear colleagues,
>>
>> On behalf of the Metaverse Standards Forum 
>> <https://metaverse-standards.org/> I have submitted an I-D here 
>> https://datatracker.ietf.org/doc/draft-stockhammer-msf-urn/ 
>> <https://datatracker.ietf.org/doc/draft-stockhammer-msf-urn/> with the 
>> title “URN Namespace for Metaverse Standards Forum Resources “ and the 
>> following scope
>>
>>     This document describes the Namespace IDentifier (NID) 'metaverse-
>>
>>     standards-org' for Uniform Resource Names (URNs) used to identify
>>
>>     resources published by Metaverse Standards Forum.  The forum
>>
>>     specifies and manages resources that utilize this URN identification
>>
>>     model.  Example resources include ressources, eXtensible Markup
>>
>>     Language (XML) Schemas, classification schemes, XML Document Type
>>
>>     Definitions (DTDs), namespaces, style sheets, and other types of
>>
>>     resources produced or managed by the Metaverse Standards Forum.
>>
>> By advise of Jim Fenton and Stephan Wenger (both in CC; thanks for 
>> your help), they suggested to post to the URN and make you aware that 
>> MSF is working on this.
>>
>> Note that we also have an MSF version here: 
>> https://github.com/MetaverseStandards/Internet-Drafts/ 
>> <https://github.com/MetaverseStandards/Internet-Drafts/> and you may 
>> submit any issues or pull requests directly into the repo at MSF
>>
>> Thanks for your support on this matter and happy holidays.
>>
>> Thomas (on behalf of the Metaverse Standards Forum)
>>
>> —
>> Dr. Thomas Stockhammer || Senior Director Technical Standards || 
>> Qualcomm Germany GmbH  || Mobile: [phone] || 
>> <https://wa.me/491725702667> Title: LinkedIn - Description: LinkedIn 
>> icon <http://www.linkedin.com/in/stockhammer>Title: Facebook - 
>> Description: Facebook icon <https://www.facebook.com/tstockhammer> 
>> Github symbol (png logo icon) blue <https://github.com/haudiobe> 
>> Discord Logo - Logo, zeichen, emblem, symbol. Geschichte und Bedeutung 
>> <https://discord.com/channels/thomassto#6183>
>> Qualcomm Germany GmbH, Anzinger Str. 13, 81671 München, Amtsgericht 
>> München, HRB 133031 , Geschäftsführer: Kathryn Elizabeth Turner, 
>> Hamid-Reza Nazeman, Benjamin Sokolowski
>>
>> This message may contain information which is confidential or 
>> privileged. If you are not the intended recipient, please advise the 
>> sender immediately by reply e-mail and delete this message and any 
>> attachments without retaining a copy. Thank you. Qualcomm CDMA 
>> Technologies GmbH has taken every reasonable precautions to ensure 
>> that any attachments to this e-mail has been swept for viruses. 
>> However, we cannot accept liability for any damage sustained as a 
>> result of software viruses and would advise that you carry out your 
>> own virus checks before opening any attachment.
>>
>>
>> _______________________________________________
>> urn mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/urn
>