XSF Discussion - 2018-07-14

  1. daniel

    Why does 156 have a XML and a json lookup mechanism for http. But only the XML is MUST. This leads to all web clients having to support the XML variant (even though the json variant might be easier to implemted). But if all web clients have to implemte the XML variant anyway why bother implementing the json variant?

  2. SamWhited

    I think servers have to support xml, not clients, right? So a client could only work with servers that support json

  3. SamWhited

    But I agree, it seems pointless.

  4. SamWhited

    > As specified in RFC 6120 §3, support for the XML encoding of the host-meta resource is REQUIRED while alternative representations such as JSON are OPTIONAL.

  5. SamWhited

    No idea what that's on about… this isn't mentioned in 6120 as far as I see.

  6. daniel

    Typo probably. They mean 6415

  7. daniel

    Paragraph 3 sort of matches that I guess

  8. SamWhited

    ah yah, that makes sense. 6120 section 3 is where you would expect this to be, amusingly

  9. Zash

    pubsub#include_body pubsub#show-values

  10. Zash

    nice and consistent