[Bug 26649] New: [XSLT30] EBNF for package-version and package version range syntax

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26649

            Bug ID: 26649
           Summary: [XSLT30] EBNF for package-version and package version
                    range syntax
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org

First reported by mail in
https://lists.w3.org/Archives/Member/w3c-xsl-wg/2014Aug/0009.html (member
only), recreated here for trackability.

Partial copy from that mail, only covering the actual proposal:

(where I use angle brackets, it is defined in XPath).

Syntax for version (xsl:package/@package-version):

PackageVersion   ::= NumericVersion ("-" VersionNamedPart)?
VersionNamedPart ::= <NCName>
NumericVersion   ::= <IntegerLiteral> ("." <IntegerLiteral>)*

Syntax for version ranges (xsl:use-package/@package-version):

PackageVersionRange ::= AnyVersion | VersionRanges
AnyVersion          ::= "*"
VersionRanges       ::= VersionRange (<S>? "," <S>? VersionRange)*
VersionRange        ::= (PackageVersion? <S> "to" <S>)? SingleVersionRange
SingleVersionRange  ::= PackageVersion | VersionGreater | VersionComponent
VersionGreater      ::= PackageVersion "+"
VersionComponent    ::= PackageVersion ".*"

Inasmuch as I could verify by hand, the syntax above matches the syntax in the
specification, with one exception, the EBNF allows for "1.2 to 3.4+", which is
currently not allowed by the spec (it only allows "1.2 to 3.4" or "1.2 to
3.4.*"). But I don't think this change is bad per se, I even think it is more
consistent.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Sunday, 24 August 2014 13:57:40 UTC