Comments (6)
Hello @lpoujade,
I am not 100% if we always stick to this convention, but in your title "Image in annotations" the word 'annotations' may need to be capitalized.
This phrase gets a bit circular and what image being mentioned isn't very clear.
we have a simple image body referencing our image, and a text body to provides a caption related to the image
Perhaps something like "we have two separate objects that make up the Annotation body. One object is an image which is the supplementary image and the other is a textual body which acts as a caption for the supplementary image. Both of these objects together target the image from the Canvas."
One more small touch up. This instance of "canvas" should be capitalized.
so we associated the part of the canvas containing the fountain
from trc.
@thehabes's comment reminded me that I had a comment on the recipe title. It's a bit vague - what about changing the title to something like "Annotating a Resource with an Image"?
Also, a few edits for style/grammar:
The first sentence (that vs. which; use of prepositions) - maybe something like: "Provide an image that adds details about or shows a different view of a particular feature/area of the Resource."
The second bullet point: should have a comma between "built" and "So", not a full stop. This will mean a lot of commas/clauses in that sentence, so maybe revise - something like: "To show how the completed building looks, you decide to annotate specific features, such as the patio, with actual photographs."
The third bullet point:
- "his creation" should be "its creation"
- "Sometimes" should be followed by a comma - maybe revise to something like: "In some instances, where the video shows a specific part of the building, you might want to annotate..."
The Implementation notes section, last line: "provides" should edited to "provide"
from trc.
Just a quick remark about the size of the image in the annotation (3024x4032, 9,72 Mo), so not ideal in terms of performance and best practices (given the fact that this image is mostly intended to be displayed in a small box on top of the main image, or in a sidebar)
from trc.
@regisrob you are totally right, I'll change the image for a lighter one !
@thehabes @kirschbombe thank for remarks, as you may have guessed I am not a native english speaker, I will rephrase using your hints 😁
from trc.
Issue 114 (Recipe #317: Image in annotations)
+1: 21 [akrishnan15 cubap danieltbrennan dlpierce eliotjordan glenrobson hadro ioanrichards irv jpadfield jtweed julsraemy kirschbombe markpatton markpbaggett nfreire regisrob robcast thehabes tpendragon triplingual]
0: 0 []
-1: 0 []
Not TRC: 0 []
Ineligible: 0 []
Result: 21 / 21 = 1.00
Super majority is in favor, issue is approved
from trc.
I updated the recipe with all your suggested changes except for:
- @thehabes suggestions where I changed the target from "image from the Canvas" to "Resource" to match with @kirschbombe suggestions : "… Both of these objects together target the Resource"
- I kept the title to "Image in Annotations" because I think it is "as simple as the recipe", like the other recipe "HTML in annotations". Also, reading "Annotating a Resource with an Image" I'm more inclined to think that it is a different annotation mechanism, while "Image in Annotation" seems clearer/straightforward for me. @kirschbombe what do you think ? I'll change the title if you still want to !
from trc.
Related Issues (20)
- Add Wikidata to profiles registry HOT 1
- Add Darwin Core to profiles registry HOT 1
- Georeference Extension HOT 9
- Recipe #0068: A basic newspaper - rewrite HOT 7
- Recipe #0306: Linking external Annotations targeting a Canvas to a Manifest HOT 8
- IIIF Authorization Flow API 2.0 HOT 6
- Recipe #318: Locating an Item in Place and Time HOT 3
- Recipe #261: Annotation with a Non-Rectangular Polygon (update) HOT 4
- Recipe #0135: Annotating a specific point of an image HOT 2
- Proposal for adding 'timed-text' in the Text Granularity Extension HOT 4
- Migration of Selectors from Annex to Registry HOT 1
- Annotation Motivations TSG Charter HOT 2
- Recipe #283: Missing images in a sequence HOT 9
- Re-charter of the Authorization Flow TSG HOT 2
- Recipe #22: Redirecting from one Canvas to another resource (Hotspot linking) HOT 5
- Recipe #32: Simple Collection HOT 3
- Recipe #434: Multiple Choice of Audio Formats in a Single View (Canvas) HOT 8
- Recipe #466: Sharing a link to open a Manifest in a specific viewer. HOT 12
- Recipe #346: Annotating in Multiple Languages HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from trc.