- From: Michael[tm] Smith via GitHub <sysbot+gh@w3.org>
- Date: Mon, 21 Sep 2020 14:29:13 +0000
- To: public-svg-issues@w3.org
> @sideshowbarker Our Taskforce has noticed the following observations with regards to your Schema. It’s not my schema. It was just copied straight from https://www.w3.org/Graphics/SVG/1.1/rng/ and the lightly modified. > RelaxNG seems to be in the same immature state as the SVG11 XML schema from Chris I don’t know what you mean by “immature state” but whatever “SVG11 XML schema from Chris” is, it sounds like it might be the same thing as https://www.w3.org/Graphics/SVG/1.1/rng/ — and if so, it’s unsurprising it’s in the same state. > Specifically, there are very few restrictions on attributes, most are typed as just “string”. If that’s the case, then I guess I would wonder whether the spec actually clearly sets any further restrictions on them other than just “string”. But it’s not useful to have any discussion about it in the abstract. If there are specific cases where the spec clearly says some particular attribute should be datatyped as more than just “string”, then that’s something tangible which we could have a productive discussion about. > RelaxNG has no way to express linkages between sections. I don’t know what “express linkages between sections” means, or whether any schema languages other than RelaxNG provide some way to “express linkages between sections”. > As a simple example, in SCL there is a validated linkage between the LNs in the section elements and the LNodeType in the DataTypeTemplate section. These use xs:key and xs:keyref as well as xs:unique I don’t know what LNs or LNodeType are, or what value there is in validating linkages between them. But whatever it is, it doesn’t sound like anything that’s part of SVG. So it’s unclear to me what relevance it has to the discussion about a schema for SVG validation. > The SVG11 RelaxNG files (in validator-master\schema\svg11) are missing at least “aria” definitions which inhibits my attempt to perform a translation from the RNC files to XML schema (XSD). Whatever checking the https://github.com/validator/validator/tree/master/schema/svg11 is doing for restrictions on how ARIA attributes can be used is based on the normative requirements in the https://w3c.github.io/html-aria/ spec. Is there a some other specification that normatively defines restrictions on how ARIA attributes can be used in SVG? > I could not figure out exactly what is missing but the following error messages are emited by “trang”: > > svg-basic-structure.rnc:299:9: error: reference to undefined pattern "common.attrs.aria" > svg-basic-structure.rnc:178:10: error: reference to undefined pattern "common.attrs.aria.role.application" > svg-basic-structure.rnc:179:13: error: reference to undefined pattern "common.attrs.aria.landmark.document" > svg-basic-structure.rnc:180:13: error: reference to undefined pattern "common.attrs.aria.role.img" > svg-basic-structure.rnc:229:10: error: reference to undefined pattern "common.attrs.aria.implicit.group" > svg-hyperlink.rnc:66:10: error: reference to undefined pattern "common.attrs.aria.implicit.link" > svg-image.rnc:51:10: error: reference to undefined pattern "common.attrs.aria.implicit.img" That’s because the https://github.com/validator/validator/tree/master/schema/svg11 schema isn’t intended to be used outside the context of the HTML checker. The modifications I made to it use hooks that aren’t going to be exposed without the schema being integrated in the HTML schema that the checker uses. -- GitHub Notification of comment by sideshowbarker Please view or discuss this issue at https://github.com/w3c/svgwg/issues/699#issuecomment-696153071 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 21 September 2020 14:29:15 UTC