#melvsterthis part about social profiles interests me
#melvsterit seems to me in trying to implement the use cases, there would be a benefit in a common understanding of following, and in implementing following, there would be a benefit in a common understanding of profiles
#sandroor you can use the webex client, on many platforms (ie use it on linux and android). And you can have it dialout to you if you want to use POTS and not pay.
#sandroben_thatmustbeme: THe need for multiuple natural languages in a single activity. No user stories include it. No systems I know that use it. I was suggesting removing it.
#sandroben_thatmustbeme: I think it's complex enough that I don't know how to solve it.
#tantekwe should drop features from AS2 that have zero presence in any user stories and zero silo equivalent feature implementations
#sandrojasnell: Multi language support is a feature of json-ld. We inherit support even if we don't say anything. This is trying to scope it a bit, to say it's only meaningul in particular cntext
#sandro.. I see there are some issues with translation to MF2 and MD, which are more presentation oriented.
#harryI do think multiple language support is important, the W3C really wants to support internationalization in general
#sandro.. I think it's okay that some things don't translate perfectly, but I think it's important to keep it.
#tsyesikaI think being able to express content in multiple languages is important for multilingual people with followers who understand different language(s)
#sandroeprodrom: It sounds like we have a use case not yet captured. Is it possible to capture it?
#wilkieas an implementor, I'd feel rather bad not including support for multiple language posts, and worried that the IG was just biased to miss this use-case
#tsyesikafor what it's worth http://tsyesika.se/feed I've started manually writing my ActivityPump feed before I have got my software ready, that's using it
#sandrotantek: Brainstorming document looks good. We need to keep encouraging progress. I'd like to continue down that path, rather than an arbitrary deadline, like 1st draft by tpac.
#ben_thatmustbemetries to figure out who call in users 6, 8, and 9 are
#sandroharry: I'm just trying to remind folks of our charter schedule
#sandrotantek: Worst thing is to publish a std prematurely
#tantekevan: we are done with this conversation, if you (henry) want to talk to sandro about participation in this group that's something you can do offline.
#sandrotantek, thanks for scribing. too in shock to scribe.
#bblfishit is productive for me cwebber2. I just found out that if I participate I'll get no help from Sandro. So I'd just be wasting my time. Unless others want to support me.
#harryshepazu, have time for a quick update on Annotations? When should look at the draft annotation specs? What's the dependencies?
#tantekshepazu: we separated our web annotation group into separate areas
#tantekshepazu: one is data model, given a message, what is the formatting
#sandrobblfish, that's ALSO not what I said bblfish
#tantekshepazu: our default serialization is JSONLD, you can also use turtle, some of us are interested in HTML as well, e.g. using microformats
#tantekshepazu: somehow mapping the data model to indicators in HTML
#tantekshepazu: this is basically LDP with some bits bolted on
#bblfishcwebber: > we've been asking for help from SoLID this whole time < yes, I am interested in helping but only if I get more support. I am not interested in working for free for nothing.
#tantekshepazu: main difference is that LDP has a should re: default no accept headers is sent, it should be turtle, we are saying JSONLD instead with a MUST
#rhiarobblfish, those of us who are contributing are doing so because we care about a particular technology and working for convergence, all of us 'working for free' currently
#tantekshepazu: we're about to publish that, the annotation protocol, probably next week, as a first public WD
#tantekshepazu: the 3rd thing is the range finder API
#rhiaroIt sounds like you're worried about people arbitrarily ignoring your contributions
#rhiaroFor me, and others, the result we want is interoperable decentralised social web systems, one way or another. Not the elevation of a particular technology.
#bblfishLook as sandro and Harry said its a question of how one invests one's time. If Sandro and Arnaud are not here interested in working on this document, and Tantek says its not really important that anything be ready by next F2F, then one has to consider the possibility that the work they have given you is just a political game to make people do something that the group does not really want to invest in. Now I can invest my time just doing SoLiD o
#bblfishr working with a group that does not really want to work together. So I am happy to find how these things can work together, but without support I am not sure how much time I should put into this. Sandro thinks any time put into this document is too much of his time.
#bblfishI mean I can also sit back and agree with "whatever consensus the working group comes to".
#harryLots of people in this group are working together productively, but everyone has time constraints. I would try to be more polite next time and have these kinds of conversations in private.
#bblfishLook sandro wrote above: "sandro: bblfish, don't count on me for that"
#rhiarobblfish: Nobody is demanding you help out. If you don't have time, just say so as others have. You can still follow the group without working on the spec
#rhiaroWe just have a general call for help with SoLiD, it doesn't matter particularly *who* helps
#bblfishrhiaro: yes, I understand. I am trying to find others who back supporting that document, that is who are willing to invest time in it.
melvster joined the channel
#melvsterharry: what happens if the works draft isnt ready by the F2F?
#melvsterrhiaro: I can make some minor edits just reading thru the page
#melvsterrhiaro: just a stylistic question 'We are not trying to re-standardize identity on the web' -- why RE standardize, is the implication that identity is *already* standardized someplace?
#rhiaroOh you're reading a different doc to the one I thought
#melvsterif that's a question, a webid isnt tied to foaf, it could be a schema.org Person, a facebook ogp person or any other type of agent (agent being the super class of people and bots)
#melvsterin the webid+tls spec foaf:agent is used I think in the range of some of the vocab classes, bblfish will know better, tho there's not a real need to be that specific
#melvstertl;dr to answer the question, SoLiD can accept any type of person URI for identity
#melvsterrhiaro: re: the content reading and writing, it's quite difficult to compare SoLiD to an API ... because in SoLiD, just like the web, *any* page can be a resource for reading or for writing ...
#melvsterfor example when im getting the latest posts I go
#melvsteraaronpk: it was a proposed system (by timbl) to say that a page returns content, but also has links to a bigger data set, e.g. that its one page in a set, and how to get to the other content
#melvsterpagination is only one way to organize data
#aaronpkmelvster: I should point out that my "pagination" is not actually done by page number, but by absolute offsets, so the contents of my pages never change
#melvsterfor inspiration on streams of json, activity, windowing and complex event processing, I find https://geteventstore.com/ interesting
#tantekmelvster: up to each indieweb person and their site - if having a concept of inbox/outbox is an itch they want to scratch then they might look into it.
#tantekhowever, as aaronpk said, for current indieweb sites, there's no need for a separate inbox/outbox abstraction.
#tantekas webmention endpoint / homepage h-feed already satisfy the needs
#melvstertantek: yes SoLiD is the same way, *but* we could implement inbox/outbox if it was a requirement of the spec
#oshepherdaaronpk: pump.io does rel=next/prev (encoded in JSON links collection) pagination of its' collections too
#oshepherdI think for ActivityPump/ActivityStreams I prefer rel=next/prev as link headers as it removes "representation metadata" from the actual content
almereyda, tantek, harry, jasnell and melvster joined the channel
#tantekmelvster - the difference is that indieweb folks implement stuff because they're scratching a personal practical itch, not because "if it was a requirement of the spec"
#melvstertantek: yeah that's one thing i really like about indieweb, but if the w3c comes out with a social spec, I'll probably implement it, assuming I dont have to drop something else
#melvstertantek: pretty much everything I implement is scratching an itch, just stuff that I found no place else so I just thought, OK, I'll build it myself
#melvsterweb 2.0 can get you 80% of what you need, but it's that 20% that hurts me
#melvstertantek: in fact the web itself was a 'scratching an itch' project
#tantekright - which is why I think any specs the W3C develops, social or otherwise, ought to also be scratching very specific itches, or rather based on what has been *proven* by people/implementers scratching their own itches
#tantekinstead of the classic spec model of political aspirational consensus first, implementation second
#melvstertantek: I hear what you are a saying, but I think you may be jaded from listening to opinionated people without implementation experience
#tanteknot jaded, but rather emboldened, by finding that working with implementers you can get things done, even semi-independently, without having to worry about armchair architects that don't actually build or ship anything ever
#melvstertantek: I generally agree, but I dont take such an extreme position. There some people with great knowledge, that you can learn lots from even if they are not coding day in and day out.
#tantekgreat knowledge rarely exists in the absence of great (implementation) experience
#tantekthat being said, we can learn from anyone who has an itch
#tantekwhether or not they can or do scratch it themselves
#melvstertankek: i used to run a fantasy football forum ... everyone has an opinion but most people never will anything and will never win anything ... some people say 10%-20% have consistently good opinions, thats rare, you learn to listen to them ... most of the time this correlates well with good results back and forward ... from working on the web I do think implementation experience counts for a lot, but maybe not 100% more like 80% in my book
#melvsteron the web the other part is that you need to scale
#melvstertantek: you need a good architecture to scale, then it comes with iteration ... there are many many examples of systems that dont scale, the web is a RARE exception
#tantekno you need iteration to scale. you never hear about the prematurely overarchitected solutions that never ship or are too cumbersome for the simple initial use-cases to get any uptake.
#tantekwhat scales is what first succeeds, then rapidly iterates.
#tanteksuccefuly sclaing architectures are evolved, not designed 100% a priori
#tantekHTML, HTTP, and URL being prime examples, as opposed to all the massively overarchitected hypertext system designs that preceded them