Re: [dxwg] property profileOfTransitive

Perhaps the idea is that a specification might include more than simply the constraints. The term constraints is  a little tricky.  Following the modular specification logic, its useful to think of a specification in terms of requirements and conformance classes.  Most existing specs only explicitly define one conformance class--meets all requirements, and this typically is about some specific implementation/serialization/syntax. Usually there are some requirements stated using the standard  RFC2119 language, but often there is an underlying implicit conceptual or logical model that establishes unstated requirements as well. Perhaps one of the problems with thinking about profiles is that they might conform to implicit requirements (conceptual or logical), but not the explicit one.

As far as transitivity, can we define different relations (names are for discussion purposes here). A and B are specifications; since multiple conformance classes are rarely defined, these are based on requirements. For example:
1. isType1ProfileOf -- if A isType1ProfileOf B, then instances of A meet ALL requirements in B, and requirements in A are all restrictions of requirements in B.
2. isType2ProfileOf -- if A isType2ProfileOf B, then instances of A meet a subset of requirements in B,  and requirements in A are all restrictions of requirements in B.
3. isType3ProfileOf -- if A isType3ProfileOf B, then instances of A meet ALL requirements in B, and  A adds additional requirements from other specifications that are not incompatible with B.
4. isType4ProfileOf -- if A isType4ProfileOf B,  then instances of A meet a subset of requirements in B,  and  A adds additional requirements from other specifications that are not incompatible with B.
5. isType5ProfileOf -- if A isType5ProfileOf B,  then instances of A meet a subset of requirements in B,  and  A adds additional requirements from other specifications that may be incompatible with B.
6. uses -- if A uses B, then instances of A meet one or more requirements of B. This is a generic statement that would subsume the other relations (above) 

The transitivity rules could be constructed here, but they're tricky.  
If A isType1ProfileOf B and B isType1ProfileOf C then A isType1ProfileOf C, is true.

If A isType1ProfileOf B and B isType4ProfileOf C then A isType4ProfileOf C is true...

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

Received on Thursday, 1 November 2018 17:46:25 UTC