Ge0rGNow how do I display this DOAP thing properly?
lovetox_has left
lovetox_has joined
wurstsalatLink Mauve ^
Link MauveGe0rG, what is your wanted rendering thingy?
Link MauveSomething like that? https://pulkomandy.github.io/xmpp-doap/samples/movim.xml
Ge0rGLink Mauve: yes
Link MauveSomething like that? https://linkmauve.fr/extensions/xep-0048.xml
Ge0rGLink Mauve: I've forked your xmpp-doap repo and included the style, but it doesn't show the table content
Link MauveGe0rG, then just use the linked XSLT style sheet, by viewing source.
Link MauveGe0rG, this was PulkoMandy’s.
Ge0rGLink Mauve: I can't do that on a local file :(
Link MauveMaybe it isn’t fully up to date with the latest format?
Link MauveGe0rG, oh?
Ge0rGyeah, local files are a separate security domain
Link MauveIndeed, it isn’t up to date.
Link MauveI can fix that.
ralphmhas left
Ge0rGLink Mauve: can we also get the XEP titles in there?
Ge0rGIdeally, I'd also just have `<XEP-0077/>` instead of `<xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0077.html" /><xmpp:xep rdf:resource="https://xmpp.org/extensions/xep-0077.html" />`
Link MauveGe0rG, the XEPs don’t have any semantic document thingy we could use to extract the names from.
Link MauveAlso <XEP-0077/> isn’t valid RDF.
Ge0rGLink Mauve: there used to be an XML file listing all that.
Ge0rGLink Mauve: that was a placeholder for whatever the shortest possible syntax is
Ge0rGis a proponent of zero-boilerplate
Ge0rGNo idea how I ended up with XMPP
ralphmhas joined
Link MauveGe0rG, syntax doesn’t matter here.
Link MauveSemantic web parsers already exist, and reusing one is much less work than writing a parser from scratch.
Ge0rGcloses VIM
Link MauveI had a much shorter syntax at first, but it wouldn’t be compatible with existing DOAP software.
Ge0rGSo syntax *does* matter? ;)
Ge0rGanyway, this is just minor nitpicking.
Link MauveGe0rG, I mean, shorter syntax doesn’t matter.
Ge0rGI want to get this thing going, and that means I need to render it locally
pep.Ultimately you can have something generating your doap file :p
Ge0rGLink Mauve: what would you need to allow XEP name resolution?
Ge0rGpep.: I had some*body* generate it.
pep.Ge0rG: good first step
Link MauveGe0rG, you can use xsltproc from libxslt to generate a HTML file from the CLI.
Link MauveGe0rG, hmm, a deeper understanding of how XSLT works.
Link MauveAlso since there is a Python version nowadays (see https://github.com/xsf/xmpp.org/pull/594) it could be done much easier.
Ge0rGLink Mauve: xsltproc shows the same output as chrome. Your style must be b0rken
Ge0rGI thought you had the bestest changes, but now...
Link MauveIt’s not mine, complain to PulkoMandy.
Ge0rG> Resource interpreted as Stylesheet but transferred with MIME type application/xslt+xml: "file:///usr/src/yaxim/xmpp-doap/style.xsl".
Is that bad?
Ge0rGMaybe my XML is b0rked? https://op-co.de/tmp/yaxim.doap.xml
Ge0rGah, yes it is.
Zash> The requested URL /style.xsl was not found on this server.
Ge0rGZash: it's all horrible!
ZashXSLT is pretty cool
Ge0rGbut it was <implements> instead of <xmpp:supports>
Zashhttps://xmpp.org/extensions/xep-0199.xml
Ge0rGLink Mauve: is <xmpp:version> the XEP version, and <xmpp:since> the application version?
Ge0rGThis is super-confusing.
pep.Yeah that's the semantics
pep.Suggestions?
Link MauveGe0rG, https://github.com/pulkomandy/xmpp-doap/pull/6
Link MauveGe0rG, yes, version and since have this semantic, as you can see in the OWL schema.
Link MauveGe0rG, https://linkmauve.fr/ns/xmpp-doap
Danielwhat do i need to get started with doap? is there a good sample file including style file and everything?
Link MauveDaniel, easiest would be to start from one of the ones linked from here: https://github.com/xsf/xmpp.org/pull/594
DanielLink Mauve, but that doesn’t do the rendering
pep.Board meeting with doap stuff is today right
Link MauveDaniel, rendering would be up to consumer services, such as xmpp.org, JabberFR’s wiki, some random comparison table, etc.
Danielright. i'm just looking for something that makes writing easier
Link MauveZash, hmm, the format changed to better match DOAP since then.
Danieland verify that i did everything correctly
Link MauveZash, see https://lab.louiz.org/poezio/poezio/commit/31c605528c0ad8b22d617073fb2e1722b82fabb2
ZashMeh
Link MauveDaniel, clone https://github.com/pulkomandy/xmpp-doap/pull/6, then run `cd samples; xsltproc -o conversations.html ../style.xsl conversations.xml`.
Link MauveThat’s the closest we have from a renderer.
Link MauveZash, when did you do that, and from which example?
DanielLink Mauve, thanks. that probably comes close to what i was looking for
Link MauveIf you additionally want RDF validation, https://github.com/xsf/xmpp.org/pull/594 contains a doap.py script which you can use to parse it using a real RDF parser.
Link Mauvehttps://github.com/xsf/xmpp.org/pull/594/files#diff-64332f4e20f843debc79815b0ecd6a97R81
ZashLink Mauve some week(s) ago. Dunno what it's based on, could be the translation thing I made for the old xmpp-features thing.
bhaveshsguptahas left
bhaveshsguptahas joined
MattJLink Mauve, is there any chance we can get XEP revision into there?
ZashWasn't there already?
MattJXEPs change, sometimes substantially
Link MauveMattJ, it already is there.
MattJOh
Link MauveIt’s the version property.
Link MauveFor instance here: https://pulkomandy.github.io/xmpp-doap/samples/movim.xml
Link MauveThe second column.
MattJOh yeah, it's just the Dino one I looked at didn't have it
Link MauveDaniel, maybe remove the comments affecting poezio.
Link MauveHum, like Zash you based it on an older example. :/
Danielthat's the one you linked me to
Link Mauvepoezio’s doap file is https://lab.louiz.org/poezio/poezio/blob/master/data/doap.xml
Link MauveSo hmm, as I told Zash at 13:57:10, remove the <software><Client/></software> wrapper, change xmpp:supports into doap:implements, and that should be it.
Ge0rGSo I named it .rdf, and now Chrome tells me to "Save as" the file:// URL
Ge0rGLink Mauve: I've done that, and I'm using your update branch and it doesn't render the table
Link MauveGe0rG, can you show me your DOAP file?
Ge0rGah, I took `doap:` too literally. `<implements>` did the trick
Ge0rGLink Mauve: how do we handle Compliance Suites?
Link MauveGood question.
Link MauveMaybe the same way Zash’s XMPP-Features did, by checking for complete status on the relevant XEPs?
Link MauveOr for now we could say complete and mark the profile(s) in the <note/> field.
Ge0rGLink Mauve: what about a separate RDF element?
Link MauveGe0rG, that could work, do you have something in mind?
Ge0rGLink Mauve: no, I was just asking
Danieli think it should be figured out automatically
Danielto me that's the point of having machine readable files
Link MauveDaniel, yes, indeed.
Link MauveBut which entity would be responsible of that?
Ge0rGDaniel: I agree, but it's probably more work to do the automatic figuring-out
DanielYes but only once
Ge0rGWhat if the developer has a different opinion?
Link MauveGe0rG, https://code.zash.se/xmpp-features/file/tip/compliance.lua
Link MauveThese rules are what XMPP-Features was doing.
DanielLink Mauve, does that look ok now? https://github.com/siacs/Conversations/blob/master/doap.rdf
Link MauveDaniel, yes, the structure looks good. :)
Link MauveMaybe make 0166 partial?
Danielwhy?
Link MauveYou say it’s only for file transfer.
Link MauveBut anyway it’s your call.
Danielsure but 0166 doesn’t mandate you to support a specfic application, no?
Link MauveLooks great, I’ll add this URL to my xmpp.org PR.
bhaveshsguptahas left
bhaveshsguptahas joined
bhaveshsguptahas left
bhaveshsguptahas joined
jcbrandhas left
bhaveshsguptahas left
kevinhow can i get and post requests to xmpp with postman
Ge0rGpostman is the wrong tool for the job, even though in theory you could do some weird BOSH stuff
kevinreally
kevini just want to be able to monitor http requests
Zashxmpp is not http
kevini know
kevinbut it uses http though
kevinlike 5443
ZashI don't know what you're talking about now
kevini want to be able to listen to requests on a specific port
kevinand i was told postman was the best program to use
MattJIt doesn't use HTTP, and what port it uses is not directly related to what protocol it uses
ZashYou can of course tunnel anything over everything, hence BOSH as Ge0rG mentioned.
MattJYou can do XMPP over HTTP, but most XMPP connections are not doing this (unless they are from a web browser)
ZashYou can do HTTP over XMPP as well.
Ge0rGIs there a solution yet for the F5 on Converse when running via WS?
ZashGe0rG: 198 I guess?
Ge0rGZash: we had a discussion about 0198 on anon, which doesn't work
MattJIt works fine if the server assigns the same JID to the same user
MattJwhich can be done through evil means, such as cookies
Ge0rGyou can have cookies on WS?
ZashSure
ZashThe initial handshake is a HTTP request, you can pass whatever headers or parameters there.
Ge0rGThat's evil indeed, but I'm only slightly surprised.
Ge0rGMattJ: do you have such a mechanism in prosody yet?
Ge0rGI'm using BOSH now for the webchat because of this.
MattJGe0rG, not open-source, sadly
DanielI think there is no real downside of keep using bosh for those anon cases