From W3C Wiki

Based on minutes.


jasnell, elf-pavlik, evanp, jtauber, Arnaud, ShaneHudson, +1.703.670.aaaa, +1.503.567.aabb, aaronpk, Sandro, +1.541.410.aacc, bblfish, hhalpin, markus, tantek, tiborKatelbach


RESOLVED: Minutes of 16 september approved

RESOLVED: Initial use cases from the IG for social data syntax by TPAC

[scribe: There were a number of other straw proposals but it wasn't clear to me if there were any further RESOLUTIONS passed, for example "SWAT0 is the initial use-case"]


ACTION: everyone review AS2.0 for FPWD for next week. [recorded in]


<evanp> trackbot, start meeting

<trackbot> Date: 23 September 2014

<evanp> who's on the call

<aaronpk> Zakim: aabb is aaronpk

<evanp> scribe: jtauber

<aaronpk> i always forget the comma

<jasnell_> tantek: so, in your opinion "social" only means "public 'posts' with @mentions to other people" and to be a valid example, those posts must be publicly accessible?

<wilkie> I think

approval of last week's minutes

<evanp> +1

<jasnell_> +1

<ShaneHudson> +1

<wilkie> +1

<jtauber> +1

<aaronpk> +1

<elf-pavlik> +0 (didn't have chance to read :( )

evanp: minutes approved

... registration for TPAC: important for people to register to keep room

<wilkie> I don't think I can afford that trip :(

<Arnaud> the right way to scribe this is: resolved: minutes of 16 september approved

<Loqi> it'll be ok

Arnaud: thanks

<Arnaud> resolved: minutes of 16 september approved

<elf-pavlik> evanp: question of use cases...

<harry> note that use-cases are in scope of Social IG

<harry> *not* Social WG

<harry> thanks!

<elf-pavlik> +1 harry

<Arnaud> the right way to scribe change of topic: topic: xxx

question of use cases

<Arnaud> +1 to elf

<wilkie> oops

<bblfish> +q



<Arnaud> +q


<wilkie> sorry

<jasnell> At the very least, this WG ought to define: (A) what is a "Social System" and (B) what constitutes "Social Data"

<elf-pavlik> Arnaud: appreciates concern about timeline, but we don't need to make it a huge effort

<wilkie> are there existing use case analysis??

<harry> Yes, please see Social XG

<elf-pavlik> Arnaud: agrees with elf, picking specific use cases we care about addressing

<harry> rather infinite use-case documents.

<jtauber> elf-pavlik: you keep beating me to it :-)

<harry> We define all of that in the Social XG report.

<evanp> Zakim: q?

<Zakim> sandro, you wanted to say a few illustrative use cases might be a reasonable compromise


<wilkie> harry: yes. I've read that. exactly. it seems the challenge is not coming up with the use cases again and again or refining them but rather now applying knowledge to create a flexible social vocab/syntax with what we have

<aaronpk> can someone add : as an alternate for , in Zakim? or where is the source code so I can hack it up?

<harry> Yes, so do it in the Social IG

<harry> We have technical and implementation work to do here.

sandro: what are people's elevator pitch for involvement in this group?

<wilkie> harry: +1

sandro: capture use cases lazily when we disagree

<bblfish> +1 for that

harry: use cases are off topic for this group and use case discussion should move to IG

<Arnaud> if there is already a list we can point to and adopt that's great

harry: happy for some use cases to be attached to spec

<wilkie> is the social XG use cases linked on the wg wiki?


harry: use cases for spec should be drafted first by editor of spec

<ShaneHudson> +1 for what harry is saying

jasnell: we don't have a shared definition of what a social system is

<evanp> tantek: mute please

<harry> PROPOSAL: Use-cases happen in Social IG. Editors may add "use cases" to their specs and can argue those later.

<evanp> your keyboard is too loud

<tiborkat> zakim: +tiborkat


harry: we spent a long time working on definitions in incubator

... definition discussion can take place in IG

<harry> Move the XG's use-cases and definition discussion to the IG.

evanp: possible resolution: accept XG use cases and move discussion to IG

<harry> +1

<evanp> +1

<tiborkat> +1

<ShaneHudson> +1

<MarkCrawford> +1

<jtauber> +1

<bblfish> -1

<aaronpk> +1

<sandro> -1

<wilkie> +1

<markus> +0

<elf-pavlik> -1

<tantek> +1 with ok to add more use-cases to

<Loqi> tantek meant to say: +1 with ok to add more use-cases to

<jasnell> Need time to review XG definitions again prior to deciding

<harry> Sandro and Henry Story both dissented.

<harry> And Elf.

MarkCrawford: use cases is primary deliverable of IG ... more than happy to direct IG on particular set of use cases the WG would find useful in short term

i can't hear bblfish to scribe

<evanp> <-- I added a link to the XG use cases

<wilkie> evanp: so did I!

<sandro> harry: the final report wasn't a list of use cases [ I think]

<harry> Please type your point bblfish.

sandro: difference between listing use case and accepting use case

... all for IG enumerating possible use cases but WG doesn't want to accept all use cases as requirements

<bblfish> my point was that the is not a list of use cases. That is mostly just a list of existing technologies

<tantek> +1 on accepting a *subset* of XG use-cases per sandro clarification

<tantek> thank you sandro

<harry> Sorry, bblifsh, you are wrong

<harry> neutral use-cases are here:


<evanp> bblfish: sorry, when I said "XG use cases" I meant

<bblfish> and I agree with Sandro that we have to here agree on the use cases, plus we need to narrow them down to what this group is doing


<aaronpk> at this point we might as well do IRC-only conferences

<tantek> Aside: I am opposed to without having any such representative join the wg. All schema-org members are W3C members thus they should join the socialWG if they want to participate in the meeting.

harry: compromise: let IG work out use cases

<tantek> +1 to let IG work out use-cases

<elf-pavlik> i -1 since i didn't ask about heavy pile of use cases, but one or two we can excercise in our conversations

<bblfish> The deliverables are very vague harry

<jasnell> tantek: +1, definitely agree

<elf-pavlik> so this resolution didn't address my proposal

<MarkCrawford> We can stage our work in the IG so that we are only looking for a few related to the focus of the WG as a first step

<tantek> jasnell - for clarification in minutes do you mean in reference to the schema-org special meeting proposal?

<jasnell> proposal: give us a week to review the XG final report, defer this conversation for next week

<jasnell> yes

<tantek> +1 harry to IG being used for use-case discussion

<ShaneHudson> The purpose of the IG is for this exact thing

<tantek> if you want to bring a use-case to the WG, you MUST provide a URL to your use-case documentation.

<tantek> otherwise you're not done discussing it, and continue on IG list

<tantek> who is scribe?

<tantek> I don't see any minuting happening.

bblfish: there has to be more open and agreement about what the use cases are before we start spec

<harry> No, the Interest Group has official status and is not open to everyone.

<harry> It requires an IE status. It just has no patent commits.

<harry> You should read the charters bblfish.

bblfish: WG isn't bound by IG

<elf-pavlik> harry, CG then most peole can join

<Arnaud> the problem is more about scope, the IG is much more open ended

<Arnaud> I think it's reasonable to have the IG develop use cases

<Arnaud> but the WG ought to agree on which ones are relevant to this WG

<harry> So, we let the development of use-cases happen in IG

<harry> and then they bring them up to WG when mature.

<harry> Makes sense.

<sandro> Possible proposal: postpone discussion of use cases, except when they illustrate a design decision

elf-pavlik: asking for some simple scenarios not complete use cases


<MarkCrawford> If you tell me for which expected functionality of the spec you want use cases, we will get those for you.

<tantek> SWAT0 and its components are a good starting point, and quite challenging :)

