Skip to content

Conversation

@s-adamantine
Copy link
Contributor

A couple of thoughts that might warrant discussion

  1. I added an optional coverPhoto field, we might want to normalize the size/aspect ratio of this. Or maybe this is not even required?
  2. This is the first lexicon that has the key: tid. I think it could make sense here - might make eg sorting by recently created easier

@s-adamantine s-adamantine changed the title Draft hypercert collection Hypercert Collection Lexicon Nov 4, 2025
@holkexyz
Copy link
Member

holkexyz commented Nov 4, 2025

For a hyperboard we would need only a single additional piece of information, which is the weight for each hypercert in the collection. For instance, if a hyperboard for an event includes a hypercert that represent a 5min lightening talk and another that represents a 3h workshop, we might want to weight the latter more in the hyperboard resulting in it having more space.

We could either create another schema for a hyperboard or just include this additional information as optional here. Then a hyperboard would be just a visualization of a collection. This is how it is in v0.1. And I think I'm in favor of that.

@aspiers
Copy link
Contributor

aspiers commented Nov 19, 2025

A couple of thoughts that might warrant discussion

  1. I added an optional coverPhoto field, we might want to normalize the size/aspect ratio of this. Or maybe this is not even required?

@bitbeckers made the point that there is a risk of this becoming a slippery slope towards a schema which includes a lot of data dictating visual rendering, rather than just tracking membership.

I think it's a valid concern, although I'm not sure it's a very slippery slope as long as we're clear up front that this is not a schema for frontend visuals. With that lense, it sounds reasonable to me as an optional field; and maybe we could recommend an aspect ratio too, but I don't have a strong opinion on any of this yet. @bitbeckers Can you chime in here, or perhaps better file an issue if you think we need to work on this further?

  1. This is the first lexicon that has the key: tid. I think it could make sense here - might make eg sorting by recently created easier

I see tid in the evaluation and measurement lexicons already, but yeah I think tid is a sensible choice.

@aspiers aspiers merged commit 713e871 into main Nov 19, 2025
@aspiers aspiers deleted the hypercert-collection-lexicon branch November 19, 2025 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants