- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Wed, 01 Oct 2025 07:46:31 +0900
- To: Jim Barnett <1jhbarnett@gmail.com>, Bento Borges Schirmer <bbschirmer@inf.ufsm.br>
- Cc: www-voice@w3.org, plh@w3.org
Hi Bento and Jim, adding Philippe to CC I talked with Philippe Le Hegaret, the W3C VP, Technical Strategy, about how to handle the bug reports for SCXML again, and our suggestion is creating a dedicated GitHub repository to maintain the SCXML specification: https://www.w3.org/TR/2015/REC-scxml-20150901/ and its Errata document: https://www.w3.org/2015/08/scxml-errata.html As you might know, the latest W3C Process Document: https://www.w3.org/policies/process/#no-group-maintenance let the W3C Team maintain the specification depending on the level of bugs/fixes if there is no WG any more. So we've created a dedicated GitHub repository: https://github.com/w3c/scxml based on the original contents on the W3C CVS server: https://www.w3.org/Voice/Group/2005/HST/ to maintain the SCXML spec and its errata document. For further discussion/fixes, please use the above GitHub repository. For example, you can create a GitHub Issue to point to the existing bugs being discussed on the www-voice list. Thanks, Kazuyuki On Thu, 11 Sep 2025 18:49:29 +0900, Kazuyuki Ashimura wrote: > > Hi Bento and Jim, > > Thanks a lot for finding the issues, Bento! > And thank you for your response as the (former) main Editor of the spec, Jim! > > It seems to me that we should fix two typos within the SCXML > Recommendation: > https://www.w3.org/TR/2015/REC-scxml-20150901/ > > If that is what we should do, I'd like to talk within the W3C Team > to clarify what we can do. > > Thanks, > > Kazuyuki > > > On Tue, 09 Sep 2025 06:41:41 +0900, > Jim Barnett wrote: > > > > Thank you for raising these issues. The working group that produced SCXML has been closed, so there is no way to update any of the documents. The only option is to post problems/comments here, and hope that other developers and users will see them. > > Jim > > > > > On Sep 8, 2025, at 11:30 AM, Bento Borges Schirmer <bbschirmer@inf.ufsm.br> wrote: > > > > > > Hey fellas, > > > > > > I'm writing a SCXML parser, and learning some XML along the way. I > > > noticed two problems I will detail shortly. > > > > > > I'm referring to this version: > > > https://www.w3.org/TR/2015/REC-scxml-20150901/ > > > And I'm also referring to this version: > > > https://www.w3.org/2011/04/SCXML/scxml-datatypes.xsd > > > Both are current at the time of writing. > > > > > > Problem 1: https://www.w3.org/TR/2015/REC-scxml-20150901/#N103BF > > > > > > At the section 3.5.1 "Attribute Details" containing a table of > > > attributes for <transition>, it states that the type of the attribute > > > "event" is EventsTypes.datatype. I believe the correct type is > > > EventTypes.datatype, i.e. without an "s" after "Event". > > > > > > Problem 2: https://www.w3.org/TR/2015/REC-scxml-20150901/#EventDescriptors > > > > > > In the fifth paragraph of the section 3.12.1 "Event Descriptors", it states: > > > > > > "Note that a transition with 'event' of 'error', one with 'error.', > > > and one with 'error.*' are functionally equivalent". > > > > > > However, the <xsd:pattern> for both EventType.datatype and > > > EventTypes.datatype preclude a trailing period. > > > > > > Best regards, > > > Bento Borges Schirmer > > > > > > > > > > >
Received on Tuesday, 30 September 2025 22:46:37 UTC