#social 2015-06-22
2015-06-22 UTC
jasnell, bblfish and tilgovi joined the channel
# 
ben_thatmustbeme melvster1: rhiaro: just catching up on your conversation. nothing is wrong with the parsers. Indeed, according to spec the parser would not be responsible for dereferencing a fragment. The user of the parser can certainly look at that after the fact, but the fact is you lose those IDs when you parse, so i don't think it really makes sense.
# ben_thatmustbeme the only possible way to get around that i would see would be to suggest the parsers keep the id values of parsed items
# ben_thatmustbeme perhaps the correct way to do it is that you should be fetching the html, finding that fragment, then passing only that section to the parser, again, its a problem before it gets to the parser.
# 
melvster1 ben_thatmustbeme: sounds good
# ben_thatmustbeme otherwise its like claimning that CURL is in error because it fetches the whole page and not the fragment. it treats multiple URLs the same
# ben_thatmustbeme okay, shower time
# melvster1 curl should fetch the whole page
# melvster1 the parser just looks at the page and gets what it wants
# melvster1 that's generally the way of doing things that ive observed
# ben_thatmustbeme The mf2 parser does not care what url the html came from but implementations filtering to only that fragment before passing to the parser would be good I think. Would solve the whole "subscribe to second feed on a page".
tilgovi, jasnell, jaywink, bblfish, pfefferle, pfefferle_, the_frey and edhelas joined the channel
# 
Loqi Eprodrom made 1 edit to [[Socialwg/2015-06-23]] https://www.w3.org/wiki/index.php?diff=84732&oldid=0
AnnB joined the channel
# AnnB evanpro just published agenda for tomorrow's WG meeting
jasnell_ joined the channel
# AnnB question: will Zakim be used?
pfefferle joined the channel
# AnnB if not, the WebEx info needs to be inserted
# AnnB I'd do it, but don't have that info
# AnnB this might be the last time we can use Zakim for this meeting; not sure
# AnnB in any case, I can't be there, so good luck!
# Loqi Abasset made 1 edit to [[Socialwg/2015-06-23]] https://www.w3.org/wiki/index.php?diff=84743&oldid=84732
# melvster1 FYI: http://www.w3.org/TR/2015/NOTE-contacts-manager-api-20150602/
# Loqi Aaronpk made 1 edit to [[Socialwg/2015-06-23]] https://www.w3.org/wiki/index.php?diff=84744&oldid=84743
# AnnB interesting link, melvster1!
# AnnB seems like we should coordinate with those guys
# AnnB a "Note", in the W3C world, is essentially someone documenting an idea
# AnnB they're putting it in the record, but it's not a standard recommendation or anything
# melvster1 AnnB: sort of it's one below a REC, but for various reasons it doesnt become a REC, sometimes it's just politics, but normally they are technically sound, some Notes are better than RECS!
# AnnB yes on all that; was just trying to clarify for those who might not know
# AnnB in any case, thanks for highlighting that one
# AnnB seems directly relevant
# melvster1 AnnB: ah ok, great ... this group may produce some Notes too
# AnnB do you know those guys or anything about it?
# melvster1 no, just heard of it today
# AnnB we, in Boeing, are very keen on establishing foundational standards for how profile info is defined
# AnnB which is similar to contacts, but not quite the same
# AnnB we have many products coming in which have a 'profile' capability .. we want to have one master profile source, and then federate from that
# melvster1 AnnB: can you say any more? id recommend : http://www.w3.org/2005/Incubator/webid/spec/identity/
AnnB_ joined the channel
# AnnB_ dang; got dropped
# AnnB_ melvster1, last I heard, our security people use SAML for most things; are looking at OpenID Connect for mobile; and have not evaluated WebID
# Loqi Rhiaro made 1 edit to [[Socialwg/2015-06-23]] https://www.w3.org/wiki/index.php?diff=84745&oldid=84744
# melvster1 AnnB_: webid is more about profiles, it's authentication agnostic
# AnnB_ hmm .. guess we need to learn more
tilgovi joined the channel
# AnnB_ thanks for that distinction
# melvster1 essentially recommends using HTTP profiles with machine readable linked data
# AnnB_ cool
# AnnB_ I'll point this out to AdamB
# melvster1 you might think such a thing is self evident, but you'd be surprised how few people do that, facebook are the main adopter so far
# AnnB_ (who runs the internal social network, which is our profile repository)
# ben_thatmustbeme we said last week that it would be our last time on Zakim, and we are on webex this week
# AnnB_ hmm, that's interesting
# ben_thatmustbeme to answer question from earlier
# AnnB_ that's kind of what I remembered, Ben ... but I don't think we have the WebEx info yet
# melvster1 AnnB_: actually people didnt want to write a spec for it, because it was felt to be "obvious" ... however when looking at the different systems out there, differences in profiles and lack of standardization there, seems to be one of the biggest causes of non interoperability
# melvster1 personally, I think consensus on how to do profiles would be as useful, if not more useful, than a social api, because that's what everything gets built on, and it shows implementers how to work together, which we dont seem to have yet
the_frey and the_frey_ joined the channel
# AnnB_ melvster1, that's one of our big hopes from social WG, is that we'll standardize the profile bits
# melvster1 AnnB_: oh great! that was my hope too, but I didnt see it in the charter, so I was slightly concerned as to whether it would be foscused on
# AnnB_ well, just cuz I say that's our hope .. doesn't mean it'll happen
# AnnB_ nor that it's in the charter
# melvster1 AnnB_: ah ok, got it ... is my hope too!
# AnnB_ seems like it's been hard to get traction on this idea
# AnnB_ maybe the more basic API needs to happen first?
# melvster1 AnnB_: my feeling was that the API would be easier to spec out and implement, if profiles were understood, rather than, the other way round ... I guess we'll find out ...
# AnnB_ hmm .. I'm not a developer, so don't have an opinion yay or nay
# melvster1 AnnB_: well all I can say is that with SoLiD we felt profiles were important enough to document and make into its own spec, so I hope it will be relatively easy to interoperate with SoLiD as we didnt create anything new just followed W3C RECS and linked data
# AnnB_ cool
the_frey joined the channel
# AnnB_ yay, rhiaro!
# AnnB_ Loqi's little comments always make me smile
# AnnB_ I'm eager for suggestions on what should be on the IG agenda for Wednesday
KevinMarks and edhelas joined the channel
# AnnB_ draft for IG agenda: https://www.w3.org/wiki/Socialig/2015-06-24
# ben_thatmustbeme hello cwebber2
AnnB joined the channel
# AnnB I saw your regrets, rhiaro; thanks .. darn!
# ben_thatmustbeme melvster1: confirmed that mf2 parsing algo only talks about parsing "a document" never says where you get it from. so really its parser libs that decided to include curl but never included frament lookup thats really to blame for indieweb ignoring fragments
# ben_thatmustbeme s/frament/fragment
# Loqi Hhalpin made 2 edits to [[Socialwg/2015-06-16]] https://www.w3.org/wiki/index.php?diff=84751&oldid=84666
# ben_thatmustbeme wrong week harry :/
# melvster1 ben_thatmustbeme: thanks for the explanation!
# ben_thatmustbeme AnnB: actually we are moving to a 9 digit phone number system. didn't you get that memo? :P
# AnnB hehe
# Loqi Benthatmustbeme made 1 edit to [[Socialwg/2015-06-23]] https://www.w3.org/wiki/index.php?diff=84752&oldid=84745
# AnnB one never knows with phones these days
# ben_thatmustbeme very curious on what IG says about future of IG
# ben_thatmustbeme what people are motivated to work on
jasnell joined the channel
# AnnB eager for ideas, ben_thatmustbeme, if you have suggestions
# Loqi Hhalpin made 1 edit to [[Socialwg/2015-06-23]] https://www.w3.org/wiki/index.php?diff=84753&oldid=84752
# ben_thatmustbeme it certainly depends on what people are interested in
jasnell joined the channel