Re: [dxwg] Differentiating Functional & Data Profiling in Conneg (#1022)

@agreiner @kcoyle @rob-metalinkage @nicholascar let me try to recap the current proposal for keeping functional profiles in a way that would minimize confusion (copying and slight re-wording material from previous comments):
1. keep our notion of "data profile" in the definitions and clearly present data profiles as the profiles that are the object of content negotiation
2. make sure that _every_ reference to functional profiles in the document is spelled out as "functional profile" and not "profile", leaving the shorter form usable for the references to "data profile". 
3. not try to present a complete, unifying framework, which again is not needed for the document to work. If a generalization is offered to readers it should be done only in the lightest manner: i.e. in the "definitions" section, there could be a generalized definition for "profile" (the one currently in the editor's draft is close enough to the one of "data profile" that it won't be objected to, hopefully) and maybe a definition for "functional profile" (which I think could be a job for a PR, i.e. after CR). These would sit next to a definition of "data profile", not replacing it.
4. putting the section on functional profiles (currently 2.1) further down in the document, i.e. in the opening of the current section 7.  And section 2 on conformance would refer to the new subsection of section 7 instead of presenting functional profiles itself. 

I am aware that form of support for some of these elements has already been voiced, and reluctance to some of them has been voiced too. But this has happened in different comments or even outside of github. Hopefully putting everything here will help make all that visible and progress towards a solution.

-- 
GitHub Notification of comment by aisaac
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1022#issuecomment-534749144 using your GitHub account

Received on Tuesday, 24 September 2019 21:08:57 UTC