jalcine
commented
2 years ago I have a particular use-case for this that I'd outline below:
- Each page on my site points to my h-card from the header. That's marked up with
rel="me author"and as a.h-card.u-uid.u-url. It has a photo and my nickname that I'd prefer to use. Ideally, this is what people can use if they don't do deep author parsing. - The aforementioned link points to my about page that has more information like my birthday, current time zone, a complete breakdown of my name and other bits of information (like rel-me links).
- On that about page, there's (going to be) a link to my contact page, which would have my IM information and other means of reaching me faster-than-replying-to-a-post.
My hope is to have a way that, from my embedded h-card in the header, be able to resolve all of this information using markup (be it something like rel=contact or some sort of system).
I have considered using something like rel=next to hint at 'more' information, but I'd have to figure out how to build pagination between these pages and that doesn't seem correct to me.
(Originally published at: https://jacky.wtf/2022/3/KI/KIwzHTO3Tl3oefYxGbalz5W7)
One possible solution for the partial plus complete h-card issue is to include a link to the full h-card and not mark up the partial profile information on the home page as an h-card. The representative-hcard-parsing algorithm would then follow the link and use its full data. It doesn't seem ideal, but it'd work.
If you did this using the rel-me markup, the home page usually has many rel-me links and we don't yet have a way to denote the "canonical" one.
u-uid and/or a new rel-canonical property could be used for this.
See https://indieweb.org/h-card#Brainstorming