Stream: implementers
Topic: Client Conformance
Rik Smithies (May 17 2016 at 17:55):
How does this work? Does the server call back to the client to read its Conformance? Or does the client somehow post it to the server?
Grahame Grieve (May 17 2016 at 19:36):
at the moment, the client does not communicate it's conformance statement to the server .
Grahame Grieve (May 17 2016 at 19:36):
what would it do with it?
James Agnew (May 17 2016 at 19:38):
I could see a world one day down the road where an app/client might provide a conformance statement to declare that it conforms to specific profiles (say, US DAF or SMART-CA or whatever) as a part of being published on an app gallery.... The gallery could then tailor itself based on the profiles that a given organization/server/jurisdiction/whatever are able to support
Grahame Grieve (May 17 2016 at 19:39):
yes. that's what client conformance is for - app registrys
Ewout Kramer (May 19 2016 at 09:10):
And we have also discussed having an operation that the client can invoke (say, $conforms-to), sending the client conformance "requirements" as a conformance statement. The server can then do the heavy lifting, comparing the conformance statement and returning to the client whether the stuff the client conformance statement requires are all supported. Good stuff for one of our or your students to figure out....
Grahame Grieve (May 19 2016 at 21:14):
I think you and I might have to work that out first
Michael Lawley (May 23 2016 at 06:45):
Yes, I was wondering about using client conformance to check that a server supports everything my client wants to do.
Last updated: Apr 12 2022 at 19:14 UTC
