#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.
#tantekmisa__: welcome, and yes that's a summary result from the W3C HTML Working Group discussions on microdata
#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...
#tantekmisa__: it's up to date. there has been no further work on microdata at W3C so it's still just as dead/dropped from a W3C standards perspective
#tantekpeople work on all kinds of things outside W3C
#tantekwhich is fine too, it just means those things are not W3C standards
#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?
#tantekmisa__: schema.org is a Google run effort, with some contributions from Microsoft and Yandex. It's not an open standard.
#tantekI sympathize with the sense of being overwhelmed
#tantekhence why a lot of us have worked on simplifying things with microformats2
KartikPrabhu joined the channel
#misa__so as far as indieweb is concerned this is not something i should care about?
#tantekcorrect, it's been pretty much completely ignored
#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
#KartikPrabhumisa__: you should decide what to use depending on what you'd like to use if for
#KartikPrabhuSchema.org has not been very useful for indieweb things mainly due to its complexity of parsing and publishing
#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...
#tantekmisa__: microdata is ignorable for indieweb. no one is actively using it.
#KartikPrabhumisa__: I would suggest starting with microformats as they are the simplest ones to publish
#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
#tantekmisa__: glad to hear indieweb seems very right for you! come on by to #indiewebcamp and say hello to discuss indieweb concepts :)
#KartikPrabhuschema.org is so horribly over-thought that it is ignorable too
#ben_thatmustbemeso if you had just an embedded object, would it also be just in "refs"
#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
#aaronpki'm only interested in that h-card if it has explicit meaning that I can consume
#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
#ben_thatmustbemeaaronpk: it looks like you are doing [] specifically for some values but not for others
#aaronpkactually tantek.com is a great example. There's an h-card as the last child object of the top-level Tantek h-card
#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")
#aaronpkI have no idea what that means, so it's not going to show up in the XRay output
#aaronpkI didn't say author centric, I said author-level
#tantekbut you're not doing author-level either, you're doing consuming-level
#aaronpkwhat was your intention of marking up that Rebecca Daniels h-card?
#tantekas a publisher, it makes sense to markup all your content that's meaningful with established microformats
#ben_thatmustbemecan we get back on to the point we were discussing?
#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
#aaronpkben_thatmustbeme: yeah that's kind of what I'm thinking
#tantekben_thatmustbeme: that's how it starts, but as you add more use-cases, you'll likely end up making something very similar
#aaronpkthe problem is when a property can be either an array or a string, then both cases end up needing to code exceptions for
#tanteke.g. every use-case I listed above for random h-cards on a page *IS* social
#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
#tantekaaronpk: precisely why that design decision was made for mf2 json
#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
#tantekso consuming code wouldn't have to do "bunch of checks" (or at least fewer)
#aaronpki'm not saying that's bad, just what it is
#tantekwhich I'm happy to see the alternative being explored
#aaronpkso with the XRay output, I made it vocabulary-aware, so that it's easier to consume when you know what your'e consuming
#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'"
#ben_thatmustbemeso, one of the biggest complaints i keep hearing is the need to check if something is an array, single item, or object
#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
#ben_thatmustbemeshouldn't author: be a single array item then? couldn't you have multi-author posts?
#tantekwhere do you hear these complaints ben_thatmustbeme ?
#ben_thatmustbemejust for comments that don't have a URL, what do you do?
#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
#ben_thatmustbemei don't think thats true, salmention would still work with a comment that doesn't have a url
#aaronpkstick a fragment URL on the inline comment and then it's useful again
#aaronpkben_thatmustbeme: in practice, any consuming code trying to handle something that doesn't have a URL isn't going to end up with good results
#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
#ben_thatmustbemetrying to think of a good argument for shortlink, i feel like it is needed as an authoriative alternate url
#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.