misa__hello channel, just found this line on the microformats wiki: microdata was explicitly dropped by the W3C (and therefore not part of W3C HTML5) due to a lack of interest by anyone to edit the spec and keep it up to date.
misa__I understand that, and just a note here, I am quite unexperienced regarding these concepts so I would appreciate some guidance from more experienced folks, just this seems a bit outdated as microdata blog seems to be quite a busy place...
misa__yes I can see that, just deciding with what to get going is somehow overwhelming, then there is schema.org... could you care to share your thoughts in a brief on that?
tantekthere has been some use of OGP / Twitter Cards as a fallback for some use-cases, but schema is largely ignored for being overly complex and unnecessary
misa__indieweb seems very right for me, I can comprehend most of its concepts, just this whole thing with microdata/microformats and the rest got me overwhelmed...
tantekthere may be a few folks publishing a few microdata things experimentally, but it's never gotten any traction in the peer to peer independent web
aaronpkso rather than if(is object) {...} else if(is url) { ... } it's just always a URL, and if you want you can check if there's extra data about the URL
ben_thatmustbemei like the idea of pulling it all out, almost like the refs: section could be completely ignored since you have to fetch the content anyway
tantek"put an h-card anywhere on the page" - then the h-card likely has different meanings, so it makes sense for it to show up different places in the mf2 JSON
tantekaaronpk - that's not author-centric (as you claimed originally), that's *consuming* centric ("i'm only interested ... if it has explicit meaning that I can consume")
aaronpkthere's no other references to it though, so it has no context. For example if there was some other object on the page with a u-url of rebeccadanielsphoto.com then I might know what it's for
aaronpkin mf2 json everything is an array, so most of the time you're doing [0] to get the first. but when jf2 makes a property a string if there's only one value, then you have to do a bunch of checks
ben_thatmustbemewhat if we just make this one rule aaronpk, as soon as you hit somthing that has a specific URL outside the domain context (non-authoritative content) we move it over to refs. Basically we could do that as the only change to the MF2 JSON and see what we get
aaronpke.g. "this is an h-entry. if there is a published date, it will always be a string. if it's a reply, you can find all the URLs it's in reply to in the array 'in-reply-to'"
aaronpkalso the value of "in-reply-to" will never be an object with this, since if it was an object in the mf2 JSON, that object gets moved down to refs and the URL of the object is the value in the array
aaronpkif there's no URL for a comment (including no fragment URL) then I'm just going to drop it, since nothing will be able to do anything with that comment anyway
aaronpkcombine that with tantek's earlier suggestion of XRay returning the object inside the fragment identifier and then fragment comments act just like comments with their own URL
ben_thatmustbemeall seems to make sense, looks like uid and logo aren't carried over, but those aren't really needed / prefer url over uid and logo is just photo again
aaronpkbtw i'm not sure this is actually the best step for jf2, which is why i've just been building this as an API, but this is how I want to consume pages
gRegorLoveLooks good at a glance, without testing. I think the innerText method should remove the script and style, but I'm not aware of any problems explicitly removing them first, either.