W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2012

[Bug 15399] New: [XP3.0] Conflict between EQName syntax and JSON

From: <bugzilla@jessica.w3.org>
Date: Tue, 03 Jan 2012 10:00:45 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-15399-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15399

           Summary: [XP3.0] Conflict between EQName syntax and JSON
           Product: XPath / XQuery / XSLT
           Version: Member-only Editors Drafts
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XPath 3.0
        AssignedTo: jonathan.robie@gmail.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


For an XPath/XQuery release after 3.0, there is discussion about supporting
maps, and one of the proposals is to support maps using a JSON-like syntax. For
example a map constructor might take the form

{ "colour":white,
  "size":large,
  "weight":heavy
}


The current syntax for EQNames, for example "foo":bar, will create usability
problems if we do this, as it will be necessary to use spaces around the colon
for disambiguation.

This bug report suggests that in the interests of keeping our options open, we
should use a different syntax for EQNames. EQNames are intended primarily for
use in software-generated code, and their readability is not of paramount
importance.

We should reconsider the original proposal to use a backtick (`foo`:bar) .

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 3 January 2012 10:00:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:47 UTC