- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Feb 2019 21:21:51 +0000
- To: public-dxwg-wg@w3.org
discussed in CNEG sub group 13 Fec.. action to propose some options: Option 1: Server offers a 1:1 mapping from (optional) tokens to URIs using typical "parameter" syntax - we define the parameter "token" Accept-profile: URI[;token=mytoken], Pros: self-contained,flexible, explicit. Cons: potential redundancy in URIs if many offered Option 2: tokens are registered in a global registry and servers may use them in place of a URI Accept-profile: token1, URI2 Pros: compact Cons: global registry for profiles not manageable when many systems define profiles - limits all the other capabilities of profile description by forcing generic profiles. Option 3: allow namespace declarations - like in JSON CURIE (compact URI - declare namespaces) Accept-profile: @:<namespace1>,@ns2:<namespace2, :token1, w3c:token2 Pros: compact, no registry requirement Cons: clients have more parsing to do Note: could easily be a JSON-LD payload (alternative syntax using parameter ns2;ns=<namespace2>) Option 4: add a namespace header Accept-profile-namespaces: :<namespace1>,ns2:<namespace2> Accept-profile: :token1, w3c:token2 -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/290#issuecomment-463376944 using your GitHub account
Received on Wednesday, 13 February 2019 21:21:55 UTC