Closed clapierre closed 1 year ago
@iherman do you know why the ash-nazg error thing says @clapierre needs to join the schema.org CG? He's part of the CG for this vocabulary and an admin.
I can't make a comment on a paragraph before some of these changes, so I'm going to open a pull request on this pull request to suggest a few changes... 😄
@iherman do you know why the ash-nazg error thing says @clapierre needs to join the schema.org CG? He's part of the CG for this vocabulary and an admin.
I have already seen this, and I have no idea. I usually approve these PR-s for this reasons (and this is a CG).
cc @deniak @plehegar @dontcallmedom or whoever handles this service these days...?
ash-nazg still had the repository linked to the schema.org CG. When @iherman updated the reference a while ago, the repository manager was not updated automatically. I just did it and the IPR check passes now.
ash-nazg still had the repository linked to the schema.org CG. When @iherman updated the reference a while ago, the repository manager was not updated automatically. I just did it and the IPR check passes now.
Thanks a lot, @deniak !
Thanks @deniak!
Looks great Matt, @gregoriopellegrino & @madeleinerothberg Do you all agree this works for you with Matt's changes. I think its a big improvement.
I'm going to merge this and then fix any conflicts with the i18n request. I should then be able to get these published. I'm going to get the crosswalk published through the official w3c process this time.
Great for me, thank you!
In addition to adding the individual "unknown" options.
I notice an error with the noFlashingHazard's description which was a copy/paste from the Flashing Hazard section.
Also added some recommendation for the use of "unknown" and "none" to be used instead of the equivalent 3 separate values.
Preview | Diff