#social 2016-01-05

2016-01-05 UTC
jasnell, prtksxna, jasnell_ and jaywink joined the channel
#
Loqi
RESOLVED: Skipping telcons on 12/22 and 12/29, next telcon
#
Loqi
Countdown set by eprodrom on 12/15/15 at 10:15am
elf-pavlik and shevski joined the channel
#
ben_thatmustbeme
lol, thanks Loqi
#
Loqi
you're welcome
shevski joined the channel
#
cwebber2
I'm on a train to San Francisco!
#
cwebber2
I might be present via IRC, I'm not sure yet.
tantek joined the channel
#
tantek
good morning #social!
#
wilkie
good morning
azaroth joined the channel
#
cwebber2
morning
akuckartz joined the channel
#
Arnaud
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
#
trackbot
Meeting: Social Web Working Group Teleconference
#
trackbot
Date: 05 January 2016
#
sandro
Arnaud, did you use the host code, or not need to?
#
rhiaro
present+ rhiaro
#
Arnaud
present+
#
wilkie
present+
#
rhiaro
I'll scribe!
#
rhiaro
been a while
#
rhiaro
scribenick: rhiaro
#
Arnaud
chair: Arnaud
#
aaronpk
present+
#
azaroth
present+ Rob_Sanderson
#
akuckartz
present+
#
akuckartz
No audio yet
#
tantek
present+
#
jasnell_
running late, be right there
#
tantek
mutes himself since it's a bit noisy here.
#
rhiaro
Arnaud: welcome back, happy new year!
#
rhiaro
TOPIC: approval of minutes from 2015-12-15
#
rhiaro
PROPOSAL: Approve minutes from 2015-12-15
#
tantek
looked at them a while ago
#
rhiaro
Arnaud: any objections? anyone looked at them?
#
akuckartz
agenda is empty?!
#
rhiaro
sandro: They contain approval to go to fpwd for two drafts
#
jasnell_
present+
#
rhiaro
Arnaud: hearing no objections, approved
#
rhiaro
RESOLVED: Approve minutes from 2015-12-15
#
rhiaro
... Reminder, face to face proposed march 16th
#
rhiaro
... Page set up, please specify your expected attendance
#
rhiaro
... As usual, if you're not sure please say so
#
rhiaro
... Better than saying nothing
#
rhiaro
... As you remember I sent regrets for the last few meetings, but noticed that agenda ended at the last call with the post-type discovery draft going to fpwd, and that was postponed to this week
#
rhiaro
TOPIC: Post type discover draft
#
rhiaro
tantek: We've had this up for a while, a few issues and some resolved
#
rhiaro
... a few implementaitons of parts of it
#
rhiaro
... I think it's in public shape for fpwd
#
rhiaro
... So I request the group consider that
#
rhiaro
... If there are specific issues that must be resolved before we take it to fpwd pleases say what the issue number is
#
rhiaro
... Other than that, general feedback, is it ready or not. I think it's ready.
#
rhiaro
Arnaud: Comments?
#
tantek
muted
#
rhiaro
... Need more time?
#
wilkie
I think it is fine
#
rhiaro
... If you need more time you could object and ask for time
#
rhiaro
... Been on the agenda for a while
#
tantek
PROPOSED: Publish Post Type Discovery as a FPWD
#
rhiaro
... Don't see any reason to delay further
#
tantek
is still listening, just muted
#
azaroth
I haven't implemented it, but have read it and see no reason to delay FPWD
#
azaroth
+1
#
rhiaro
... Please vote
#
rhiaro
... For FPWD we don't need implementation, to clarify
#
ben_thatmustbeme
there are 10 ppl on the call
#
tantek
is abstaining obv
#
rhiaro
... I think we can call it resolved. Last call?
#
rhiaro
RESOLVED: Publish Post Type Discovery as a FPWD
#
rhiaro
... Sandro, you'll have to send the transition request
#
rhiaro
sandro: is it all under respec? or need to be reformatted?
#
rhiaro
tantek: I probably have some respec reformatting and all the pubrules checking to do
#
rhiaro
sandro: could you do that in the next day or so? then we could do all three documents on thursday
#
Loqi
I added a countdown for 1/7 12:00am (#5785)
#
rhiaro
... Just less work to do three at once
#
rhiaro
tantek: I'll see what I can do, but don't hold up the others
#
rhiaro
Arnaud: key part is, tantek you have the ball, once you're done let sandro know
#
rhiaro
... Sandro you can still request the transition in th emeantime
dromasca joined the channel
#
rhiaro
TOPIC: AS2
#
rhiaro
... Ready to go to CR? Still a few issues left, some editorial
#
rhiaro
... 276 in particular postponed because someone was missing
#
sandro
RRSAgent, pointer?
#
rhiaro
... James?
#
rhiaro
jasnell: want to ensure that vocabulary document has examples of all features
#
rhiaro
... Examples there don't illustrate everything
#
rhiaro
... I can add those, but PRs would be helpful
#
rhiaro
... tantek opened one about it needing a section on privacy implications, current working draft should have that
#
rhiaro
... would like everyoen to take a look and see ifthat's adequate
#
rhiaro
... Other editorial is 278, updating acknowledgements section, which I will do
#
rhiaro
... Two substantive issues, 261 and 276
#
rhiaro
... 261 talks about lifecycle and naming conventions for extensions, came up at last f2f
#
rhiaro
... So far no proposal put forward
#
cwebber2
participating via text-only from here
#
cwebber2
as long as train connection lasts
#
rhiaro
... 276 might be easier after 261
#
rhiaro
Arnaud: cwebber wants to talk about 261?
#
rhiaro
jasnell: 261 was a conversation between sandro and tantek at the f2f
#
rhiaro
... do you want to discuss?
#
cwebber2
huh, do I?
#
rhiaro
tantek: I captured because sandro felt strongly about it
#
rhiaro
... I'll leave to sandro
#
Arnaud
I may be mixing issues and people :)
#
cwebber2
oh... Arnaud I think it's probably important but I don't have much to say at the moment
#
tantek
"Need lifecycle and naming convention guidance for extensions to help possible future convergence and standardization "
#
rhiaro
jasnell: goes back to whether we need to capture naming convention or registry for extensions
#
rhiaro
... for future standardisation
#
rhiaro
... and whether that needs to be documented in the core draft
#
rhiaro
sandro: I don't think so. I mean.. I have been thinking about this a lot and I don't think there's anything we can do right now that will really help
#
rhiaro
jasnell: so close without action?
#
rhiaro
sandro: yep
#
tantek
I'm ok with that
#
rhiaro
PROPOSED: Close issue 261 without further action
#
rhiaro
Arnaud: please vote
#
azaroth
+1
#
dromasca
+1
#
rhiaro
RESOLVED: Close issue 261 without further action
#
rhiaro
jasnell: next is 276, require valid as2 implementations to use vocabulary where applicable
#
rhiaro
... So when we're using an extension, say schema.org as a type, eg. Person
#
rhiaro
... THe implementor should also use the corresponding core vocabulary type
#
rhiaro
... So the type field would list schema:Person and as:Person
#
jasnell_
"type": ["schema:Person", "Person"]
#
tantek
that must seems reasonable
#
rhiaro
... That is so that anyone who doesn't understand the extesion can still make use of that by falling back to core vocab term
#
rhiaro
... Recommendation is for interop
#
rhiaro
... Spec says should, issue says make it a MUST
#
tantek
as in, prevent extension makers/users from hijacking core spec semantics
#
tantek
and claim compliance
#
rhiaro
... Personally I think should is fine
#
rhiaro
... I know in the comment thread others said SHOULD is okay
#
rhiaro
... but we need to get clarification
#
rhiaro
... I'd like to propose keeping should
#
rhiaro
... ie close without further action
#
tantek
I'm leaning more towards MUST
#
tantek
What are the objections to MUST?
#
tantek
I think it makes the spec stronger FWIW
#
Zakim
sees no one on the speaker queue
#
rhiaro
if you have a really good reason not to use AS2, why are you using AS2 at all?
#
rhiaro
Arnaud: use cases to argue one or the other?
#
tantek
MUST tends to be better for interop
#
rhiaro
jasnell: use case is interop
#
sandro
tantek, can you update https://github.com/w3c-social/post-type-discovery to explain which of the two drafts it links to is the real one?
#
ben_thatmustbeme
must means extensions have to have two types, which i find annoying personally
#
tantek
I can't think of any good reason to allow foo:person and allow them to NOT say 'Person"
#
rhiaro
... if someone lists only schema.org, someone who doesn't understand schema.org might not know there is a core type to correlate
#
rhiaro
... tantek, want to speak?
#
azaroth
q+ to be in favor of MUST
#
Zakim
sees azaroth on the speaker queue
#
rhiaro
tantek: I think that when in doubt standards tend to work better when conservative, MUST is more consvertaive. Tightens up interop.
#
rhiaro
... If people feel ambivalent about it, or no strong opinion, we should go with MUST
#
cwebber2
I'm -0 on MUST
#
rhiaro
... Unless there's an objection to must
#
rhiaro
... More MUST = better interop
#
cwebber2
+1 on SHOULD
#
rhiaro
... Curious about use case for SHOULD
#
jasnell_
I have no objection to must but think the should is ok
#
Zakim
sees azaroth, ben_thatmustbeme on the speaker queue
#
rhiaro
... I think that's where burden of proof is
#
Arnaud
ack azaroth
#
Zakim
azaroth, you wanted to be in favor of MUST
#
Zakim
sees ben_thatmustbeme on the speaker queue
#
rhiaro
... shouldb e MUST by default
#
rhiaro
azaroth: also in favour of MUST for similar reasons
#
rhiaro
... Should be explicit about what is required, and promoting classes and properties that the standard requires is just part of every day life. To say that you not-must use the features when you don't want to just makes it more difficult for everyone to implement
#
Arnaud
ack ben_thatmustbeme
#
Zakim
sees no one on the speaker queue
#
rhiaro
ben_thatmustbeme: My only concern is that extensions are forced to have multiple types
#
rhiaro
... if they want their own types. Annoying as a developer. Can live with, but is a nuisance
#
jasnell_
lets perhaps split the question: show of hands in favor of must vs show of hands in favor of keeping it as should
#
azaroth
q+ to ask about extensions
#
Zakim
sees azaroth on the speaker queue
#
tantek
it's not for all extensions
#
tantek
it's only "where applicable "
#
cwebber2
o/ should
#
wilkie
"MUST" to promote interop seems strange. do you add MUST for every new thing? hmm.
#
tantek
ben_thatmustbeme: note: "where applicable "
#
tantek
poll should vs must?
#
rhiaro
Arnaud: straw poll
#
tantek
wilkie: yes, MUST is how standards indicate their core requirements
#
rhiaro
cwebber2 I'm interested in why you're -0
#
tantek
+MUST
#
wilkie
I know what MUST means
#
Arnaud
STRAWPOLL: a) keep it a SHOULD, b) make it a MUST
#
azaroth
Right. Extensions that don't conflict with the core wouldn't have multiple types
#
Arnaud
a: x, b: y
#
jasnell_
a) +1 b) +0
#
rhiaro
Arnaud: +/-/0 responses to both in one line
#
azaroth
a: -0, b: +1
#
rhiaro
a) +0 b) +1
#
tantek
a: -0, b: +1
#
sandro
a) -0 b) +0
#
akuckartz
a: +0.5 b: +0.5 :-)
#
wilkie
a) +1 b) +0
#
ben_thatmustbeme
no real objections either way
#
rhiaro
Arnaud: argh...
#
cwebber2
a)+1 b) -0
#
rhiaro
jasnell: I would wager to say that everyone could live with MUST
#
ben_thatmustbeme
I can live with MUST
#
rhiaro
... even if folks are okay with should
#
ben_thatmustbeme
it certainly does improve interop
#
rhiaro
sandro: only negative on must is chris with -0
#
cwebber2
I can live with MUST, though I think it's strange to have it that strong
#
rhiaro
... chris wanst to voice?
#
cwebber2
but I can live with it
#
rhiaro
Arnaud: I'll cast a vote to try to make thins different
#
cwebber2
I think that it would be strange to point to an AS2 implementation and point at a term and say "you didn't include our term, you aren't compliant"
#
cwebber2
thus I think SHOULD makes more sense
#
rhiaro
... I'm sensitive to tantek's arguement that the more MUST we have the more interop we have
#
cwebber2
that's my voice
#
cwebber2
but, I think it doesn't make or break things
#
Arnaud
PROPOSED: Close 276, changing to a MUST
#
azaroth
+1
#
wilkie
cwebber2: that's essentially exactly how I feel
#
rhiaro
<rhiaro> cwebber2 only if there's an applicable type, right?
#
cwebber2
however I'm also happy to have a resolution
#
rhiaro
<rhiaro> so if there *is* an applicable type, why wouldn't you use it?
#
tantek
cwebber2: that's exactly what the MUST is for, so an implementer can't just make up their own duplicate versions of the terms in AS2 Core and claim compliance without using AS2 terms in actuality.
#
rhiaro
<rhiaro> if there isn't an applicable as2 type, no big deal
#
jasnell_
thank you cwebber2 .. yeah, it's only applicable if there's an overlapping type in the core
#
cwebber2
note that going through trains makes it hard to vote
#
rhiaro
Arnaud: we don't have to rush if you want to discuss further
#
jasnell_
understood cwebber2
#
cwebber2
I'm 0 becaus I am fine with closing with MUST
#
cwebber2
if it means closing it
#
cwebber2
I don't think it's worth keeping open
#
rhiaro
jasnell: I can add language to clarify that this is really when there are overlapping terms
#
rhiaro
... It's not saying you MUST use one every time, only when there's overlap
#
cwebber2
jasnell_, that is fine with me
#
tantek
Also, making it a MUST will help force implementers to reveal any specific use-cases to the contrary (i.e. for a SHOULD)
#
cwebber2
and helps
#
rhiaro
Arnaud: I think we can close it
#
cwebber2
+0 with that clarification
#
rhiaro
RESOLVED: Close 276, changing to a MUST
#
rhiaro
Arnaud: ready for CR then?
#
cwebber2
I should say
#
rhiaro
jasnell: Will get a new wd out this week, and go from there
#
cwebber2
going through tunnels makes it hard to vote :)
#
cwebber2
mountain tunnels aren't exactly great for tethering :)
#
rhiaro
Arnaud: can we agree to go to CR pendng james's edits?
#
tantek
ok will add an issue
#
cwebber2
+1 on CR pending edits
#
rhiaro
sandro: we can't go to CR without figuring out exit criteria, and we should probably ?? tests
#
rhiaro
Arnaud: for now we'll let james edit, get it in shape, then tackle those issues next week
#
rhiaro
... Maybe now?
#
sandro
loves that, perfect scribing .... I did, in fact, says "probably ?? tests" :-)
#
tantek
just created
#
tantek
for tracking purposes
#
rhiaro
... tantek, you're pointing to an issue..
#
rhiaro
... proposal?
#
rhiaro
tantek: just wanted to capture what sandro said
#
Zakim
sees azaroth, jasnell_ on the speaker queue
#
rhiaro
Arnaud: usually exit criteria means there are two implementations of every feature
#
rhiaro
... doesn't mean they have to be in the same implementation
#
rhiaro
sandro: need to clarify what it means to be an implementation
#
rhiaro
... producer, consumer..
#
rhiaro
... Vague sense we had consensus at face to face, but not clear
#
Zakim
sees azaroth on the speaker queue
#
azaroth
q-
#
Zakim
sees no one on the speaker queue
#
jasnell_
q+ to talk about test suite
#
Zakim
sees jasnell_ on the speaker queue
#
rhiaro
Arnaud: we could talk more now or put at the end of agenda for today
#
rhiaro
... Mostly what's left today is status updates
#
Zakim
sees jasnell_, tantek on the speaker queue
#
Arnaud
ack jasnell_
#
Zakim
jasnell_, you wanted to talk about test suite
#
Zakim
sees tantek on the speaker queue
#
rhiaro
jasnell: as far as test suite is concerned, I did create a new github repo to start collecting sample activitystreams documents
#
rhiaro
... PRs to add samples to these would be helpful, I'll add as I have time (which I haven't)
#
rhiaro
... will continue to add myself too
#
rhiaro
... intent of this is to give us a corpus of test documents that illustrate every feature of the vocabulary
#
rhiaro
... so that implementations can go test to make sure that they are compliant
#
rhiaro
Arnaud: so what's important is that when we publish the cr draft is we have a pointer that leads people to a page where they can understand where to start and how to test their implementation
#
rhiaro
sandro: and where to post test results
#
rhiaro
Arnaud: okay if it's not complete, but we at least need a pointer in the document
#
rhiaro
sandro: gonna be some press around it saying this is our call for implementations
#
rhiaro
... so good to have instructions (complete) on day one
#
rhiaro
... strongly suggest we have test suite done
#
akuckartz
Samples of non-AS2 documents will also be helpful
#
rhiaro
... we can fix it later
#
Zakim
sees tantek on the speaker queue
#
rhiaro
... but should have it ready to go and copmlete before CR
#
Arnaud
ack tantek
#
Zakim
sees no one on the speaker queue
#
rhiaro
... Depending on whether we're trying to sneak through or get something good here
#
rhiaro
tantek: from my understanding we don't actually need to have a complete test suite to enter CR, even to have a test suite at all, but the more we do have the more real it looks and the more implementable it looks
#
rhiaro
... so this is going to have to be a judgement call
#
rhiaro
... strictly from a process perspective we can enter CR as long as we have agreed on exit criteria
#
rhiaro
... that meet w3c exit criteria expectations
#
rhiaro
... The biggest challenge with the test suite is not to have one that's complete but to have a test suite that lets us have some common understanidng
#
rhiaro
... last time we got into a heavy discussion about the test suite there were different opinions about what that meant
#
rhiaro
... if we have to figure this out, the biggest challenge is how to say this implementation does something with the vocabulary that makes it necessary to be in the spec
#
rhiaro
... If all we have is tests that converts a stream between syntaxes, all it's testing is syntax parsing, not justifying anything in the vocabulary
#
rhiaro
... That's the biggest problem of considering whether a feature is 'implemented\
#
rhiaro
... That's the biggest challeng
#
sandro
+1 tantek -- the tests should really show the vocabulary being used
#
Zakim
sees sandro on the speaker queue
#
rhiaro
... Don't have a proposal, more just want to raise this issue as an area of past disagreemtn that we need to resolve on
#
rhiaro
... Also an area that evan and myself have disagreed on in the past
#
rhiaro
... other opinions on this, people should speak up
#
akuckartz
tantek++
#
Loqi
tantek has 267 karma
#
rhiaro
... say what they think a featur emeans, and what testing that feature means
#
azaroth
+1 to tantek, and +1 to not delaying -entering- CR before having the test suite
#
rhiaro
Arnaud: i recall, two aspects
#
rhiaro
... testing producers, can do with a validator
#
rhiaro
... testing consumers, have a suite of documents that james was talking about
#
ben_thatmustbeme
a validator should certainly be a very minimum for our "test suite"
#
rhiaro
... How you test wehther the application really understands it is still open ended I believe
#
Arnaud
ack sandro
#
Zakim
sees no one on the speaker queue
#
rhiaro
sandro: I agree with what tantek just said
#
rhiaro
... i think cwebber2 and I were talking after the f2f... understanding I came to is that we should have a validator that at least gives a simple human readable description of what the machine readable syntax says
#
rhiaro
... Producers check their output against this validator
#
rhiaro
... And they send us an email saying all the terms they used and checked against the validator
#
rhiaro
... and we keep a table of all the terms they said that about
#
rhiaro
... and Consumers, need to use our suite of documents to tell us which terms their consumer can consume
#
rhiaro
... and their good faith assertion that it consumes them properly and understands what they mean
#
rhiaro
... and they might want to test that side by side with a validator. Look at a document in our validator and their thing, and say if they agree they make sense in the same way
#
rhiaro
... So we have a list of terms people produce and consume and believ ethey do so correctly because it aligns with our validator
#
rhiaro
Arnaud: comment?
#
Loqi
sandro has 26 karma
#
rhiaro
tantek: good start
#
akuckartz
sandro++
#
Loqi
sandro has 27 karma
#
rhiaro
... biggest challenge is validating that a vocabulary is being used correctly
#
rhiaro
... is one thing, but part of the purpose of exiting CR is saying
#
rhiaro
... these feature are *doing something*
#
rhiaro
... if that something is abstrac tor concrete... by concrete I mean in a UI
#
tantek
the challenge is whether the abstract vocabulary does something specifically in the UX
#
rhiaro
sandro: I'd like the reports from people not just to be a checklist of terms, but a paragraph saying what they're doin gwith it
#
rhiaro
... Hope that would help get the ball rolling if people see what others ar edoing
#
rhiaro
Arnaud: sandro since you seem opinionated about what we are to do, can you make a proposal?
#
rhiaro
... By next week
#
rhiaro
sandro: Sure.. the hard work is going to be having the test suite and validator and collecting results
#
rhiaro
... I think we need volunteers to do all those things
#
rhiaro
... But I'm happy to write that proposal
#
rhiaro
Arnaud: Quite a bit of work, not sure if we can afford to wait for it all to be done for CR
#
rhiaro
... Would be in favour of adding framework set up, publish CR with pointer, and keep on working on it
#
rhiaro
sandro: be nice to have the beginnings of a test suite and hopefully a partial validator
#
rhiaro
... but could say coming soon
#
rhiaro
tantek: this is where if we are specific in the exit criteria and we say that we say there are two or more implemenations of every feature where an implemenation means they are producing/consuming syntax correctly, and also producing some result that is unique to that vocabulary term as compared to other terms
#
rhiaro
... some language like that to put strenght into CR exit critiera
#
rhiaro
... that buys us time to create broader test framework
#
rhiaro
... we don't even need to have it partially done before CR
#
rhiaro
... I don't want to delay CR based on test suite
#
rhiaro
sandro: I'm not going to stand on the road over this, but If eel like in terms of developer engagement, but I'd rather hit them with one.. here's a time to look at AS2, and have the ducks in a row
#
rhiaro
... meaning there's a validator, examples
#
rhiaro
... and here's one or two implementations from inside WG
#
rhiaro
... as a developer I'd have a much more positive reaction
#
rhiaro
... if it all says coming soon, I could ignore
#
rhiaro
Arnaud: I agree we don't want to have nothing, but there's a middle ground
#
rhiaro
... We have a basic framework set up, and say as we move forward we'll add
#
rhiaro
sandro: has to be enough that i can start to play right now
#
rhiaro
... has to be a working validator for at least some stuff
#
rhiaro
... and a working set of info documents
#
rhiaro
... if I can't write code today and get in a feedback loop with the WG
#
rhiaro
tantek: I sympathise with what sandro is saying from a developer perspective. In the braoder view, AS2 has been in the discussion for years before w3c etc
#
ben_thatmustbeme
i'd agree with sandro, as a developer i would want a validator and set of documents
#
rhiaro
... Some level of built up expectation that we have inherited
#
rhiaro
... This is not brand new, it's been maturing for years
#
rhiaro
... Expectation that more of these tools and tests exist
#
rhiaro
... Absence may give people the wrong impression
#
rhiaro
... The fact that as2 has been going on for years before w3c has touched it. People have heard of it, already have an idea of what it means
#
rhiaro
... There's been a lot of work, we're not just rubber stamping, we need to show developers where the work is
#
rhiaro
... Devleopers can say 'okay now I get why this is real now'
#
rhiaro
... We have to figure something out, I don't know how
#
rhiaro
Arnaud: i don't think we're far away, just a matter of finding the sweet spot so we can got to CR without waiting for too long
#
rhiaro
... Suggest we leave it at this for today, sandro will put proposal together
#
rhiaro
... Feel free to discuss between now and next week
#
rhiaro
... Next week we can see what it will take
#
rhiaro
... See who volunteers to help out etc
#
rhiaro
TOPIC: Status updates
#
rhiaro
... Docs approved for publication last week. Sandro?
#
rhiaro
sandro: I think it's in my lap at this point. We can't use echidna for fpwd, so a bunch of manual steps, which can only be done on thursday
#
Loqi
I added a countdown for 1/7 12:00am (#5786)
#
rhiaro
shut up loqi
#
rhiaro
Arnaud: we got approval from wendy
#
rhiaro
sandro: I have to convert to static html and run a bunch of tests
#
ben_thatmustbeme
arronpk what was the command to tell loqi to forget a timer?
#
rhiaro
Arnaud: maybe thursday, if not tuesay next week
#
aaronpk
!cancel 5786
#
Loqi
Ok, I cancelled it
#
rhiaro
... Reminder on giving everybody until 12th Jan to raise issues in ActivityPump and micropub
#
rhiaro
... Don't miss out
#
rhiaro
... Expectation to go to fpwd
#
rhiaro
... Finally, admin.. looking at tracker, a couple of issues
#
rhiaro
... when I looked at actions, baffled by list of open actions
#
rhiaro
... Don't care to go through this now, but highly recommend that people look, several of you have open actions
#
rhiaro
... We should be able to close some of these
#
rhiaro
... Either they have become irrelevant or you can tell us what's stopping you
#
rhiaro
... But looks silly to have actions due over a year ago still open
#
rhiaro
... Please ahve a closer look and see where cleanup can be done?
#
rhiaro
... That leads us to the end of the call
#
ben_thatmustbeme
we have actions for people no longer in the WG
#
rhiaro
... Next call next week, resuming normal weekly callls
#
rhiaro
... Any other items?
#
rhiaro
sandro: on the open actions, some of mine are obsolete and we basically just stopped using the tracker
#
rhiaro
... should just mark as done? Others are more debateable?
#
rhiaro
... Shouldl people just mark them done or invovle the rest of the group?
#
rhiaro
Arnaud: personally I'm fine with people marking them as done
#
rhiaro
... There is a history of changes
#
rhiaro
... So if there's abuse, it can be dug up
#
rhiaro
... Meant to be a help to the group
#
rhiaro
sandro: mark as closed if it's not controversial, pending review if you want to talk about it
#
rhiaro
Arnaud: yes, then we can discuss on calls
#
rhiaro
... If there's something that really ought to be done, please do it!
#
rhiaro
... Any other business?
#
Zakim
sees no one on the speaker queue
#
rhiaro
evan isn't here to defend himself
#
rhiaro
... Let's close on this
#
rhiaro
... Thanks!
#
wilkie
rhiaro++
#
azaroth
Bye all! :)
#
wilkie
thanks all
#
Loqi
rhiaro has 194 karma
#
Arnaud
trackbot, end meeting
#
trackbot
is ending a teleconference.
#
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,
#
Zakim
... tantek, hhalpin, james, tsyesika, wseltzer, akuckartz, shepazu, Rob_Sanderson, Shane_, rene, cwebber2, Benjamin_Young, bengo, ben_thatmust, KevinMarks_, jasnell_, MUST
#
trackbot
RRSAgent, please draft minutes
#
RRSAgent
I have made the request to generate http://www.w3.org/2016/01/05-social-minutes.html trackbot
#
trackbot
RRSAgent, bye
#
RRSAgent
I see no action items
#
rhiaro
jasnell_: do you have time for a quick (hopefully) question?
#
jasnell_
what's up
#
rhiaro
I dug up from a PR comment that @graph isn't valid in AS2
#
rhiaro
but all the turtle->json-ld converters (disclaimer: didn't try many) use @graph by default
#
rhiaro
which meant I ended up quickly hacking together my own just for collections
#
rhiaro
Which is just kind of inconvenient. Is there a good reason @graph isn't valid?
#
rhiaro
(since I store all my blog data as turtle, I thought it would be a couple of lines to output AS2, but can't with the rdf library I currently use, and web services I tried use @graph)
#
rhiaro
Not a huuge deal, just curious about it
#
rhiaro
oh hm, on that note I believe in the AS2 spec it says AS2 is a 'subset' of JSON-LD, but isn't clear about what the subset is. But maybe I need to re-read.
#
jasnell_
@graph implies use of JSON-LD, which isn't normatively required
#
jasnell_
in other words, it serves no function within AS2
#
rhiaro
but if I do use @graph, is it still valid as2?
#
rhiaro
or not because normal json consumers will be confused?
#
jasnell_
@graph is technically a valid extension property
#
rhiaro
(which is fair enough)
#
jasnell_
but normal json consumers wouldn't know how to deal with it
#
rhiaro
that's reasonable
#
jasnell_
json-ld compaction using the normative context should never output @graph
#
rhiaro
having actually typed this it makes more sense than when it was just in my head ;)
#
rhiaro
I don't know the ins and outs of json-ld, I just like to throw turtle at converters
#
rhiaro
possibly the converter I was using did that because I had multiple contexts
#
rhiaro
although... I think it did it when I only had as2 as well
#
jasnell_
ok.. yeah, may be a problem with those converters
#
rhiaro
okie dokie
#
rhiaro
thanks!
jaywink joined the channel
#
tantek
and with that no more open actions for me!
shepazu joined the channel
#
jasnell_
editor's draft update published
#
jasnell_
will prepare the new WD's by end of week
Arnaud1 joined the channel
#
Zakim
sees sandro on the speaker queue
#
cwebber2
I'm back now
#
tantek
sandro ?
#
cwebber2
sorry about earlier
#
aaronpk
ack sandro
#
Zakim
sees no one on the speaker queue
#
cwebber2
spottiness about connections from a train, as I said
#
cwebber2
I'm amazed that a connection held up that long.. we were traveling through the snow covered mountains formerly traversed by the donner party :)
#
cwebber2
not exactly known for its connection to civilizaiton
#
cwebber2
(though beautiful!)
#
sandro
(my q+ was in the wrong irc channel)
#
Zakim
leaving. As of this point the attendees have been Arnaud, csarven, rhiaro, aaronpk, shanehudson, sandro, elf-pavlik, kevinmarks, wilkie, eprodrom, jasnell, ben_thatmustbeme,
#
Zakim
... cwebber, tantek, hhalpin, james, tsyesika, wseltzer, akuckartz, shepazu, Rob_Sanderson, Shane_, rene, cwebber2, Benjamin_Young, bengo, ben_thatmust, KevinMarks_, jasnell_, MUST