Where even are any of the values in this format defined? The DOAP link in the proto XEP just links to a giant blob of XML which is not useful.
Every time I go through trying to create one of these I end up with a million questions that I can't actually get answers to. This format is not that widely used and isn't actually useful. Just as a quick example, if I wanted to set the <os> property that I see used in the example, what are the valid values? Or is it text? Can I have multiple of them? Are they comma separated, or multiple elements? etc. None of that is defined by this XEP, and I don't know where I would even start to find out. On Wed, Jan 13, 2021, at 20:27, Matthew Wild wrote: > On Wed, 13 Jan 2021, 19:43 Sam Whited, <[email protected]> wrote: > > I do not believe this is an appropriate technology whether it's an > > existing specification or not. It's just too complicated. > > It's really not. It's also easy to generate, so feel free to have a > different canonical format for your projects (a Lua DSL does tempt me, > personally...). > > But for external tools to collect and gather data from an array of > projects, DOAP is the existing standard interchange format for this > kind of data and we should use it. > > The alternative is some custom format that we will need to bikeshed, > document, version and maintain. I'm not keen on it. > > Regards, Matthew > _______________________________________________ > Standards mailing list Info: > https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: Standards- > [email protected] > _______________________________________________ > -- Sam Whited _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
