Hi Amanda, Yes please keep it open I'm reaching out to the apache support team and a colleague to see if there is interest in providing some help to get the required information to you. Especially around the interoperability considerations.
The feedback from Darell has outlined pretty clearly what needs to be done. I have just been a little swamped. Thanks [cid:8a6d41bb-ab8a-472b-a3b4-97ea8940b0ff] Scott Lutwyche Enterprise Data Architect Climate Biodiversity and Information Information and Digital Science Delivery | Science Data Operations Department of Environment and Science ________________________________ P: 0421 058 554 | T : Teams Chat<https://teams.microsoft.com/l/chat/[email protected]> E: [email protected]<mailto:[email protected]> 41 Boggo Rd, Dutton Park 4102, GPO Box 2454 BRISBANE Qld 4001 ________________________________ From: Amanda Baber via RT <[email protected]> Sent: 28 February 2023 09:14 To: Scott Lutwyche <[email protected]> Subject: [IANA #1264350] application/vnd.apache.parquet registration request Hi Scott, I haven't seen a response to this message. Do you want us to keep this open for another 30 days? You can update your request by editing your changes into this text and sending it back in a reply to this message: Name: Scott Lutwyche Hi Scott, I haven't seen a response to this message. Do you want us to keep this open for another 30 days? You can update your request by editing your changes into this text and sending it back in a reply to this message: Name: Scott Lutwyche Email: [email protected] Media type name: application Media subtype name: vnd.apache.parquet Required parameters: N/A Optional parameters: N/A Encoding considerations: binary Security considerations: the security issues associated with this type have not been assessed Interoperability considerations: refer to https://urldefense.com/v3/__https://github.com/apache/parquet-format__;!!PUY2jUP3Fp7oEg!DFAtFXXZ8LGV0At905HmGDRfHgZp0ukMpL3vasRpspeKqQrIXwxQEcoJKNNlJDsMHy84FmiGsexPh0Z7JS3uPzIwgAkIaQ$ Published specification: https://urldefense.com/v3/__https://github.com/apache/parquet-format__;!!PUY2jUP3Fp7oEg!DFAtFXXZ8LGV0At905HmGDRfHgZp0ukMpL3vasRpspeKqQrIXwxQEcoJKNNlJDsMHy84FmiGsexPh0Z7JS3uPzIwgAkIaQ$ Applications which use this media: It's used by many applications - sql based client tools and binary readers, also common in most cloud based data platforms Fragment identifier considerations: refer to https://urldefense.com/v3/__https://github.com/apache/parquet-format__;!!PUY2jUP3Fp7oEg!DFAtFXXZ8LGV0At905HmGDRfHgZp0ukMpL3vasRpspeKqQrIXwxQEcoJKNNlJDsMHy84FmiGsexPh0Z7JS3uPzIwgAkIaQ$ Restrictions on usage: refer to https://urldefense.com/v3/__https://github.com/apache/parquet-format__;!!PUY2jUP3Fp7oEg!DFAtFXXZ8LGV0At905HmGDRfHgZp0ukMpL3vasRpspeKqQrIXwxQEcoJKNNlJDsMHy84FmiGsexPh0Z7JS3uPzIwgAkIaQ$ Provisional registration? (standards tree only): Yes Additional information: 1. Deprecated alias names for this type: not known 2. Magic number(s): 4-byte magic number "PAR1" 3. File extension(s): .parquet 4. Macintosh file type code: .parquet 5. Object Identifiers: mime-generic-data OBJECT IDENTIFIER ::= Person to contact for further information: 1. Name: [email protected] 2. Email: [email protected] Intended usage: COMMON This file and the Thrift definition should be read together to understand the format. Author/Change controller: https://urldefense.com/v3/__https://lists.apache.org/[email protected]__;!!PUY2jUP3Fp7oEg!DFAtFXXZ8LGV0At905HmGDRfHgZp0ukMpL3vasRpspeKqQrIXwxQEcoJKNNlJDsMHy84FmiGsexPh0Z7JS3uPzKi89Evjg$ thanks, Amanda Baber IANA Operations Manager On Sat Feb 04 16:20:09 2023, [email protected] wrote: > Hi Scott, > > Thank you for your registration request. Apologies for the delay in > responding. There are few items that need to be addressed in your > submission. > > > 1. You answered yes to “provisional registration”, however, that is > only applicable for standards tree registrations and you are making a > submission to the vendor subtree. The appropriate answer to that > question is no. > 2. Regarding the security considerations, considering parquet is > encoded using Apache Thrift, it would be helpful to consumers of this > media type to understand that it has similar security considerations > to those defined by the Apache Thrift registration. Perhaps > reiterating the security considerations from here would be helpful > https://urldefense.com/v3/__https://www.iana.org/assignments/media-__;!!PUY2jUP3Fp7oEg!DFAtFXXZ8LGV0At905HmGDRfHgZp0ukMpL3vasRpspeKqQrIXwxQEcoJKNNlJDsMHy84FmiGsexPh0Z7JS3uPzIX3BrXxA$ > types/application/vnd.apache.thrift.json > 3. The interoperability considerations points to the GitHub project. > However, there is no obvious document that contains interoperability > considerations within that document. The file format identifies a > “magic number” that appears to contain some kind of version. The > extensibility section mentions a file version but it is not clear if > that is the same or different than the value in file format. The > value of the media type registration is to allow someone who is > familiar with the specification to extract some of the key pieces of > information and present that information in a standardized way to > media type handlers to help them work with the format in an optimal > way, without needing to be intimately familiar with the details of the > specification. If you could summarize the interoperability > considerations for this format, it would be very helpful. > 4. I was not able to find any reference how fragment identifiers > might be used with this media type. If such support exists for the > format, could you link to a description of it specifically. > Otherwise, it might be appropriate to simply state that fragment > identifiers are not supported for this media type. > 5. Regarding restrictions on usage, based on your description of its > current usage, it would appear that anyone is free to use this format > and therefore N/A would be the appropriate answer to that question, if > that is the case. > > As this is a submission to the vendor tree, and not the standards > tree, the requirements are relaxed and it is sufficient to use a > reference to external content. However, if this were to be registered > in the standards tree, it would be necessary to “inline” the content > to ensure that changes are not made without updating the registration. > > If you could update your submission based on this feedback, that would > be appreciated. > > Darrel > > ===== > > Name: Scott Lutwyche > > Email: [email protected] > > Media type name: application > > Media subtype name: vnd.apache.parquet > > Required parameters: N/A > > Optional parameters: N/A > > Encoding considerations: binary > > Security considerations: the security issues associated with this type > have not been assessed > > Interoperability considerations: refer to > https://urldefense.com/v3/__https://github.com/apache/parquet-format__;!!PUY2jUP3Fp7oEg!DFAtFXXZ8LGV0At905HmGDRfHgZp0ukMpL3vasRpspeKqQrIXwxQEcoJKNNlJDsMHy84FmiGsexPh0Z7JS3uPzIwgAkIaQ$ > > Published specification: > https://urldefense.com/v3/__https://github.com/apache/parquet-format__;!!PUY2jUP3Fp7oEg!DFAtFXXZ8LGV0At905HmGDRfHgZp0ukMpL3vasRpspeKqQrIXwxQEcoJKNNlJDsMHy84FmiGsexPh0Z7JS3uPzIwgAkIaQ$ > > Applications which use this media: It's used by many applications - > sql based client tools and binary readers, also common in most cloud > based data platforms > > Fragment identifier considerations: refer to > https://urldefense.com/v3/__https://github.com/apache/parquet-format__;!!PUY2jUP3Fp7oEg!DFAtFXXZ8LGV0At905HmGDRfHgZp0ukMpL3vasRpspeKqQrIXwxQEcoJKNNlJDsMHy84FmiGsexPh0Z7JS3uPzIwgAkIaQ$ > > Restrictions on usage: refer to > https://urldefense.com/v3/__https://github.com/apache/parquet-__;!!PUY2jUP3Fp7oEg!DFAtFXXZ8LGV0At905HmGDRfHgZp0ukMpL3vasRpspeKqQrIXwxQEcoJKNNlJDsMHy84FmiGsexPh0Z7JS3uPzL4IzuXRg$ > format > > Provisional registration? (standards tree only): Yes > > Additional information: > > 1. Deprecated alias names for this type: not known > 2. Magic number(s): 4-byte magic number "PAR1" > 3. File extension(s): .parquet > 4. Macintosh file type code: .parquet > 5. Object Identifiers: mime-generic-data OBJECT IDENTIFIER ::= > > Person to contact for further information: > > 1. Name: [email protected] > 2. Email: [email protected] > > Intended usage: COMMON > > This file and the Thrift definition should be read together to > understand the format. > > Author/Change controller: > https://urldefense.com/v3/__https://lists.apache.org/[email protected]__;!!PUY2jUP3Fp7oEg!DFAtFXXZ8LGV0At905HmGDRfHgZp0ukMpL3vasRpspeKqQrIXwxQEcoJKNNlJDsMHy84FmiGsexPh0Z7JS3uPzKi89Evjg$ > > _______________________________________________ > media-types mailing list > [email protected] > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/media-types__;!!PUY2jUP3Fp7oEg!DFAtFXXZ8LGV0At905HmGDRfHgZp0ukMpL3vasRpspeKqQrIXwxQEcoJKNNlJDsMHy84FmiGsexPh0Z7JS3uPzIVLwSGhg$ ------------------------------ The information in this email together with any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. There is no waiver of any confidentiality/privilege by your inadvertent receipt of this material. Any form of review, disclosure, modification, distribution and/or publication of this email message is prohibited, unless as a necessary part of Departmental business. If you have received this message in error, you are asked to inform the sender as quickly as possible and delete this message and any copies of this message from your computer and/or your computer system network. ------------------------------
