-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clipboard format missing? #507
Comments
Just to note that clipboard name and OSX UTI name are not things normally submitted in the media type registration. They seem to be extra items only found in some W3C-originated registrations. The IETF registrations guidelines do not require or mention them at all. Some examples include: As per Ivan's email to me, not sure if there is a point for clipboard data for csvm+json since this is a metadata format. Regular CSV may benefit but that's a different discussion. |
(Copying the end of a longer thread)
|
My personal opinion is not to specify the clipboard formats on the csvm+json document as per Ivan's comment that it is not useful. If a new revision of RFC 4180 comes out, we should surely consider it. |
Set the label to review and decide on the call. For the records, I agree with @yakovsh |
@JeniT to respond on list. |
@JeniT 's official answer to the commenter: http://www.w3.org/mid/etPan.5540cb55.79a1deaa.d2@jenit.local |
Do I understand that the group considers it inappropriate to copy-and-paste csvm ? |
@polx I don't think we see any special handling for copy-and-paste csvm JSON over and above what's done for other kinds of JSON. |
Jeni, JSON copy and paste, in a user-oriented-form, does not really exist as Answering Yves, I've suggested that the feature that has been now paul |
@polx The question for the CSV on the Web Working Group is whether it is appropriate for the specification of this particular JSON vocabulary to include a specification of general JSON clipboard formats. I would argue that it is outside the scope of what this group should do. That doesn't mean it's not needed, just that it's not something that this group has the remit or expertise to achieve. We can take the action to request the appropriate groups to take a look, and we can do that for CSV as well. If you're not content with us saying nothing about clipboard formats for JSON, please could you provide some more specific recommendations about what you think we should say? Thanks. |
Jenni,
That is as irrealistic as defining a clipboard name or media type for Maybe I should remind that, generally, content sniffing is not done or Specifying a clipboard name and media-type for CSVM is completely paul |
@polx OK. Can you tell me what text we should include in the media type registration to do this, or point to a media type registration in which you think that this has been done well so that we can copy that pattern? |
Hello Jeni, Examples: What you need:
Here is my suggestion:
hope it helps. paul PS: as far as I know, Linux Window Managers use the media type for |
Thank you Jeni, |
Paul Libbrecht's comment
The thread includes mails from @danbri, @yakovsh, and, @timbl.
The text was updated successfully, but these errors were encountered: