Closed amwebb closed 9 years ago
so for clients that do not support showing images:
is that right?
it seems pretty acceptable to me.
Best Regards, Yin Qu (屈垠)
On Thu, Feb 7, 2013 at 5:41 PM, Andrew Webb notifications@github.comwrote:
currently, a majority, if not all, composite fields of type="image" have hide="true" in meta-metadata. i think this is wrong, or at least problematic for our new metadata visualizations. i would like to remove hide="true" on all image fields. it should be an application's metadata visualization that decides whether or not to the show an image field and how to represent it (you may still want to show a link).
is this acceptable? it will require changes in existing metadata visualizations that do support showing images. if we agree, i will begin making the changes.
— Reply to this email directly or view it on GitHubhttps://github.com/ecologylab/BigSemanticsWrapperRepository/issues/2.
Yin -- I think that is an excellent functional description of what it should do.
I would add that effected applications include ice, mâché,, android metadata viewer, and (theoretically) info composer.
Essentially, we are beginning a new era if metadata presentation.
Andruif
On Friday, February 8, 2013, quyin wrote:
so for clients that do not support showing images:
- if they do not change, the image will be shown as an ordinary composite that contains fields such as image location, referrer location, title and creation date.
- the application can choose to hide the image by explicitly matching the field type with "image".
- the application can possible show the image by using that location.
is that right?
it seems pretty acceptable to me.
Best Regards, Yin Qu (屈垠)
On Thu, Feb 7, 2013 at 5:41 PM, Andrew Webb <notifications@github.com<javascript:_e({}, 'cvml', 'notifications@github.com');>>wrote:
currently, a majority, if not all, composite fields of type="image" have hide="true" in meta-metadata. i think this is wrong, or at least problematic for our new metadata visualizations. i would like to remove hide="true" on all image fields. it should be an application's metadata visualization that decides whether or not to the show an image field and how to represent it (you may still want to show a link).
is this acceptable? it will require changes in existing metadata visualizations that do support showing images. if we agree, i will begin making the changes.
— Reply to this email directly or view it on GitHub< https://github.com/ecologylab/BigSemanticsWrapperRepository/issues/2>.
— Reply to this email directly or view it on GitHubhttps://github.com/ecologylab/BigSemanticsWrapperRepository/issues/2#issuecomment-13276634.
andruid kerne, ph.d. director, interface ecology lab associate professor, department of computer science and engineering texas a&m university 979.862.3684 fax college station, tx 77843-3112 http://ecologylab.net
http://facebook.com/ecologylab
Interfaces are the multidimensional border zones through which the interdependent relationships of people, activities, codes, components, and systems are constituted. Interface ecology investigates the dynamic interactions of media, cultures, and disciplines that flow through interfaces.
currently, a majority, if not all, composite fields of type="image" have hide="true" in meta-metadata. i think this is wrong, or at least problematic for our new metadata visualizations. i would like to remove hide="true" on all image fields. it should be an application's metadata visualization that decides whether or not to the show an image field and how to represent it (you may still want to show a link).
is this acceptable? it will require changes in existing metadata visualizations that do support showing images. if we agree, i will begin making the changes.