#social 2015-10-13

2015-10-13 UTC
eprodrom joined the channel
#
eprodrom
cwebber2: you around?
#
eprodrom
I started writing a test driver here
jasnell joined the channel
#
eprodrom
I just threw in some basic tests from the very first example
#
eprodrom
There's a dummy consumer which basically fakes its way through
#
cwebber2
hi eprodrom
#
cwebber2
eprodrom: oh
#
cwebber2
well eprodrom quit :P
#
cwebber2
I understand now what he meant, I didn't before
Arnaud, tilgovi and jasnell joined the channel
jasnell, tilgovi, bblfish, the_frey and elf-pavlik joined the channel
jasnell, jasnell_ and bblfish joined the channel
#
rhiaro_
Morning all. I sketched out a kind of outline of how I see things could be divided up in terms of smaller parts that can be implemented individually, and started fitting the input specs into this outline: http://rhiaro.github.io/Social-APIs-Brainstorming/socialapi
#
rhiaro_
I added it to the agenda for today, but don't have much to say on it. Only that this is a potential route towards a unified standard document (or set of documents) based on the specs and implementations we currently have
#
cwebber2
rhiaro: \o/
#
cwebber2
unrelated, joining the credentials wg call today to see the demos of what they're doing there
#
cwebber2
it might be useful to this group, trying to get a sense of overlap
melvster1 joined the channel
#
cwebber2
wow there's cool things going on here re: credentials group
#
melvster1
cwebber2: yeah the credentials group is pretty awesome
#
cwebber2
melvster1: yeh I'm watching their demo now
#
melvster1
anyone else had problems getting webex to work on linux?
#
melvster1
cwebber2: which one?
#
cwebber2
melvster1: it's going over the payment-centric demo, but showing off login and etc
#
cwebber2
I'm really interested in the "did:" stuff they're talking about
#
melvster1
cwebber2: got a link?
#
cwebber2
melvster1: and /join #credentials on freenode
#
cwebber2
call is nearing over. if you're at TPAC, they'll show it there too
#
cwebber2
but this is looking *really* promising.
#
melvster1
nice!
#
cwebber2
melvster1: btw haven't fetched my mail yet in the last hour, but did you see my reply to you today?
#
melvster1
yes, it's good stuff, ive been following that work for a few years, and it's maturing now
#
melvster1
i think so yes
#
melvster1
cwebber2: cool demo! it's improved since I saw it last ...
#
cwebber2
melvster1: are you following their "decentralized identity" "did:" scheme stuff
#
cwebber2
because that realllllly interests me
#
cwebber2
DHT over https, yes please
#
melvster1
cwebber2: yes, we had quite a long thread with dave longely about it ... the motivation is portability, I personally prefer http: uris but it's all good
#
melvster1
the challenge with new URI schemes is popularizing them, that's just one more fire to fight for me, but if someone else does that, or there's a use case, I'd be happy to reuse it, otherwise http handles everything I need right now
#
melvster1
cwebber2: glad you like the demo, there was some pushback against the credentials work
#
melvster1
is there any way I can test webex before the call starts?
#
aaronpk
you know you don't have to use the webex client right? there's a phone number you can call as well.
#
cwebber2
as long as you're in the US, yeah :)
#
cwebber2
I just dial in.
#
melvster1
aaronpk: I tried it a couple of times before but got a weird java error, ive dialed in with skype instead as an alternative, but would like to see if I can get webex going on linux ...
eprodrom joined the channel
#
eprodrom
jasnell: when you get a chance I'd love your thoughts on the testing framework
#
melvster1
but it wont let me test further, im not sure which java it wants me to install
#
aaronpk
you can also call the phone number from within Gmail or google hangouts
#
melvster1
aaronpk: oh thanks, but only from the US, right? I think I just need to maybe install oracle java8 or something
#
aaronpk
no like seriously, just open up gmail and dial the number
#
aaronpk
it's the internet, it doesn't care where you are
#
melvster1
wow, great
#
melvster1
i normally do that from skype, but have to pay :)
#
rhiaro_
melvster1: google voice/hangouts works fine for me, for free, from not-US
#
aaronpk
that was one of the nice things about google buying GrandCentral
#
melvster1
ah cool, thx
#
melvster1
btw working on a little app market for SoLiD : https://files.gitter.im/melvincarvalho/Fjyx/appscreen.png
tantek and hhalpin joined the channel
#
hhalpin
meeting is in 40 minutes I think
#
jasnell
eprodrom: saw your note, hopefully will have a chance to look today
#
hhalpin
If anyone is in London or nearby, there will be a great discussion at http://redecentralize.org/conference/
#
hhalpin
this coming weekend
#
hhalpin
eprodrom: Ever catch up with John Cowie from Thoughtworks?
#
eprodrom
hhalpin: yes
#
hhalpin
did you think he was acceptable as an IE?
#
hhalpin
If so, ping me (via email is fine) and I'll enable his account.
#
cwebber2
o/ tantek, I left a message for you with Loqi
#
melvster1
java8 installed, maybe webex will work now. 'Hangouts needs the Google Talk plug-in to make calls. Install the Google Talk plug-in'
#
rhiaro_
melvster1: that takes like 2 seconds
#
melvster1
rhiaro_: I have it on chrome, not on firefox, less worried about the time, more about what the proprietary s/w does to my machine
#
melvster1
I tend to use firefox for my email, because of speed (lack thereof)
#
rhiaro_
I couldn't get WebEx to work on any of my devices
#
rhiaro_
Including Android phone
#
aaronpk
you really should be more concerned with installing java on your machine than installing the google talk plugin, given that there are actual exploits in the wild for java
#
melvster1
aaronpk: yes, agree ... I'd rather not install anything
#
cwebber2
especially a java application which provides all the right tools to be a trojan horse
#
melvster1
totally
#
melvster1
but figured getting webex working would be a good thing
#
cwebber2
I think it was mentioned last call that there would be international numbers provided
#
cwebber2
did that happen btw
#
hhalpin
Again, W3C is happy for us to use Mumble
#
hhalpin
we just need to do a call for consensus in the WG
#
hhalpin
add it to the agenda?
#
aaronpk
this is gonna be a long call
#
ben_thatmustbeme
melvster1: you have been on 1 call before haven't you?
#
ben_thatmustbeme
how did you get on that time?
#
ben_thatmustbeme
i would be fine switching to mummble but would -1 it until we at least try it first
#
cwebber2
sure, doing a test call would be fine
#
aaronpk
a subset of the group could try a trial call later today or later this week
#
melvster1
ben_thatmustbeme: normally use skype, I think I was on about 100 calls that way in the XG
#
ben_thatmustbeme
no, i meant i thought you were on a socialwg call once already
#
ben_thatmustbeme
i might be mistaken
#
melvster1
yes, skype
#
melvster1
skype lets you dial in if you have credit, which I Do
#
ben_thatmustbeme
yeah, you shouldn't have to pay though
#
hhalpin
added mumble option to our discussion
akuckartz joined the channel
#
tantek
hey cwebber2
#
tantek
catching up
#
Loqi
tantek: cwebber2 left you a message on 10/12 at 10:27am: Hey, you may wish to read this thread before the next meeting starts http://lists.w3.org/Archives/Public/public-socialweb/2015Oct/0013.html http://socialwg.indiewebcamp.com/irc/social/2015-10-12/line/1444670847917
#
ben_thatmustbeme
looks at his watch
#
jasnell
will be a few minutes late to the call
#
hhalpin
present+ hhalpin
#
hhalpin
trackbot, start meeting
#
trackbot
is preparing a teleconference.
RRSAgent joined the channel
#
trackbot
RRSAgent, make logs public
#
RRSAgent
I have made the request, trackbot
#
trackbot
Zakim, this will be SOCL
#
Zakim
I do not see a conference matching that name scheduled within the next hour, trackbot
#
aaronpk
present+ aaronpk
#
trackbot
Meeting: Social Web Working Group Teleconference
#
trackbot
Date: 13 October 2015
#
hhalpin
present+ hhalpin
#
tantek
present+ tantek
#
eprodrom
present+ eprodrom
#
eprodrom
o/ hhalpin
#
ben_thatmustbeme
present+ ben_thatmustbeme
bblfish joined the channel
#
eprodrom
any scribes?
#
cwebber2
present+ cwebber
csarven joined the channel
#
kevinmarks
present+ kevinmarks
#
tantek
cwebber2 seems like a reasonable email. Only thing I may take issue is the implied "war" - as there have been a bunch of us working very hard for many years to both get lots of interop, and to take lessons learned from various approaches and iterate / integrate accordingly.
#
csarven
present+ csarven
#
eprodrom
jasnell: are you on your way?
#
eprodrom
Arnaud: joined?
#
rhiaro_
present+ rhiaro
#
wilkie
present+ wilkie
#
jasnell
will be there in a couple
#
hhalpin
My feeling is that the RDF and microformat discussion has been quite predominant, and would be good to simply call it a truce and go back to JSON for interop.
#
ben_thatmustbeme
we are up to 12 on the call
#
hhalpin
And if folks want to treat like that JSON(LD) that's good, but let's not get religious about it.
#
ben_thatmustbeme
Arnaud is on
#
ben_thatmustbeme
at least his name is there
#
tantek
cwebber2 we're not "done" by any measure, but I think we made a lot of progress, both in terms of approaches (e.g. simplifying RDFa to just use property instead of property & rel), and in terms of extensibility (e.g. microformats2 separation of syntax and vocabularies, and specification for how vendors can do extensions or experiments like in CSS)
#
hhalpin
As pragmatically, most developers will likely treat it as JSON
#
Arnaud
looking at the spinning "connecting..." again
#
Arnaud
present+ Arnaud
#
hhalpin
notes I've added moving to Mumble to the agenda
#
tantek
cwebber2 bottom line - I dislike the "war" characterization because many of us with different approaches have been spent a lot of time working hard on interop and areas of agreement.
#
Arnaud
go ahead
#
eprodrom
scribe?
#
ben_thatmustbeme
\me Arnaud, i did hear you for a moment there
#
rhiaro_
scribed last week, but if nobody else wants to..
#
eprodrom
Zakim, who's on the call?
#
Zakim
Present: Arnaud, csarven, rhiaro, aaronpk, shanehudson, sandro, elf-pavlik, kevinmarks, wilkie, eprodrom, jasnell, ben_thatmustbeme, cwebber, tantek, hhalpin
#
jasnell
present+ james
#
hhalpin
Happy to scribe
#
hhalpin
scribe: hhalpin
#
tsyesika
present+ tsyesika
#
wseltzer
present+ wseltzer
#
hhalpin
topic: Approval of minutes from last week
#
hhalpin
+1
#
tantek
quickly skims the minutes
#
eprodrom
+1
#
tantek
looks fine. +1
#
hhalpin
APPROVED: Minutes of 10-6-2015 approved
#
hhalpin
topic: Discussion of F2F
#
hhalpin
eprodrom: Our agenda is developing nicely
#
hhalpin
... good number of people attending
#
akuckartz
present+ akuckartz
#
eprodrom
q?
#
Zakim
sees no one on the speaker queue
#
cwebber2
marks himself as attending
#
cwebber2
I need to find crashspace, thoug.
#
hhalpin
... do we have space?
#
hhalpin
tantek: I can confirm space for up to 12 without difficulty
#
hhalpin
... by end of month, if we need space for more than 12 we're fine
#
hhalpin
... right now, we have 6
#
Arnaud
we're still missing a lot of names on the wiki
#
cwebber2
I just added myself :)
#
hhalpin
I'll ask for W3C if they will support travel.
#
Arnaud
please, put your name, in one of the categories!
#
hhalpin
tantek: Please add yourself as a 'maybe'
#
hhalpin
... with whatever caveats you want to add
#
hhalpin
... so I can gauge scope and size of room needed
#
hhalpin
... also add yourself to regrets if you can't come
#
ben_thatmustbeme
as long as we actually get to it
#
hhalpin
jasnell, are you on the call yet?
#
hhalpin
otherwise, we can do Social API first
#
hhalpin
topic: AS 2.0
#
hhalpin
jasnell: The new version was published on Tuesday with license change
#
tantek
jasnell++ for publishing new AS2 docs with new license!
#
hhalpin
eprodrom: awesome
#
Loqi
jasnell has 31 karma
#
hhalpin
... what's next?
#
tantek
akuckartz, at the usual /TR I presume
#
hhalpin
... if there's any other changes
#
hhalpin
q+
#
Zakim
sees hhalpin on the speaker queue
#
eprodrom
ack hhalpin
#
Zakim
sees no one on the speaker queue
#
hhalpin
Should we go for wider review before we push for CR?
#
hhalpin
Should we do this wider push before or after F2F?
#
Arnaud
the process requires us to have broad review before going to CR
#
Arnaud
it's the "virtual Last Call"
#
hhalpin
Indeed, noting Kevin Mark's email, looking at existing AS1.0 users
#
hhalpin
eprodrom: I've reached out to SugarCRM, etc.
#
hhalpin
... its not so much about going to Candidate or about deciding if we go to Candidate
#
hhalpin
... and that internal decision will be based on f2f
#
ben_thatmustbeme
q+ Just a point of clarity regarding CR
#
Zakim
ben_thatmustbeme, you typed too many words without commas; I suspect you forgot to start with 'to ...'
#
hhalpin
I've started some outreach to thoughtworks etc.
#
hhalpin
but will aim for me, let's remember we have a deadline re outreach
#
tantek
ben_thatmustbeme try "q+ to say that ..."
#
ben_thatmustbeme
q+ to Just a point of clarity regarding CR
#
Zakim
sees ben_thatmustbeme on the speaker queue
#
eprodrom
ack ben_thatmustbeme
#
Zakim
ben_thatmustbeme, you wanted to Just a point of clarity regarding CR
#
Zakim
sees no one on the speaker queue
#
hhalpin
ben: Don't we need wide review before hitting Last Call?
#
hhalpin
Arnaud: Yes, even though there is no "last call" step anymore
#
hhalpin
... but you need to do it before CR
#
hhalpin
eprodrom: Do we commit to that process or decide at our F2F?
#
hhalpin
... my guess is we commit at F2F
#
hhalpin
sandro: That decision is largely based on the amount of review beforehand
#
Zakim
hhalpin, you typed too many words without commas; I suspect you forgot to start with 'to ...'
#
hhalpin
eprodrom: I want a number or orgs to basically agree we will be implement
#
hhalpin
Notes that maybe people doing outreach should put their names in the wiki after the group
#
eprodrom
hhalpin: still scribing?
#
hhalpin
yes, but trying to catch the voice
#
hhalpin
who is speaking?
#
wilkie
cwebber2
#
hhalpin
cwebber2: I discussed with Evan how to implement AS2.0 and we've started a repo for test
#
hhalpin
... now after some misstarts I'm working on a validator in addition to test-suite
#
hhalpin
... things are moving forward
#
hhalpin
eprodrom: We have at least a framework for a test-suite
#
hhalpin
... testing the data format
#
hhalpin
... requests for producing and consuming AS2.0
#
hhalpin
... wrapper for AS2.0 implementation
#
hhalpin
... would like jasnell's review in particular, but want
#
hhalpin
... additional review and a wrapper for java version
#
hhalpin
... need to talk to TW around their implementation
#
hhalpin
jasnell: The java version is out of date due to lack of time
#
hhalpin
I think TW has some cycles for this, will be seeing them Firday
#
hhalpin
eprodrom: we can then do hackathons and libraries in multiple languages
#
hhalpin
... right now, we have node.js
#
hhalpin
... need python and an out of date java
#
hhalpin
... a hackathon before the f2f would be great
#
hhalpin
jasnell: I'll look at it soon
#
hhalpin
eprodrom: multiple types on objects etc.
#
hhalpin
... any github/tracker updates?
#
eprodrom
q?
#
Zakim
sees no one on the speaker queue
#
hhalpin
jasnell: Number of issues, 8 remaining issues on github tracker
#
hhalpin
... stuff we need some resolution on, please take a look and weigh in
#
hhalpin
eprodrom: Some are fine-grained
#
hhalpin
... a few interesting
#
hhalpin
... the media/type MIME argument
#
hhalpin
... can we do Editor's Choice and WG decision
#
hhalpin
q+
#
Zakim
sees hhalpin on the speaker queue
#
hhalpin
jasnell: lack of @id in examples, MIME type needs WG decision, etc.
#
hhalpin
... the rest is more 'something that we need or not'
#
hhalpin
... want comments on 208, 205, 175, and 152
#
hhalpin
jasnell: 152 and 205 may need WG discussion
#
hhalpin
... 175 or 157
#
akuckartz
Issue 52 needs input!
#
trackbot
doesn't understand that ISSUE command.
#
eprodrom
ack hhalpin
#
Zakim
sees no one on the speaker queue
#
cwebber2
btw I put an item under social api for this week's agenda, but accidentally put it on last week's agenda because I added it to the latest one
#
hhalpin
Process point - close them by f2f, so have editor state his proposal or 'don't care', and then try to get consensus on each editor proposal
#
hhalpin
if not, list options and do straw polls
#
hhalpin
topic: Social API
#
hhalpin
rhiaro: Map what currently exists to what implementations we have
#
cwebber2
and the latest one wasn't this week's meeting up yet ;\
#
Zakim
sees cwebber on the speaker queue
#
hhalpin
... think its a useful way to move forward
#
hhalpin
eprodrom: Let's get review this week
#
eprodrom
ack cwebber2
#
Zakim
sees cwebber on the speaker queue
#
hhalpin
it would be good to get a FPWD after our F2F if we have consensus
#
eprodrom
ack cwebber
#
Zakim
sees no one on the speaker queue
#
hhalpin
cwebber2: I did write an email to the call
#
hhalpin
... I was interested in whether or not AS2 should be mandatory or not
#
hhalpin
... we should address this
#
hhalpin
... two compoenents:
#
hhalpin
... 1) One difficulty has been a cycle of conversation between microformats vs Linked Data for the last 15 years
#
melvster1
linked data didnt exist 15 years ago
#
hhalpin
... probably not helpful to continue to have those discussions in the WG
#
hhalpin
I believe it was just RDF
#
Loqi
melvster1 has 3 karma
#
hhalpin
there has been an ongoing argument betwen RDF and microformats obviously.
#
kevinmarks
microformats din't either; 12 years maybe
#
ben_thatmustbeme
can we get back to the agenda?
#
hhalpin
... we should specify a deliverable
#
tantek
yes KevinMarks 12 years if you count XFN in 2003
#
hhalpin
... at last call we were worried that there would be no deliverables for client-server API, federation, etc.
#
hhalpin
... so I think we need to agree whether or not AS2 should be mandatory to implement
#
hhalpin
... then we can finally move on the API
#
hhalpin
... but without that level of agreement we are having trouble moving forward
#
Zakim
sees kevinmarks on the speaker queue
#
hhalpin
eprodrom: What the resolution would look like?
#
hhalpin
cwebber2: To agree we implement to AS2.0 for whatever is sent to endpoint-to-endpoint
#
hhalpin
... then we can move forward for other things we are stuck on
#
hhalpin
q+ kevinmarks
#
Zakim
sees kevinmarks on the speaker queue
#
hhalpin
q+
#
Zakim
sees kevinmarks, hhalpin on the speaker queue
#
hhalpin
... tantek has figured how to map microformats to RDF's type system
#
hhalpin
... that seems like a good proposal
#
tantek
present+ tantek
#
hhalpin
... then we can figure out whether or not we can move forward
#
eprodrom
PROPOSAL: require AS2.0 for Social API and Federation Protocol
#
hhalpin
cwebber2: It's not other things are not possible, but one is mandatory
#
hhalpin
+1
#
eprodrom
+1
#
melvster1
+0 need to see what AS2.0 is first (mime type will affect existing tooling)
#
eprodrom
ack kevinmarks
#
Zakim
sees hhalpin on the speaker queue
#
hhalpin
eprodrom: An interesting point about where dynamic is
#
tantek
+0 I'd like to improve AS2 more before making it mandatory for anything
#
wilkie
practically speaking, a good implementation will have both AS2 and render with microformats. it is practical to have one required though.
#
hhalpin
kevinmarks: The fundamental disagreement is are we trying to legislate or are we trying to document
#
aaronpk
kevinmarks++
#
rhiaro_
-1. AS2 could be SHOULD but not MUST
#
Loqi
kevinmarks has 173 karma
#
hhalpin
... what's actually working in the wild
#
hhalpin
... the point is that the microformat effort has succeeded
#
eprodrom
ack hhalpin
#
Zakim
sees no one on the speaker queue
#
wilkie
well, we could have servers negotiate... do they serve AS2 or just tagged html and then servers will then automatically be required to do both by not requiring one
#
wilkie
it's a fun fact of distributed system design
#
kevinmarks
microformats have a consistent JSON format for all those languages now
#
tantek
we do have JSON explicit in our charter for Social Syntax - just pointing that out in the hopes that we at least don't have to debate that?
#
ben_thatmustbeme
JSON is suggested in the charter
#
csarven
Charter says JSON, and possible JSON-LD as a convention.
#
melvster1
"most people will drop the @context" -- why?
#
aaronpk
because it's not actuall necessary to get stuff done
#
wilkie
melvster1: because it will probably work without it, and people do that stuff all the time
#
ben_thatmustbeme
csarven: i stand corrected
#
eprodrom
q?
#
Zakim
sees no one on the speaker queue
#
hhalpin
As the author of the charter, JSON is a requirement
#
hhalpin
JSON-LD was optional
#
hhalpin
Sorry guys, but that seemed a rather obvious compromise to me
#
hhalpin
Particularly in terms of developer community size
#
hhalpin
most modern developers send JSON via HTTP APIs
#
ben_thatmustbeme
no, thats a fine compramise to me
#
hhalpin
See Go, Ruby, Django, etc.
#
kevinmarks
documenting is moving things forward
#
ben_thatmustbeme
i was just being specific about it
#
ben_thatmustbeme
i'm fine with JSON
#
kevinmarks
mandating things that no-one implements isn't
#
csarven
hhalpin Makes perfect sense to me; if JSON, a "convention" needs to be picked, and so JSON-LD is a good candidate.
#
hhalpin
So, we just need good mappings from mf2 (needs more work but possible) and RDF (JSON-LD solves this, but RDF folks need to stop being so pushy over fine details that most JSON devs don't care about)
#
Loqi
hhalpin has 8 karma
#
cwebber2
why have we put all this time into AS2 if it isn't good enough of a structure? :\
#
tantek
eprodrom: if we are not comfortable requiring JSON as in the charter, we need to figure out alternative, if we are not comfortable requiring AS2, we need to figure out an alternative
#
wilkie
hhalpin++
#
Loqi
hhalpin has 9 karma
#
tantek
eprodrom: if we can't agree with the charter says, we need to come up with alternatives
#
tantek
eprodrom: I'm looking for some guidance
#
hhalpin
eprodrom: I'm looking for some guidance
#
eprodrom
q?
#
Zakim
sees no one on the speaker queue
#
hhalpin
sorry, had to stop scribing for a sec to catch up with my own thought
#
hhalpin
eprodrom: I see a lot of -1s.
#
hhalpin
eprodrom: Let's try to resolve this and get a proposal we can accept.
#
hhalpin
I'm happy to flesh out my proposal over the next week or two in terms of RDF/mf2 interop
#
cwebber2
it's fine, I realize it was kind of a bombshell :P
#
akuckartz
eprodrom++
#
Loqi
eprodrom has 27 karma
#
hhalpin
That being said, as a reality check, 99% of web devs use JSON, not mf or RDF
#
eprodrom
PROPOSAL: accept PTD as an editor's draft for continued development as part of the WG
#
ben_thatmustbeme
cwebber2, bombshells are fine but maybe put it on the agenda first
#
hhalpin
mf has higher uptake in web-pages than any other format
#
cwebber2
ben_thatmustbeme: I did, I just messed up and put it on the wrong agenda :P
#
hhalpin
and RDF has a sizable community as well
#
kevinmarks
100% of web devs use HTML
#
hhalpin
topic: Type discovery
#
hhalpin
Yes, but NOT mf2
#
cwebber2
so yeah I failed ;p
#
hhalpin
sorry, but that's true
#
tantek
issue-4
#
trackbot
is looking up issue-4.
#
trackbot
issue-4 -- Do we rely on explicit typing or support implicit typing based on explicit property names? -- open
#
hhalpin
So we can't force parsing HTML on people who see JSON as easier
#
ben_thatmustbeme
cwebber2 haha, no problem, we all make mistakes
#
melvster1
kevinmarks++
#
Loqi
kevinmarks has 174 karma
#
kevinmarks
sure, but claiming that JSON is JSON-LD is more tendentious
#
tantek
action-35
#
trackbot
is looking up action-35.
#
RRSAgent
sees no action items
#
trackbot
action-35 -- Tantek Çelik to Come up with a simple proposal for implicit typing based on property names -- due 2015-02-10 -- PENDINGREVIEW
#
hhalpin
however, I agree with the general goal that people who embed data into web-pages using mf seems to work well
#
eprodrom
tantek++
#
Loqi
tantek has 246 karma
#
hhalpin
so it should be supported, it has wider uptake
#
eprodrom
excellent guessing
#
hhalpin
tantek: We have implicit typing
#
hhalpin
... we can get interop in mf2 with AS2
#
kevinmarks
no-one is forcing you to parse mf2, we have many parsers for you out there
#
hhalpin
... its a small, modular draft
#
hhalpin
my point is *most* people don't use mf2 in modern webdev frameworks. They use HTTP APIs that deliver JSON
#
cwebber2
rhiaroif it was the same proposal, but SHOULD instead of MUST for as2
#
hhalpin
tantek: My request is that the group accept it as editors draft
#
hhalpin
however, my second point is the main issue is AS1 and AS2 has little uptake
#
cwebber2
would that affect your response btw?
#
hhalpin
My point is that JSON *itself* has much wider updake than either RDF or mf2
#
rhiaro_
cwebber2: I could live with SHOULD
#
hhalpin
so that should be a common conversion pattern
#
cwebber2
rhiaro_: noted
#
csarven
q+ ISSUE/ACTION is not clear to me.. there is a minor gap. What are the actual implications of this to current AS2? Is ACTION-25 meant to provide an alternative (implicit)?
#
Zakim
csarven, you typed too many words without commas; I suspect you forgot to start with 'to ...'
#
hhalpin
tantek: I would like to keep that mechanism the same
#
kevinmarks
no-one is arguing against JSON
#
csarven
q+ ISSUE/ACTION is not clear to me..
#
Zakim
csarven, you typed too many words without commas; I suspect you forgot to start with 'to ...'
#
csarven
q+ ISSUE/ACTION is not clear to me
#
Zakim
csarven, you typed too many words without commas; I suspect you forgot to start with 'to ...'
#
hhalpin
furthermore, it's not a small difference: it's several orders of magnitude in terms of uptake
#
eprodrom
q?
#
Zakim
sees no one on the speaker queue
#
Zakim
sees csarven on the speaker queue
#
aaronpk
try q+ to discuss
#
ben_thatmustbeme
i made a quick point that i was corrected on that could have been seen as that kevinmarks
#
eprodrom
ack csarven
#
Zakim
sees no one on the speaker queue
#
kevinmarks
mandating the specific JSON-LD vocab that is under draft was what was being proposed
#
hhalpin
PROPOSAL: Take up tantek's post-type discovery as a Working Draft of the WG
#
Arnaud
I think this is in keeping with the trend of untyped languages like Javascript with all of its pros and cons :)
#
tantek
hhalpin, as an Editor's draft
#
hhalpin
s/Working Draft/Editor's Draft
#
hhalpin
csarven: The result of ACTION-35 is to change from implicit to explicit approach
#
hhalpin
... so we have an algorithm to deal with implicit approach
#
Arnaud
the claim "explicit post types that are being abandoned by modern post creation UIs" probably ought to be backed up with some references though
#
hhalpin
tantek: Accept the document as a work-item
#
hhalpin
... that's all I'm proposing
#
hhalpin
... for systems that require explicit typing it expands content they can consumer
#
hhalpin
... we've had some good experience
#
aaronpk
Arnaud, see: facebook and twitter
#
kevinmarks
arnaud look at the Medium and Buzzfeed post editors if you want mainstream UI
#
hhalpin
I am going to note that it appears the mf2 community is the most active implementers
tilgovi joined the channel
#
eprodrom
q+
#
Zakim
sees eprodrom on the speaker queue
#
hhalpin
tantek: We've had good feedback
#
hhalpin
csarven: We would mention that we could say "explicit" or "implicit"
#
Arnaud
I'm not questioning the claim, just pointing out that this ought to have a reference, your examples would work
#
kevinmarks
instead of a post type, they both have a series of blocks that enable you to post different content types as part fo a post
#
hhalpin
tantek: I would work with jasnell to see if we could do co-ordinate and browsers tend to do this
#
hhalpin
q+
#
Zakim
sees eprodrom, hhalpin on the speaker queue
#
hhalpin
csarven: That makes sense
#
hhalpin
eprodrom: This is the pattern used in micropub
#
hhalpin
... with POST parameters for intended types of parameters
#
hhalpin
... correct?
#
hhalpin
tantek: If you are an AS2 consumer that has explicit types
#
hhalpin
... the micropub use-case is an explicit one
#
Zakim
sees eprodrom, hhalpin, aaronpk on the speaker queue
#
hhalpin
... one of the implementations is to do this
#
eprodrom
ack aaronpk
#
Zakim
sees eprodrom, hhalpin on the speaker queue
#
eprodrom
ack eprodrom
#
Zakim
sees hhalpin on the speaker queue
#
melvster1
JSON LD has implicit typing (elf posted some links to the ML)
#
hhalpin
aaronpk: when I receive a micropub request based on what's in it
#
hhalpin
... it shows up in different feeds
#
cwebber2
melvster1: yeah but the goal here is to help microformats->AS2
#
cwebber2
which I think doesn't work with elf's examples
#
cwebber2
in that sense it might also be helpful in getting from microformats->rdf
#
cwebber2
I think?
#
hhalpin
eprodrom: There's the types mentioned in a webmention, thats where these properties came from
#
rhiaro_
I have my own version to decide internally how to display posts based on the properties: http://rhiaro.co.uk/2015/09/post-type
#
hhalpin
... are we documenting existing behavior?
#
ben_thatmustbeme
yes, i do something similar
#
eprodrom
q?
#
Zakim
sees hhalpin on the speaker queue
#
ben_thatmustbeme
but this actually helps clear some parts up and makes sense to me
#
hhalpin
tantek: All sorts of ways of doing responses, but its mainly trying to do things like distinguish between articles and notes
#
eprodrom
ack hhalpin
#
Zakim
sees no one on the speaker queue
#
eprodrom
q?
#
Zakim
sees no one on the speaker queue
#
ben_thatmustbeme
can we just vote on the proposal?
#
hhalpin
Editors draft does not mean we have consensus, just its a reasonable thing to be working on and within scope
#
hhalpin
usually in W3C it's a fairly low bar
#
hhalpin
I would vote for it as it seems useful to a particular community and necessary for interop
#
eprodrom
+1
#
hhalpin
+1
#
eprodrom
RESOLVED: Take up tantek's post-type discovery as a Working Draft of the WG
#
hhalpin
RESOLVED: Accept Post-type discovery as an editor's draft
#
sandro
present+ sandro
#
Zakim
sees ben_thatmustbeme on the speaker queue
#
hhalpin
eprodrom: Can you move this to the wiki Tantek?
#
hhalpin
q+
#
Zakim
sees ben_thatmustbeme, hhalpin on the speaker queue
#
eprodrom
q?
#
Zakim
sees ben_thatmustbeme, hhalpin on the speaker queue
#
eprodrom
ack ben_thatmustbeme
#
Zakim
sees hhalpin on the speaker queue
#
tantek
will do! thanks everyone
#
hhalpin
ben: Let's have a flat agenda
#
hhalpin
... rather than devote too much to the first topic
#
hhalpin
s/too much/too much time
#
hhalpin
ben: Single items rather than going through actions
#
hhalpin
... use github issues
#
hhalpin
... even if it's skipping around subjets
#
hhalpin
s/subjets/topics
#
eprodrom
q?
#
Zakim
sees hhalpin on the speaker queue
#
tantek
+1 to flat agenda - allows us more freedom to FIFO different topics and make sure we get to different topics in the order raised / added to agenda
#
hhalpin
I'm not on this point
#
eprodrom
PROPOSAL: flat agenda where we use bullet points
#
hhalpin
tantek: CSS WG does it this way
#
hhalpin
+0
#
Arnaud
I have to admit not to understand what a flat agenda means
#
eprodrom
-1
#
eprodrom
q
#
Arnaud
it's too bad because I'd be very interested to understand
#
eprodrom
q?
#
Zakim
sees hhalpin on the speaker queue
#
hhalpin
We could run an experiment and try it once
#
eprodrom
ack hhalpin
#
Zakim
sees no one on the speaker queue
#
Arnaud
but we're out of time
#
tantek
Arnaud - see CSS WG telcon agendas as an example
#
tantek
posted to www-style
#
sandro
-1 I want phone dialin, as much as I like mumble for some things
#
ben_thatmustbeme
Arnaud: it would mean this would have had more time than the last minute on the call to discuss this
#
Arnaud
to be more explicit: the problem seems to be about time allocation
#
sandro
but we could try one of the other phone dialin options
#
hhalpin
any objections to mumble?
#
Arnaud
I don't know that the format of the agenda is the problem
#
cwebber2
so, sounds like objections. ok!
#
hhalpin
What we need is mumble + phone dial-in :)
#
akuckartz
+1 to using open source compatible solution
#
cwebber2
I think we still need to handle the international phone version :P
#
hhalpin
Although notes non-US folks can't dial-in as easily
#
tantek
-1 I want phone dialin also like sandro
#
eprodrom
agenda item for next week?
#
hhalpin
eprodrom: lets revisit next week
#
ben_thatmustbeme
can it be the top of the agenda next week?
#
tantek
hhalpin: I'm using Google Hangouts on iOS over wifi to make a "phone call"
#
kevinmarks
the workaround for no-us is to use google hangouts which does require an account, but has free us calling
#
hhalpin
eprodrom: meeting adjourned, talk to you next week
#
tantek
hhalpin++ for minuting!
#
hhalpin
trackbot, end meeting
#
trackbot
Zakim, list attendees
#
Zakim
As of this point the attendees have been Arnaud, csarven, rhiaro, aaronpk, shanehudson, sandro, elf-pavlik, kevinmarks, wilkie, eprodrom, jasnell, ben_thatmustbeme, cwebber,
#
trackbot
is ending a teleconference.
#
Loqi
hhalpin has 10 karma
#
Zakim
... tantek, hhalpin, james, tsyesika, wseltzer, akuckartz
#
trackbot
RRSAgent, please draft minutes
#
RRSAgent
I have made the request to generate http://www.w3.org/2015/10/13-social-minutes.html trackbot
#
trackbot
RRSAgent, bye
#
RRSAgent
I see no action items
#
eprodrom
kevinmarks: right, but some of the people don't want to use Google Hangouts
#
kevinmarks
other services offer free us calling too
#
akuckartz
I would like to see a system using WebRTC
#
kevinmarks
I just meant it is easier than getting webex working
#
aaronpk
i can make a webrtc to phone bridge if someone is willing to contribute a little $$
#
kevinmarks
I agree that WebRTC is great
#
cwebber2
btw, I think kevinmarks(?) is right in that there's a component of "are we documenting the real world" vs "are we putting forward a standard to implement", and that's an unresolved part of this group
#
cwebber2
though it's also notable
#
ben_thatmustbeme
Arnaud, eprodrom, this is actually the exact problem the proposal is trying to solve, we rush these "other items" in at the end of the meeting, if -1s result from the fact that its just the last few minutes (which is fair, we need time to discuss) anything that is in the "other items" can just get pushed off indefinitely and never given adequate time to discuss
#
Arnaud
ben_thatmustbeme, you could have two bullets on the agenda and spend the whole hour on the first one and you'd end up with the same frustration
#
tantek
akuckartz: I would too! WebRTC++
#
cwebber2
federation doesn't really exist on a real scale
#
aaronpk
the twilio api has a webrtc bridge
#
tantek
but the software is just not there yet
#
ben_thatmustbeme
Arnaud: true, except bullet 3 would be the top of the next week
#
aaronpk
it costs a little per minute, but is not outrageous
#
kevinmarks
well, it is, but only really in chrome
#
cwebber2
so it's kind of a pile of barely implemented incompatible stuff right now
#
Arnaud
ok, that I understand
#
akuckartz
tantek: I will try to make a proposal next week ;-)
#
ben_thatmustbeme
more like a rolling bulletted list
#
Arnaud
but it's not the flatness that makes that happen :)
#
tantek
ben_thatmustbeme is right - having a flat agenda avoids the topic-starvation problem
#
Arnaud
you can do the same with the current format
#
Arnaud
just make sure you move things around
#
Arnaud
I think that's fair
#
tantek
the assumption of a flat agenda is that you discuss things in the order added
#
ben_thatmustbeme
this topic i actually added the the agenda as soon as the agenda was proposed, and it didn't get any discussion time this week because of the formatting
#
tantek
and anything not discussed rolls over to next week
#
ben_thatmustbeme
s/proposed/posted
#
kevinmarks
so treat the agenda as a queue, with only chairs able to adjust ordering?
#
tantek
Arnaud the current format means AS2 issues can starve everything else
#
Arnaud
that's poor chairing from our part
#
tantek
that's the point of breaking up the clusters
#
Arnaud
we can and should have time limits
#
tantek
the clusters in the agenda make it extra work (harder) for the chairs to do anything FIFO like
#
rhiaro_
Like, AS2 has one or two important items under that heading, and a bunch of stuff that's less important. But the less important stuff gets to take up time because it's all in one place at the top.
#
tantek
rhiaro: right
#
Arnaud
if we have spent too much time on AS2 we need to stop and move on
#
rhiaro_
Stuff that could be discussed if time, gets discussed instead of stuff that needs to be discussed
#
tantek
Arnaud: or we have a flat time-ordered agenda and don't have to worry about topic-starvation
#
tantek
because any agenda items not addressed get addressed the next week etc.
jasnell_ joined the channel
#
Arnaud
I find the name "flat agenda" not really descriptive of what you are talking about, round robbing or something like that would be better in my opinion
#
aaronpk
"round robining"?
#
kevinmarks
cwebber2: I found this quote that sums up well what I am getting at: https://kindle.amazon.com/post/HLglK_6oRhOnsiQSo829eg
#
Arnaud
but now that I understand I'm fine with that
#
tantek
Arnaud: flat in contrast to grouped
#
kevinmarks
linear agenda?
#
tantek
perhaps FIFO would be more descriptive
#
Arnaud
aaronk: sorry, round robin :)
#
tantek
to make the ordering more clear
#
Arnaud
linear, flat, are missing the point
#
kevinmarks
“Language is not a protocol legislated by an authority but rather a wiki that pools the contributions of millions of writers and speakers, who ceaselessly bend the language to their needs and who inexorably age, die, and get replaced by their children, who adapt the language in their turn.”
#
Arnaud
the point is the order
#
Arnaud
kevinmarks: go tell that to the French Academy :-)
#
Arnaud
fifo is good
#
kevinmarks
I don't need to; millions of French speakers already are.
tilgovi and jasnell joined the channel
#
rhiaro_
Minutes correction:
#
rhiaro_
[13:30:09] <hhalpin> rhiaro: Map what currently exists to what implementations we have
#
rhiaro_
-> rhiaro: This is an outline of how I understand the different pieces of the SocialAPI and how they fit together or could be considered independantly, which I've started to fill with the equivalent parts of existing specs - as a potential route to convergence.
#
rhiaro_
cwebber2, you were minuted as saying [13:35:38] <hhalpin> ... tantek has figured how to map microformats to RDF's type system
#
rhiaro_
is that accurate to what you said?
#
cwebber2
rhiaro_: I think I said something closer to "I think tantek's proposal might be able to map microformats to types"
#
cwebber2
since that's my rough understanding
#
tantek
right - high level (user level) post types
#
tantek
I'm not claiming to know anything about RDF's type system :)
#
cwebber2
tantek: do you think it could be used to map to specific AS2 vocabulary types?
#
cwebber2
because that could be really helpful for convergence purposes
#
tantek
cwebber2: yes - and the "like" example demonstrates that https://indiewebcamp.com/post-type-discovery#Like_post
#
cwebber2
tantek: +1
#
tantek
I'd rather focus on ways of interoperating than wars.
#
cwebber2
+1 there too.
#
cwebber2
who is right and wrong in long running disagreements preceding this group is out of scope. but how to work together is totally in scope.
#
cwebber2
or at least I hope :)
#
tantek
I think we can make a lot of progress with the combination of documenting what's been implemented, and how to interoperate with multiple approaches.
jaywink, bblfish, tilgovi, Arnaud, jasnell, kevinmarks, eprodrom and tantek joined the channel