#ajordancwebber2: nightpool you were asking what's first on the agenda; since you weren't here we actually started with the AS2 extension teminology. the second one
#ajordan... this is very helpful; one thing I'm noticing about this is that there are a lot more extensions than I was anticipating which is good, I guess
#ajordan... what I'm wondering is, are they being embedded with every object that's sent across the wire or are they being linked to as contexts that you retrieve?
#ajordannightpool: kroeg and hubzilla do the former, plemora/mastadon/??? do the latter
#ajordancwebber2: it's useful to know that there's a mix of both
#ajordancwebber2: so eprodrom have you looked adt this list? I wonder what your thoughts are since there are a bunch of items we haven't even discussed making extensions yet
#ajordan... I have different feelings on different things on here
#ajordan... some of them are interesting... a lot of this is just redefining AS2 stuff, hashtag etc.
#ajordan... others are interesting in that they're mixing in well-known vocabularies, schema.org is in here
#ajordan... that one's interesting in that, should we make that available right in the context
#ajordan... just add in schema.org, vcard, etc. to save a couple lines in here
#ajordan... it's a little bit of a permission, suggestion, guidance
#ajordan... there are some that are clearly experimental or focused on the particular implementation
#ajordan... I take the Mastadon namespace as one there
#ajordan... it's probably a good idea to not fish too far into ones that are clearly experimental or implementation-focused and instead kinda let those bubble up as they become more used across system
#ajordan... looks like the mastadon one *is* being used across systems so I'd love to see what those elements are
#nightpoolq+ to talk about "redefining as namespaces"
#ajordan... but I think more focused specific ones should live in their own systems
#ajordan... and let me also say this is the first time I'm looking at this so it's just impressions
#ajordan... cwebber2 I wonder if there's a mechanism we could provide as a way of defining extensions
#ajordan... like, I am working on an AS system and I've created a set of things around role playing games and I'd like to create a namespace that's like socialcg:rpg to start experimenting in
#ajordan... and we could give a nod to that and say here's a namespace
#ajordan... and then people could start building on that so we have a mechanism for people to start experimenting in
#nightpool(reminder that the w3 wiki is not editable by community group members, only WG members)
#ajordan... and then we can discuss bringing them into the main as namespace if they have a lot of implementations, getting them in the context , etc.
#ajordancwebber2: I think we're retreading some conversations we had without any of the AS2 editors present which was a mistake
#ajordan... I think last time we agreed that the AS2 Git repository and issue tracker was where we were discussing pulling in extensions
#ajordaneprodrom: that makes a lot of sense, absolutely, and I think that namespacing...
#ajordan... in this gist you've got there's personal URLs for namespaces
#ajordan... if I look at this I'm not gonna say that looks like the W3C people are experimenting with a new namespace for conversations
#ajordan... what I see is there's a guy named ??? and he's experimenting with nomadic locations
#ajordan... I think there's some value in using a namespace that carries some infor
#ajordancwebber2: my impression was that last time we decided to keep stuff in a repo but maybe I'm wrong
#ajordannightpool: I think we made that decision based on the fact that W3C wiki isn't editable by non-members anymore
#ajordancwebber2: the systems team has said that's what's happened
#ajordaneprodrom: can we enable the wiki on GitHub?
#ajordancwebber2: we could, I'm not against this, but part of the argument for issues/PRs was that it would be a work flow we're familiar with as developers
#ajordan... it sounds like we don't have a resolution on this but I want to switch to nightpool
#ajordannightpool: yeah so summarizing the ostatus thing Mastadon switched from ostatus to AP and we needed some context terms
#ajordan... so e.g. if we got an edit for an ostatus post we had to associate that with the original ostatus URL
#ajordan... the ostatus:conversation is something we're seeing people using even if they didn't do an ostatus migration because it lets you associate posts in a thread
#ajordan... that's something that maybe needs rescuing from the ostatus namespace and put somewhere else
#ajordaneprodrom: that makes sense, I'm capturing in an issue
#ajordan... I can think of a couple of existing terms that might fit there but none that are specific for "conversation"
#ajordan... it's really only important if you're doing massively hierarchical threading, just being able to link things up to the original post
#ajordan... if you're doing flatter threading it's less important
#ajordan... it's something we dropped going from statusnet -> pump.io, we had massive hierarchical threading in statusnet and most of the ux suggestions right now are "don't do that"f
#ajordan... I want to come back to cwebber2's question, there's kinda three rings
#ajordan... outer ring is per-implementation, very niche
#nightpoolzot:nomadicHubs is an example here, I think
#ajordan... I think there's a next ring in, stuff that might have multiple implementations, where we may want to have a way of defining namespaces for those
#ajordan... socialcg:voicechat, socialcg: different kinds of subnamespaces
#ajordan... that might be useful for people to start working together and collaborating on
#nightpooltoot:Emoji or as:manuallyApprovesFollowers is probably an example for the middle ring
#ajordan... and then a last kind of inner ring for things that are going to be part of the as namespace
#cwebber2q+ to ask for where these socialcg-* namespaces live, also if terms *can* move in
#ajordan... and we agreed to put extensions in the as namespace eventually
#ajordan... and I think things would move through those rings
#nightpooland as:sensitive sounds like an example of something that's pretty solidly in the inner ring.
#ajordan... we have a wiki page listing extensions, I think that would get us pretty far
#ajordancwebber2: okay I think I'm next on the queue
#ajordan... so for where the socialcg namespaces live I'm guessing you're saying they're not necessarily a subnamespace of as2 right?
#ajordaneprodrom: that might be a good way to do it actually
#ajordancwebber2: I think one of the condcwerns that sandro had is that it can be very hard to get terms to migrate
#ajordan... once people are used to terms being in a specific location it's kinda hard to update code to alias it and not necessarily all systems will update to do that
#ajordan... and you can work on your context. then say you get multiple implementations, etc. then we can move into the main namespace
#ajordan... they'll still resolve into the same URL, but you can use the namespace or not
#ajordancwebber2: note that there's a difference between vocab locations and context locations
#ajordan... if we add stuff to the main as2 context that doesn't mean we have to change the location for the vocab
#cwebber2ajordan: since we're talking about moving things... nevermind, what I was going to say is another problem we can look at is starting to use an HTTP header, and then there's X-content-security-policy AND content-security-policy... I think that's resolved by putting things in the context and not moving the vocab itself
#cwebber2eprodrom: if it's okay with you I'll document this process, and maybe we can review it at the next meeting?
#ajordancwebber2: sure that's fine with me, nightpool sorry we took over
#ajordan... should we queue Mastadon stuff for the next meeting?
#ajordannightpool: I can go over it in like 5 minutes, it's not super important
#ajordan... the main thing is that we've added pin collections
#ajordan... it accepts add/remove from the owner and is federated out
#ajordan... we added a focal point property for images to affect where they center
#ajordan... and we've added a way for reporting statuses, if a user reports a status they can also optionally send that to a mod of another server
#ajordancwebber2: ok great so sounds like we have next steps for the first topic, eprodrom's gonna write that up, and nightpool thanks for the overview
#ajordan... they're primarily errors in examples in the vocab document
#ajordan... and one that's a typographical error in one of the property definitions
#ajordan... so I've done four PRs that add these to the errata so when you look at the errata it'll say oops there's a problem with this example, a problem with that example
#ajordan... these all come from bugs people have filed on AS2
#ajordan... since we can't actually change the docs this is the next best thing
#ajordanoh also cwebber2 at the start of the meeting I was gonna mention that FWIW I too am getting ready to move across the country and I feel your pain :P
#Loqi[evanp] So, I think there are four kinds of extensions to AS2 we'd want to track.
0. ***Established vocabularies***. These are existing vocabularies that are adapted for AS2, such as [schema.org](http://schema.org/), [vcard](https://www.w3.org/TR/vcard-rd...
#Loqi[cwebber] > Possibly add the namespaces to the AS2 context document. It's not clear what the acceptance criteria for this would be. It would work like so:
I would say it's easy enough to link in another AS2 context that's "fully formed" like this, no need ...
#Loqi[cwebber] > Possibly add the namespaces to the AS2 context document. It's not clear what the acceptance criteria for this would be. It would work like so:
I would say it's easy enough to link in another AS2 context that's "fully formed" like this, no need ...