W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2015

[Bug 28901] [XP 3.1] Unary Lookup

From: <bugzilla@jessica.w3.org>
Date: Tue, 14 Jul 2015 21:53:47 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28901-523-WDFZaPw7kO@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28901

Jonathan Robie <jonathan.robie@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Jonathan Robie <jonathan.robie@gmail.com> ---
(In reply to Michael Kay from comment #0)

> Using nested lists to make clear the scope of the conditionals in this
> section would make it much clearer. I would be inclined to structure it as
> follows, even though this involves duplication:
> 
> 1. If the context item is a map:
> 1.1 If KeySpecifier is an NCName:
> 1.2 If KeySpecifier is an IntegerLiteral:
> 1.3 If KeySpecifier is a ParenthesizedExpr:
> 1.4 If KeySpecifier is a wildcard ("*")
> 2. If the context item is an array:
> 2.1 If KeySpecifier is an NCName: (always an error)
> 2.2 If KeySpecifier is an IntegerLiteral:
> 2.3 If KeySpecifier is a ParenthesizedExpr:
> 2.4 If KeySpecifier is a wildcard ("*"):
> 3. Otherwise (error)

That's the approach I took.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 14 July 2015 21:53:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 14 July 2015 21:53:50 UTC