<evanp> -1

evanp: what's feeling around single use case we use to measure different systems

<tantek> 30 seconds? no chance ;)

<tantek> (and I helped write it)

<tantek> hey that was close! nicely done evanp :)

<tantek> +1 evanp starting with SWAT0 as our first/single/primary use-case

<elf-pavlik> +1

<wilkie> +1

<sandro> +0.5 starting with SWAT0

<ShaneHudson> +1 That is very clear about how it needs to work

<bblfish> the swat one seems better

<harry> Addition: No other use-case discussion.

<harry> +1

<harry> That happens in the IG.

<MarkCrawford> +1

<jtauber> +1

<ShaneHudson> +1 to the addition

<elf-pavlik> +1

<markus> +0.8... this seems to be too broad for me... where's the limit? access control, login, ...

<aaronpk> +1 for SWAT0 since it actually covers a wide range of needed behavior

<tiborkat> +1

<evanp> +1

<bblfish> +1 for swat0, but not for limiting to that.

<jasnell> +0

<tantek> +1 for swat0 and limiting to that in this WG until IG has more to contribute

<jtauber> do we scribe "resolved" for straw polls?

<jasnell> -1... it ought to be up to the chairs when and whether to reintroduce use cases to the discussion

<markus> my vote doesn't take harry's addition into consideration

<markus> strongly object to that comment

<sandro> +1 <jasnell> -1... it ought to be up to the chairs when and whether to reintroduce use cases to the discussion

<bblfish> but you seem to have decided already what the specs are harry

<harry> RESOLUTION: SWAT0 is initial use case.

<Loqi> sandro meant to say: +1 <jasnell> -1... it ought to be up to the chairs when and whether to reintroduce use cases to the discussion

<Arnaud> err... harry we have an objection! no resolution

<ShaneHudson> Arnaud: Wasn't that for the addition?

<jasnell> link for SWAT0?


evanp: ask IG to provide additional use cases before TPAC

<tantek> harry, RESOLUTION: SWAT0 is the initial use-case

<tantek> *use* case

<Loqi> aww, cheer up

<Arnaud> ok, I'm good with that resolution

<harry> PROPOSAL: Only the chairs can decide when to introduce new use-cases into the discussion, and then the rest of the use-case discussion should happen in the IG or be off-topic

<bblfish> thanks sandro for spotting that

<tantek> we can start talking test cases when we we have one or more drafts being implemented on the way to a CR

<tantek> do we have any such working drafts?

<harry> RESOLUTION: SWAT0 is the initial use-case

<harry> Although at some point would like to see test-cases :)

evanp: reasonable to have social data syntax use cases for TPAC?

<sandro> Harry, it's already up to the chairs to decide that. Don't limit their power via the Exception Proves The Rule.

<harry> Sandro, that's a proposal to clarify the scope.

MarkCrawford: happy to ensure focus of IG is requirements of WG over next few weeks

<elf-pavlik> i propose to move it to mailing list and go on with other agenda points soon

<evanp> +1

<jasnell> alternative PROPOSAL: Anyone can propose a use case discussion on the mailing list or wiki but the chairs will decide whether the use case is put on the agenda/queued for discussion.

<harry> And ask people to move use-case discussion to IG until appropriate, as judged by the WG chairs.

<harry> jasnell, the WG mailing list is not appropriate for an open-ended use-case discussion by anyone. That's why we have the IG.

<evanp> Should we ask for initial use cases for social data syntax by TPAC (end October)?

<harry> We need to clarify what forum is useful for which kind of discussion.

<ShaneHudson> From the IG?

<evanp> ShaneHudson: yes

<ShaneHudson> +1

<wilkie> +1

<harry> +1

<elf-pavlik> +1

<jasnell> harry: I didn't say open ended use-case discussion. I said propose a use case discussion that the chairs can choose to accept or not

<Arnaud> harry, but anyone can propose the WG adopts a use case developed in the IG

straw poll: Should we ask for initial use cases for social data syntax from the IG by TPAC (end October)?

<bblfish> +1 but it's still something that the group has to then agree to here

<tantek> +1 with deadline the *Tuesday* before TPAC so we have a chance to review


<elf-pavlik> +1

<jasnell> +1 for asking the IG for use cases

<harry> Yes, but you have that discussion on the IG list, not the WG list. When you think you have something ready after discussion at the IG, then you can propose to the WG.

<markus> +1 if the IG is fine with that

<MarkCrawford> +1

<harry> We need to keep signal-to-noise ratio on WG mailing list and wiki better.

<harry> And we need more people to contribute to the IG

<ShaneHudson> I agree with Tantek that it would be good to have it ready before TPAC to review

resolved: ask IG for initial use cases for social data syntax before TPAC

<tantek> aside: federatedsocialweb (dot) net - where all SWAT0 was initially documented, expired and has been taken over by a spammer :( :( :(

<harry> RESOLUTION: Initial use cases from the IG for social data syntax by TPAC

<Loqi> it'll be ok

<wilkie> +1

<bblfish> what is a "direction for a sodical data syntax?"

straw poll: ready to start deciding direction for social data syntax

<harry> +1 for jasnell's efforts to align to without using the same URIs

<tantek> -1 I still don't understand what this has to do with AS2 or anything. vocabs yes. but syntax?

<elf-pavlik> jasnell: requir JSON-LD as minimal requirement

<bblfish> +1 for JSON-LD

<tantek> -1 for requiring JSON-LD

<tantek> +1 for JSON-LD as an *option*

<harry> We could always have the @context as an "option"

<elf-pavlik> +1 require JSON-LD

<harry> That is what AS2.0 did.

<wilkie> +1 for JSON-LD

<Loqi> harry meant to say: That is what AS2.0 did.

<markus> +1 for JSON-LD.. obviously

<bblfish> +q

<sandro> +100 jasnell redefine activity streams as an ontology, and look at alignment with no strong feelings about json-ld.

<elf-pavlik> jasnell: explains as:Activity vs as:Actions

<tantek> sandro by ontology do you mean vocab?

<harry> Also, I'd prefer to use the term "vocabulary" rather than "ontology" lest we sound silly

<markus> doesn't make sense to make it optional.. we can nevertheless ensure that JSON-only clients can process documents

<sandro> yes, I mean vocab. James used the word "ontology", and vocab owl:sameAs ontology.

<elf-pavlik> +1 markus

<elf-pavlik> +q

<tiborkat> +1 for json-ld

<Zakim> tantek, you wanted to oppose working with schema-org without documentation of concrete real world *socialweb* usage, and having schema-org companies joing the wg

<jasnell> my proposal was NOT to align with my proposal is to define AS2 as an ontology, required JSON-LD as MUST implement.

<harry> Notes that I'd like to see folks come to face-to-face to discussion.

<harry> So I'd rather do that than BOF

<harry> on Thursday, which conflicts with things.

<elf-pavlik> harry, i would like to discuss it *today*

<jasnell> real world example: github has adopted

<elf-pavlik> tantek: asks to find real world examples of uses

<elf-pavlik> tantek, github - social coding

tantek: without social web usage of or particpating companies in the WG, discussion should be out of scope

<aaronpk> agreed with tantek

<ShaneHudson> I also agree with tantek's concerns

<harry> I think we already have disagreement over JSON-LD from tantek.

bblfish: JSON-LD as a basic syntax

<harry> Everyone is happy with it as an option though.

<tantek> I am opposed to requiring *any* particular syntax from this WG

<elf-pavlik> -1 harry

<tantek> I am *for* providing syntax *options*

bblfish: don't mix syntax with semantics/pragmatics

<elf-pavlik> also markus just raised concern about optional requirement

<harry> Note that the charter requires JSON as a basis.

<tantek> -1 on JSON-LD as a required basis

<jasnell> the AS2 ontology approach allows us to use JSON-LD and HTML5 syntax options, and also allows turtle

<jasnell> etc

<elf-pavlik> evanp: we had straw pool 2 weeks ago and JSON-LD had big support

<ShaneHudson> +1 harry, JSON as a basis with JSON-LD as an option

<harry> Discussion of XML alternatives etc. are out of scope

<Arnaud> harry, are you saying that JSON-LD doesn't qualify as JSON?

<harry> Happy to bring those up in the IG.

<harry> No, JSON-LD is a subset of JSON.

<markus> +q to ask tantek why he objects to use JSON-LD

<harry> So we're happy to have JSON-LD either as a requirement (if group gets consensus) or as an option.

evanp: many proposals in front of us use JSON-LD

<tantek> I object to *requiring* JSON-LD

<jasnell> no, JSON-LD is JSON with some additional bits. JSON-LD can be parsed as JSON without requiring any of the JSON-LD processing model

<sandro> Ah, Tantek wants to allow microformats

<wilkie> some systems only use xml :)

<markus> markus: tantek, could you please elaborate on why you object to json-ld and what you mean by making it optional

<elf-pavlik> JSON-LD also allows microformats as vocab

tantek: JSON-LD can be documented options but we should allow HTML5 + microformats


<aaronpk> (side note that HTML5 + microformats can be turned into a JSON document via the parsing rules)

harry: charter says JSON is requirement

<wilkie> I feel that argument means RSS should be our leading example because of its prevalence heh

<sandro> Social Data Syntax

<sandro> A JSON-based syntax to allow the transfer of social information, such as status updates, across differing social systems. One input to this deliverable is ActivityStreams 2.0.

<elf-pavlik> evanp, can you ask for extra 15min time for this call please?

<tantek> there is canonical JSON output from microformats parsers

<evanp> elf-pavlik: will do

<bblfish> I kind of agree with the points about RDFa/microformats but then we can make it simple: The protocol could be put in terms of RDF then

<jasnell> a minimal JSON syntax can be defined and adopted that is IDENTICAL to the serialization that JSON-LD provides

<harry> The charter is pretty old :)

<harry> I'm very pro being implementation driven.

<sandro> tantek: Since the charter was written, it's become out-of-date, as we now have microformat-providing servers working well

<harry> We should get back to folks invite for TPAC.

<elf-pavlik> evanp, any objections to extending call for another 15min

evanp: extend 15 minutes

<tantek> +1 to extending the call

<sandro> +1 extending

<wilkie> +1

<bblfish> no objections

<jtauber> +1

<elf-pavlik> +1

<harry> +1

<markus> no objection

<tiborkat> +1

<ShaneHudson> There is no reason why json and microformats can not both be options, they would work the same way more or less (as microformats can be parsed as JSON anyway as pointed out)

<Loqi> tantek meant to say: +1 to extending the call

<ShaneHudson> +1

<sandro> ShaneHudson, that would require clients to parse both

<tantek> sandro - I corrected myself, "mistaken" was mis-spoke by me :)

<tantek> why put something simpler (microformats) in terms of something more complex? (RDFa)

<elf-pavlik> I think we *need* more conversation over mailin list before we discuss it during teleconf

bblfish: linked data principles whether in JSON-LD, RDFa microformats

<elf-pavlik> tantek, i find RDFa simler

<tantek> disagree that it's difficult for servers. more personal social websites are serving HTML5+microformats than RDFa.

<jasnell> Note: We already agreed previously to split Activity Streams 2.0 into separate Syntax and Vocabulary. The Vocabulary would define the Activity ontology. This vocabulary can be represented in JSON, JSON-LD, HTML, or any other syntax.

<harry> The last thing I want to revisit is the microformat vs. RDFa vs. microdata debate.

<tantek> harry - right

<elf-pavlik> evanp, I would like to ask last 5 minutes to discuss *Meeting with team @TPAC*

<tantek> and I want to avoid making that kind of decision politically for sure

sandro: one format or variety of interchangable formats?

<evanp> elf-pavlik: thanks, I will try to get us to that

<tantek> as opposed to by documented adoption

<harry> We have chosen ONE required format, JSON, in the charter. Other syntaxes are optional.

<jasnell> What I suggest is: At a minimum, to address the charter requirement, we require a minimum-to-implement JSON serialization that is compatible with JSON-LD but does not require an implementer to use the JSON-LD processing model to understand

evanp: charter does specify JSON

<bblfish> I think the social web is so big, that in then end you have to accomodate a few different syntaxes. But we MUST agree on the model

<harry> +1 and not a required @context element or "@" namespaces, although I hope folks will use this.

<markus> tantek, you stressed several time how strong the adoption is... do you have a pointer to any data... I'm curious

evanp: abstract vocabulary won't be enough for API / protocol parts of scope

<tantek> for the "required" JSON syntax in the charter, I would propose the canonical JSON output of microformats parsers:

<jasnell> We can accomplish this using a properly defined @context

<wilkie> tantek: will you just veto a non-microformat direction regardless of discussion and charter? I think JSON-LD and microformats are both very good and can be both used without too much trouble.

<tantek> markus - yes, documented on documents and in detail on


aaronpk: HTML + microformat is just syntax

<harry> Note that 99% of RDFa use is Facebook's OGP tag, which uses it incorrectly

<tantek> harry - note - not *socialweb*

<markus> tantek, thanks.. but it's quite hard to find something in the wiki... I'll give it a try

<tantek> wilkie - I will oppose *requiring* JSON-LD

<wilkie> ok

<tantek> that's a political decision

<tantek> not data/evidence driven

<jasnell> tantek: what about my suggestion?

<tantek> so is requiring JSON - but we unfortunately froze that into the charter

<wilkie> I'm not sure that's true, nor do I see a lot of data on anything

<harry> It was felt in chartering that ONE syntax was needed, and JSON was kinda simple.

<evanp> Zakim q?

<wilkie> I'm pretty sure JSON is widely supported haha

<tantek> harry - serving JSON is *extra work* = not simple

<aaronpk> and XML was widely supported 10 years ago, so...

<ShaneHudson> Focusing on the actual model will avoid problems with JSON one day going out of fashion (in the same way as XML)

<elf-pavlik> sandro: how about developin library which will bridge all exisitng indie web deployments into new standard we recommend

<tantek> whereas *everyone* on the *web* has to serve HTML

<tantek> so the *simplest* approach was to just add microformats to that HTML

<sandro> sandro: I'm hoping folks using microformats can be happy with this JSON-social-data-syntax via some conversion libraries

<elf-pavlik> i will help with microformat json to json-ld tools

<MarkCrawford> Unfortunately, I have another call. Open question - what communities would we be freezing out of our spec if we choose JSON?

<tantek> here's some JSON if that's what you're looking for:

<harry> There are real existing microformat+HTML communities

<harry> There are to my knowledge, no widespread usage of non-JSON or microformat+HTML software for federated social.

<evanp> +1

<jasnell> +1

<sandro> PROPOSED: We accept AS2.0, modified to be JSON-LD, as our starting point

<elf-pavlik> +1

<tantek> -1

<sandro> +1

<wilkie> +1

<markus> +1

<tantek> to be clear, I am very strongly *for* publishing AS2.0 in this WG

<bblfish> +1 for now

<jtauber> 0

<tantek> I am *against* picking *a* social syntax

<bblfish> Essentially that proposal interests me

<tantek> based on these current proposals

<tiborkat> +1

<sandro> PROPOSED: Publish JSON-LD version of AS 2.0 (details to be confirmed) as a FPWD (without exactly resolving the idea of it being "the one and only")

<elf-pavlik> +1

<tantek> PROPOSE: Publish AS2.0 as spec'd as *implemented* (not JSON-LD)

<elf-pavlik> -1

<tantek> implementations > JSON-LD

<aaronpk> aren't there are already implemenations of AS 2.0 without JSON-LD?

<tantek> precisely

<evanp> aaronpk: I don't believe so

<evanp> AS 1.0 is widely used

<tantek> that's my point. let's publish the spec as implemented, not some future hypothetical

<tantek> evanp - jasnell has documented implementations on the socialwg wiki

<Arnaud> maybe the question should be: should our JSON serialization be compatible with JSON-LD?

<jasnell> yes, there are implementations of AS2

<elf-pavlik> bblfish: i prefer Turtle over JSON-LD but it bridges to RDF world

<jasnell> they are not as broad as AS1

<Loqi> elf-pavlik meant to say: bblfish: i prefer Turtle over JSON-LD but it bridges to RDF world

<evanp> jasnell: thanks, useful data point

<elf-pavlik> +1 bblfish

<Arnaud> we should leave the question of required syntax off the table for now, there is clearly interest in different serializations

<jasnell> Arnaud: +1

<elf-pavlik> +1 Arnaud

<evanp> Arnaud: I think we need at least one preferred serialization for use with our other deliverables

<ShaneHudson> +1 Arnaud

<markus> arnaud, apart from tantek's -1 I just saw +1s to Sandro's proposal

<tantek> I propose people vote with their implementations and their sites. If you believe in a syntax, publish it at your personal site URL. And better yet, consume it.

<Loqi> markus meant to say: arnaud, apart from tantek's -1 I just saw +1s to Sandro's proposal

<tantek> then document it

<harry> PROPOSAL: Get a new draft of ActivityStream 2.0 for discussion at TPAC f2f

<bblfish> What happened to the proposal of Activity Streams with JSON-LD?

<harry> That's neutral on the JSON vs. JSON-LD debate btw.

<evanp> PROPOSED: Name jasnell as editor of AS 2.0 and request a draft for TPAC

<markus> what's the "new draft"?

<harry> That was rejected by Tantek, and we need to clarify.

<jasnell> there editor's draft is available on github already

<jasnell> it's available for anyone to review

<tantek> I'd like to see a FPWD of AS2 *before* TPAC

<jasnell> the pre-tpac version will be available in a branch before TPAC

<tantek> jasnell - please provide URL to current editor's draft for the minutes

<jasnell> at least two weeks before tpac

<elf-pavlik> jasnell, will you make one following your last email?




<bblfish> I am confused about what the proposal is

<elf-pavlik> some issues will come from:

<jasnell> the activitystreams2.html and activitystreams2-vocabulary.html documents are the ones that will be ready by TPAC

<jasnell> that was decided several weeks ago wasn't it?

