-
Notifications
You must be signed in to change notification settings - Fork 137
remove reference to taxonomy File #1070
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
this is insufficient to close #672, I think... the PR would need to remove all mentions of RDF throughout the spec. |
|
Thanks for continuing to push forward on this @jnurthen! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly editorial suggestions here. However, I do have some concern with the language on line 410 that specifies how inheritance works.
| <li>references to related concepts in other specifications;</li> | ||
| <li>use of <abbr title="Web Ontology Language">OWL</abbr> to provide a type hierarchy allowing for <a>semantic</a> inheritance (similar to a <a>class</a> hierarchy); and</li> | ||
| <li>supported <a>states</a> and <a>properties</a> for each role (e.g., a <rref>checkbox</rref> supports being checked via <sref>aria-checked</sref>).</li> | ||
| </ul> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unrelated to this PR, but this list is oddly incomplete.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Logged #1095
| <dd>rdfs:subClassOf</dd> | ||
| </dl> | ||
| <p>The <a>role</a> that the current subclassed role extends in the <a>taxonomy</a>. This extension causes all the properties and constraints of the superclass role to propagate to the subclass role. Other than well known stable specifications, inheritance may be restricted to items defined inside this specification, so that external items cannot be changed and affect inherited <a>classes</a>.</p> | ||
| <p>The <a>role</a> that the current subclassed role extends in the Roles Model. This extension causes all the properties and constraints of the superclass role to propagate to the subclass role. Other than well known stable specifications, inheritance may be restricted to items defined inside this specification, so that external items cannot be changed and affect inherited <a>classes</a>.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it all constraints? Unsure of this. Example, naming constraints are not inherrited. Default values are not inherrited.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Logged #1096
Co-Authored-By: Matt King <a11yThinker@Gmail.com>
Co-Authored-By: Matt King <a11yThinker@Gmail.com>
Co-Authored-By: Matt King <a11yThinker@Gmail.com>
Co-Authored-By: Matt King <a11yThinker@Gmail.com>
|
@mcking65 please re-review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't object to merging in this in its current state. There are a couple things I noticed which might merit addressing before merging, but which could also wait for later work:
- There is a retained reference to "XHTML" which I think makes less sense to keep given the other changes in this pull request, as it has less context than ever.
- Much of the edits involve replacing "RDF Taxonomy" with "Roles Model". However, I think the roles model isn't well introduced. Perhaps the RDF Taxonomy wasn't either, but there was some inherent understanding via the reference to RDF. Without that, new readers wouldn't understand the structure we're using. So an introductory paragraph in the top of the Roles Model section might help contextualize later uses of the term.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Thanks for opening the additional issues.
* Remove RDF References * change example from directory
* Remove RDF References * change example from directory
closes #672
Preview | Diff