Skip to content

Conversation

@jnurthen
Copy link
Member

@jnurthen jnurthen commented Sep 28, 2019

closes #672


Preview | Diff

@marcoscaceres
Copy link
Member

this is insufficient to close #672, I think... the PR would need to remove all mentions of RDF throughout the spec.

@marcoscaceres
Copy link
Member

Thanks for continuing to push forward on this @jnurthen!

@joanmarie joanmarie self-requested a review October 2, 2019 15:51
Copy link
Contributor

@joanmarie joanmarie left a 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!

@michael-n-cooper michael-n-cooper self-requested a review October 3, 2019 17:56
Copy link
Contributor

@mcking65 mcking65 left a 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>
Copy link
Contributor

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.

Copy link
Member Author

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>
Copy link
Contributor

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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Logged #1096

jnurthen and others added 4 commits October 11, 2019 19:26
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>
@jnurthen jnurthen requested a review from mcking65 October 12, 2019 02:40
@jnurthen
Copy link
Member Author

@mcking65 please re-review

Copy link
Member

@michael-n-cooper michael-n-cooper left a 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:

  1. 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.
  2. 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.

Copy link
Contributor

@mcking65 mcking65 left a 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.

@jnurthen jnurthen merged commit 8e0df90 into master Oct 21, 2019
jnurthen added a commit that referenced this pull request Oct 21, 2019
* Remove RDF References
* change example from directory
@jnurthen jnurthen deleted the Remove-RDF-file-reference branch November 8, 2019 00:00
carmacleod pushed a commit that referenced this pull request May 7, 2020
* Remove RDF References
* change example from directory
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RDF model still useful?

6 participants