<markus> jasnell, is activitystreams2.html already up to date?

<jasnell> there was a proposal and a resolution that a FPWD would be ready by TPAC

<ShaneHudson> Yes I think that was already resolved

<harry> Arnaud, are you OK with people attending the f2f or a section thereof at TPAC?

<tantek> I see no issues with that comparison elf-pavlik - schema vocabs are not worthy of comparison to AS2 per above issues of schema-org

<tantek> jasnell - I'm trying to make progress on publishing AS2

<sandro> Harry, I have seen zero objection to JSON-LD. That was NOT Tantek's objection.

<elf-pavlik> thanks harry, i take my question to jasnell back

<jasnell> I am too

<elf-pavlik> can we write down this proposal on IRC

<sandro> +1 invite folks to attend whatever they want, and sent aside some specific time, too

<ShaneHudson> I also need to go, sorry. I agree with inviting them

<jasnell> -1 for joining the WG session *unless* it's going to be more than a sales pitch. There needs to be a specific technical agenda

<elf-pavlik> i will reply to public-vocabs with link to log after this call

<tantek> -1 for special treatment of schema-org during TPAC

<harry> Sandro, there was objection for JSON-LD being a requirement.

<evanp> -1

<jasnell> -1

<tantek> schema-org members are all W3C members. ergo they can join the WG.

<jtauber> -1

<sandro> harry, from whom?

<wilkie> -1

<tantek> It's been over a year since the osfw3c workshop

<elf-pavlik> i don't see clear proposal writen down on irc while people do +/-1

<sandro> +1 lets learn what they have to offer

<harry> PROPOSAL: For a limited technical session with f2f at TPAC?

<elf-pavlik> +1

tantek: for editor incorporating other specs in his research, against special treatment for as they can just join WG

... unless there are real world examples, let's not spend time discussing other formats

<harry> Sandro, the objection from JSON-LD being a requirement came from Tantek. He was happy for it to be an option.

<sandro> Harry, you are completely misrepresenting what Tantek is saying.

<tantek> no I think Harry got it right. I'm opposed to JSON-LD requirement. I am *for* documenting a JSON-LD option.

<harry> Sorry sandro, but that's how it is.

<harry> You can try to discuss more with Sandro on mailing list and IRC re having JSON-LD as a requirement.

<evanp> tantek: thanks

<sandro> I'm not talking about having JSON-LD as a requirement. I'm talking about AS2.0 using JSON-LD. That's not what Tantek is objecting to, and you are saying it is.

<harry> It looks like an informal BOF is the way forward. I'd suggest Wednesday rather than Thursday, as we have structured time.

<sandro> And Harry, you're "sorry" is unbelievably rude.

<elf-pavlik> IRC log looks like very confusing

<tantek> sandro, I am *for* AS2.0 publishing as is currently implemented.

<harry> Where JSON-LD is not required.

<tantek> sandro, I am *against* making AS2.0 make changes that are political (JSON-LD) rather than what AS2 implementations support.

<sandro> You mean JSON-LD is not allowed.

<elf-pavlik> harry, BOF with team?

<harry> Happy to help wiht informal BOF if on Wednesday

<Loqi> I added a countdown for 9/24 12:00am (#5499)

<tantek> let's get a FPWD of AS2 which reflects actual AS2 implementations.

<bblfish> As a methodology point in the LDP working group, when everybody agrees with a point except one person, then ususally one tries to find a way to convince the person

no, i don't believe so

<bblfish> or get to a compromise

<evanp> ACTION: review AS 2.0 for next week [recorded in]

<trackbot> Error finding 'review'. You can review and register nicknames at <>.

<harry> Sandro, I suggest you discuss with Tantek directly. As Tantek said, I think I was accurately representing his position to, but you can discuss with him directly.

<tiborkat> thx bye

<elf-pavlik> thanks evanp ! jtauber

<evanp> *whew* that was a long one

<jtauber> do I need to do anything to close out scribing?

<tantek> specifically for that ACTION for review AS2 for FPWD publication

<evanp> jtauber: no, there's a little recipe I have to do

<tantek> ACTION: everyone review AS2.0 for FPWD for next week. [recorded in]

<trackbot> Error finding 'everyone'. You can review and register nicknames at <>.

<evanp> harry, thanks

<elf-pavlik> tantek, you may need to assign it to yourself ...

<harry> trackbot, end meeting