Clipboard identifiers from YAML

[ioggstream]

From media type ML

Question

Except being exchanged over http and being edited by simple text-editors (as text), I am supposing that YAML content is likely to be exchanged among editors using a copy-and-paste exchange mechanism. Is it the case?

If this is the case, I would like to suggest to add uniform type identifiers and windows clipboard names so that future implementations may take part to such an exchange in the Additional Information section.

See #1

[polx]

There's a few media-type registrations which contain clipboard format names. Among others MathML, SVG, USDA.

In general, windows clipboard flavor names are freely choosable. Apple's (macOS and iOS) Universal Type Identifiers (UTIs) are now somewhat governed by Apple documentation, I recommend starting at wikipedia's entry.

In general, it makes a lot of sense to consider existing widespread implementations first.

[ioggstream]

@polx can the following values work? I read the wikipedia entry, but is seems a very apple-specific stuff: should they "validate" the value? If we need to add them later, we should be able to do it directly with the IANA, no need to publish a new RFC, right?

@eemeli since you are the YAML expert, the decision is up to you and the other YAML folks.

Windows Clipboard Name: YAML

Macintosh Universal Type Identifier code: public.yaml

[polx]

For Windows, I believe this can.

For macOS, I am unfortunately unsure. Although several have defined public.-prefixed UTIs, it appears that Apple now considers these UTIs as being those that the OS defines. This was highlighted in this comment although it kind of contradicts the history of what was done earlier. That thread has not resolved yet. I would feel that public.yaml is good but it would be important to check with some members at Apple to ensure this or simply use org.yaml.

[ioggstream]

Let's wait for @eemeli .

This should be done in coordination with Apple and MS though. If we don't have connections my suggestion is to defer after the publication.

@darrelmiller can you provide a contact for the windows clipboard identified stuff? Can we use this repo after publication for tracking this kind of activities ?

[darrelmiller]

@ioggstream I will go hunting.

[polx]

I doubt that waiting on the feedback from Apple or MicroSoft folks will be timely.

From Declaring New Uniform Type Identifiers I see that the reverse DNS approach is likely the most accepted. May I suggest the following?

MacOS Uniform Type Identifier: org.yaml conforms to public.utf8-plain-text

For windows, my recommendation above stays as no strict specification seem to exist:

Windows Clipboard Name: YAML

Hope it helps.

Paul

[ioggstream]

@darrelmiller do you think Windows folks will just adapt picking the value we chose? If not, I think that updating the registration afterwards is a sensible choice.

[polx]

Here is the documentation bit for windows: https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-registerclipboardformatw

From that page, there seems to be plenty of freedom: either the app chooses something that exists and takes over the same number for its type identifier (they have converged) or they choose to diverge.

I think that those who would adapt if decided now or adapted afterwards are the apps that circulate.

[darrelmiller]

I have not got any further information from Microsoft folks, however, what I have seen is that it is it is expected that people who want to adopt a value are responsible for doing their own due diligence to ensure that the value has not been used for alternative purposes. I believe that using the YAML clipboard name is a safe choice and that we can close this issue.

[ioggstream]

I believe that using the YAML clipboard name is a safe choice and that we can close this issue

@darrelmiller should we register the YAML clipboard name in the media type registration, then?