- From: aisaac via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Sep 2019 14:03:55 +0000
- To: public-dxwg-wg@w3.org
I also would prefer if functional profiles would be called differently, but I can live with having them named like this if the document handles it well. As for definitions, I can quite comfortably live with a definition section that would include something like this: > **data profile** > A data specification that constrains, extends, combines, or provides guidance or explanation about the usage of other data specifications. > **profile** > A specification that constrains, extends, combines, or provides guidance or explanation about the usage of other specifications. > This "Content Negotiation by Profile" specification concerns negotiation for data profiles, and specifies functional profiles for different ways of achieving this. where "functional profiles" in the above would point (directly or via a pointer added to definition in the same section for functional profiles) to section 7 where they are explained. Indeed as a reader I would actually not care much about how/whether a definition is given for functional profiles. I would just want to see what they are. -- GitHub Notification of comment by aisaac Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1022#issuecomment-535039039 using your GitHub account
Received on Wednesday, 25 September 2019 14:04:06 UTC