2015-11-05 UTC
# 00:00 azaroth Is the desire to have something like: {"value": "<b>foo</b>", "language": "en", "mediaType' # 00:00 azaroth ": "text/html"} ? # 00:00 aaronpk do we have the ability to provide both plaintext and html values for content? # 00:00 aaronpk (where consumers know the two values are different representations of the same content) # 00:01 jasnell the only variations we can provide currently on content are language-tagged # 00:01 jasnell in other words, "content": "foo" == no language tag unless there's a default language context established # 00:01 aaronpk in mf2 whenever the parser encounters HTML, it also converts it to plaintext and provides a plaintext version # 00:02 jasnell "contentMap": { "en": "foo" } == content == "foo"@en # 00:02 aaronpk e.g. an e-content tag results in "content": {"html":"<b>foo</b>","value":"foo"} # 00:02 jasnell there's nothing stopping implementations from doing something similar, but I'd argue that makes a nice extension :-) # 00:03 aaronpk the nice thing is consumers who want to display HTML can sanitize the html tag and render that, or if they don't want to deal with it can just use the plaintext value # 00:03 jasnell {"content": "<p>foo</p>", "plain:content": "foo"}# 00:03 jasnell {"content": "<p>foo</p>", "jf2:content": "foo"} :-)# 00:04 jasnell that would keep the most common cases simple but allow implementers do provide for the alternate case. Not everyone is going to want to put two alternate copies of the content in the object # 00:05 aaronpk yeah, that's the advantage of it happening at the microformats parsing stage. publishers are only providing one version of the content that way # 00:05 aaronpk but that doesn't really exist with activitystreams # 00:06 aaronpk azaroth: wow you ahve to check the first character to know if the content is html? # 00:06 azaroth We couldn't get agreement in that community to always do HTML # 00:07 azaroth And it's not valid to have @value, @type and @language on the same literal # 00:07 azaroth @language has more variation, and more value, so we put in a kludgey processing rule # 00:08 jasnell aaronok: there's nothing stopping an AS2 parser from doing the same thing with content. # 00:09 aaronpk okay did you get those changes for the wording queued up somewhere? I can summarize in that github thread # 00:10 jasnell not yet but I can. basically, the proposal is to: (1) rename displayName to name, (2) drop title, (3) clarify that summary is always html, (4) clarify the relationship between mediaType and content in an object # 00:10 jasnell separately, we need to look at clarifying the definition of published # 00:11 jasnell I'm +0 on 1 but if it helps us move forward and makes implementers happy, then awesome # 00:12 azaroth is +0,+1,+1,+1 too # 00:15 jasnell btw, LINK and UNLINK support has landed in node.js master. woo! # 00:15 azaroth Nice! :) LINK++ # 00:17 jasnell aaronpk: fwiw, I may come off as a stubborn ass at times but I'm always open to be convinced on almost everything. :-) # 00:18 aaronpk i'm also not opposed to being convinced that I am wrong # 00:19 aaronpk it's just good to talk things through and improve documentation, since chances are if I am unclear on something right now, others will also be unclear on it later # 00:19 jasnell yep, and to be honest, I've been staring at these specs for years now, what's obvious and familiar to me based on past discussions and work isn't always obvious to folks coming into it fresh... I often need to be reminded of that tilgovi and kevinmarks joined the channel
# 01:04 kevinmarks azaroth's worry about published dates was dealt with in Atom by source # 01:04 kevinmarks so if you republish something and change things you put in a source with the original values azaroth, bblfish, tantek, kevinmarks and jasnell joined the channel
# 02:43 jasnell kevinmarks: I've rarely ever seen source used in the wild # 02:43 jasnell it had been discussed for AS1 but ruled out because of lack of consistent use # 02:43 jasnell I've toyed with it a few times as an extension but it's really not all that useful in practice # 02:44 jasnell a "via" extension might be useful to explore but not in core # 02:53 kevinmarks via isn't quite the same - in practice that is a 'I found this link on someone else's site and I'm giving credit' Shane_, azaroth, tilgovi, bblfish, Arnaud, jasnell, JonathanC, melvster, tantek, the_frey, ShaneHudson, kevinmarks, elf-pavlik, shevski, timbl, MarkS and daviding joined the channel
the_frey, jasnell, azaroth, melvster, MarkS, bblfish, kevinmarks and ShaneHudson joined the channel
azaroth, azaroth_, tantek and jasnell_ joined the channel
# 22:43 azaroth jasnell_: Am here if you have questions/comments re #249, #250 bblfish joined the channel
# 23:01 azaroth The only question that came up was whether Leave can be the opposite of both Join and Arrive? # 23:02 azaroth Eg can you Leave a Group, and Leave a Location? # 23:02 azaroth (In that you can't Travel or Move yourself without stating a destination) jasnell joined the channel
# 23:17 azaroth hmmm. {actor: azaroth, type: Remove, object: worms, origin: can} timbl joined the channel
jasnell_ joined the channel
azaroth Is the desire to have something like: {"value": "<b>foo</b>", "language": "en", "mediaType'
jasnell nor can you put additional metadata in there... it gets dropped by the json-ld algorithms ... http://tinyurl.com/ohqvloa
kevinmarks azaroth's worry about published dates was dealt with in Atom by source