Re: [ddi-developers] Digest for ddi-developers@googlegroups.com - 1 update in 1 topic

[Pascal Heus]

Olaf:

Thanks for looking into this. I find the double 'ddi' a bit odd/confusing. I also ran this question through a couple of LLMs. 

Some suggestions:

- Use application/vnd.ddialliance.* (instead of application/vnd.ddi.*)

   + This may apply to other  Alliance products that do not start with DDI (e.g. SDTL, CVs, future specs)

- Consider using parameters for the version (though it should be in the XML as well). For example application/vnd.ddialliance.ddi-c+xml;version=2.5

- For CDI (and potentially lifecycle), keep in mind that there are other RDF serializations (JSON-LD, turtle, N3). So, I will formalize these as well. 

   + for example application/vnd.ddilliance.cdi+json

   + I'm also still hoping someday for an official codebook JSON (this is a barrier to adoption)

- Consider official registration with IANA

Hope this helps.

Best,

*P

On Tue, Apr 8, 2025 at 6:11 PM <ddi-dev...@googlegroups.com> wrote:

ddi-dev...@googlegroups.com

Google Groups

Topic digest
View all topics

• mime types for DDI - 1 Update

mime types for DDI

Olof Olsson <bor...@gmail.com>: Apr 08 12:11AM -0700 Hi! This was something i was thinking about bringling up on the last DDI Developers meeting. I know this topic have been discussed a few years ago but there is currently still not recommendation or documentation about prefered mimetypes for DDI representations.   Looking arround it seems like the mime type should never include the version but rather the product so thing would mean something like this (for the XML representations):   application/vnd.ddi.ddi-c+xml application/vnd.ddi.ddi-l+xml application/vnd.ddi.ddi-cdi+xml   This is inspired by the listing from DataCites specified content types in thier documentation: https://support.datacite.org/docs/datacite-content-resolver   Would be happy for any suggestions or comments and if anyone think this is something we could find an agreement on and suggest as a part of the official documentation.   Will add this as a discussion point on the next virtual DDI Developers Meeting.   Best regards, Olof

Back to top

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to ddi-developer...@googlegroups.com.

[Olof Olsson]

Hi Pascal!

Good point, make sense to use  application/vnd.ddialliance.*

Having a parameter for version as a recommended part is also a good point.

for cdi i think it should be ddi-cdi to bring it into line with the naming convension for ddi-c and ddi-l.

Updated suggestion (for xml):
application/vnd.ddialliance.ddi-c+xml
application/vnd.ddialliance.ddi-l+xml
application/vnd.ddialliance.ddi-cdi+xml

Example with version:
application/vnd.ddialliance.ddi-c+xml;version=2.6
application/vnd.ddialliance.ddi-l+xml;version=3.3
application/vnd.ddialliance.ddi-cdi+xml;version=1.0

Register the prefix with IANA might be good to reserve it, will talk to TC if this is something we should look into.

Official json schema is in the bete for ddi-l 4.0 and also possible for ddi-cdi.

Ddi-c might get json schema in the future but I dont think there is any concrete plans for it yet.

Best regards,

Olof

[Joachim Wackerow]

Hi Olof, others,

Good exchange!

Reading here about mime types, thoughts about a DDI REST API came into my mind. I think only with a default API the vision of the use of distributed DDI can become reality. Mime types are one step but an API seems to be also important. Could this be another topic for the next meeting?

I have some old practical plans on a REST API in small zip files (mime types are also mentioned). Should I send them to the list?

Cheers,

Achim

--
You received this message because you are subscribed to the Google Groups "DDI Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ddi-developer...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ddi-developers/9f39a864-f812-4d51-8ba0-56896cf4a357n%40googlegroups.com.

[Olof Olsson]

Hi Achim!

I remember your proposal for a standard API and i think it would be good to present in to the group to see if there is any feedback.

Not sure if attachement works on google groups but if you have the posibility upload your files to a git repository and link it.

Wil you be able to attend the next developers meeting (may 14th 16:00 CET) to present your proposal for the standard REST API?

Best regards,

Olof

[Paul Libbrecht]

Hello all,

I am not much involved in the DDI effort. Congratulations for your progresses.

I have been registering media types for MathML and it went like a breeze by simply posting the template to the media types mailing-list
https://mailarchive.ietf.org/arch/browse/media-types/
Having a public visibility of the registration (e.g. as part of an ongoing specification process) is a useful step.

The template is described in RFC 6838. Note, however, that a somewhat slow process is being worked upon to renew the process (RFC6838bis) in order to accommodate for structured media type names. Maybe reading the current editor copy is better: https://ietf-wg-mediaman.github.io/6838bis/draft-ietf-mediaman-6838bis.html as you are proposing sub-trees. The vendor sub-tree is probably unproblematic, should the DDI be enough publicly visible.

In Summary: Filling the template and including it in the spec is the best practice (as an appendix). It should be posted and discussed before at the media-types’ mailing-list.

Hope it helps.

Paul

--

[Pascal Heus]

Paul:

Thanks for sharing your experience with registering mime types. Sounds less painful than I thought it would be.

Best,

*P

On Fri, Apr 11, 2025 at 6:11 PM <ddi-dev...@googlegroups.com> wrote:

ddi-dev...@googlegroups.com

Google Groups

Topic digest
View all topics

• Digest for ddi-dev...@googlegroups.com - 1 update in 1 topic - 1 Update

Digest for ddi-dev...@googlegroups.com - 1 update in 1 topic

Paul Libbrecht <pa...@hoplahup.net>: Apr 09 11:09PM +0200

Back to top