Re: [svgwg] Building a schema for SVG / Creating an SVG profile for IEC 61850-6-2 (#699)

Hi Dustin,

A belated response to your questions from February (sorry for the lack of response at the time), then I'll try to follow up with a review of the SVG aspects of your draft spec:

1. _When do you expect SVG2.0 to be an official w3c recommendation?_

   I don't think we can give a firm guarantee. We were hoping for this year, but the working group is very short-staffed & hasn't made much headway on the test suite, which (along with two passing implementations for each test) is a requirement for recommendation status.

2. _Do you believe the SVG2.0 is stable/mature enough for us to define an SVG2.0 schema?_

   I don't expect anything to change in the spec that would affect the schema.  Ongoing edits to the spec are likely to focus on rendering details and behavior of the DOM APIs.

   I can say with confidence that no new elements or attributes are going to be added to SVG 2.0. It is _unlikely_ that elements or attributes will be removed from the current spec text; we have already deferred most features that don't have the needed implementations. However, there may still be removals of some of the advanced text styling features, and a few other new styling properties/values, if we don't get any browser implementations of them.

3. _When do you expect the test suites/conformance testing requirements to be available?_

   Some time this year… I hope. Tests will be added (to the [WPT repository](https://github.com/web-platform-tests/wpt/tree/master/svg)) bit by bit, I don't expect a big official release date. When SVG 2 progresses to Proposed Rec / Recommendation status, that will indicate that we think we have enough tests for _new_ features (comparing SVG 2 vs SVG 1.1), but we are all also aware that SVG 1.1 tests are lacking.

4. _When can we expect browsers to claim support for SVG2.0?_

   Browser teams are mostly focused on the living standard / continuous integration model, and don't make claims about support for particular spec versions. However, they are regularly tested against the current web platform tests suite; results of the latest runs are on the [wpt.fyi site](https://wpt.fyi/results/svg?label=experimental&label=master&aligned).

5. _Are there any volunteers to assist us in defining the SVG2.0 schema?_

   I know the core team members are having a hard time finding time even for spec editing and test suite work, so I don't think we'll be likely to participate beyond this issue.

   But I updated the issue title in case some other people who watch this repo might be interested.

6. _Do you have stability dates (how long standard will enforced) in mind for SVG2.0? So when will SVG1.1 be deprecated?_

   Web standards aren't “enforced” in any way, so there is no guaranteed stability timeline. Browsers currently implement a mix of SVG 1.1 and SVG 2.0, and do not respect any `version` attribute in documents. SVG1.1 will probably be marked as [superseded](https://www.w3.org/2016/11/obsoleting-rescinding/) once SVG 2.0 is declared a recommendation.

-- 
GitHub Notification of comment by AmeliaBR
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/699#issuecomment-630964431 using your GitHub account

Received on Tuesday, 19 May 2020 17:25:20 UTC