-
Notifications
You must be signed in to change notification settings - Fork 98
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
Images as media types? #11
Comments
I'm new here. I don't see a way to "vote up" honging's comment. |
I'm not quite sure I fully understand, so could you help me understand how this might be different than an attachment annotation that would allow you to include metadata? |
Referencing https://github.com/appdotnet/api-spec/blob/master/objects.md makes note of an "image" type (or is an image simply a subset of an attachment type? this doesn't seem to be clarified in the spec). Instead of having an image: Once could generalize it further by not assuming the attachment is an image, but a generalized media type: { Which would let you embed videos as well: or who knows? Expanding on this, an image might look like: { |
Image is specifically for user icon and cover image. It's not the full and proper image annotation that we'll be adding (working on a draft of that as we speak.), more of a standard user schema for being able to have clients render posts from a user. |
It would be nice to have resolution info and maybe size (kb) info in the image objects as well. This might complicate media vs simple image but I think it will be necessary given screen and connectivity diversity. |
We're using an oembed annotation for this purpose: https://github.com/appdotnet/object-metadata/blob/master/annotations/net.app.core.oembed.md |
Looking over the API doc, could images be generalized as a media type which are then subcategorized based on MIME types? this would leave the door open for videos as well. If annotations could be attached to the media type, then we could create a pretty versatile bucket for dumping metadata (like EXIF). This could keep the core objects pretty small.
The text was updated successfully, but these errors were encountered: