-
Notifications
You must be signed in to change notification settings - Fork 61
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
Erratum for Example 79 to correct width
and height
properties
#630
Open
evanp
wants to merge
1
commit into
main
Choose a base branch
from
example-79-width-height-erratum
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dont believe there is any normative text anywhere in the as2 TR that justifies a conclusion that these properties "are only allowed on Link objects".
I think a more appropriate resolution to the confusion here would be to add
Image
orObject
to https://github.com/w3c/activitystreams/blob/main/vocabulary/index.html#L5531 , as I suggested 5 years ago.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm, I just re-read some stuff and I'm kind of convinced here that maybe the domain of
width
andheight
should beImage | Link
? If you'll indulge the wonkery, I read this sentence from section 4.2 explaining link, and comparing examples 11 and 12:If we read example 80 as a "qualified, indirect" reference to the image (resizing it from a bigger note1.png to 16x16, and resizing note2.png for the 32x32 version), then it makes a lot more sense why width and height would be set there (although the example would support this interpretation more obviously if they were both resizing
note-256-by-256.png
😅 ). This would also explain whyicon
is a distinct property, as opposed to just animage
-- it's a qualified relationship and representational hint (i.e. show the 16x16 or the 32x32 depending on the window size/CSS/etc).Just a theory... will try to make the next issue triage if it's worth discussing further.