- From: Michael Kay <mike@saxonica.com>
- Date: Wed, 11 Nov 2015 15:14:13 +0000
- To: Public Joint XSLT XQuery XPath <public-xsl-query@w3.org>
XML Query/XSL WG Joint Teleconference #623 Minutes 2015-11-10 SUMMARY OF DECISIONS ==================== Note to secretary: Please insert a summary of all decisions made during this teleconference at this location in the minutes. Decisions MUST be clear as to their complete intent. The subject of the decision should *not* require dereferencing; it is most helpful if agenda numbers and bug numbers are accompanied by their titles. If a decision is recorded about the resolution of a bug, the decision must state exactly what the resolution is (e.g., "Accept the solution in comment #5", or "Replace the production for XXX with this: <new production>", or the like. It should be possible to read a decision months later and be certain what it meant and whether or not it was properly applied. DECISION: resolve bug 29270 by documenting the expected behaviour that each time a node in the original sequence is serialized, if an XML declaration is requested, then you get a new one. (If you don't want that, don't ask for it). (May need to think what the precise rules are for example when a sequence of nodes appears as a value in a map.) DECISION: close bug 4378 as "works for me". DECISION: close bug 29260 as editorial, with an action on Jonathan to implement the change. DECISION: close bug 29263 as "works for me". DECISION: close bug 29264 as "won't fix". NEW ACTION ITEMS ================ Note to secretary: Please insert all new action items assigned during this teleconference at this location in the minutes. Action items MUST make sense even when they are viewed standalone (that is, not read in the context of the agenda item where they were assigned). This explicitly requires that all referents (e.g., "this", "that") be made clear. Action items such as "Ralph to resolve this problem" are DISALLOWED. It takes a scribe only a few additional minutes to ensure that action items are clear, while it takes the entire WG considerable effort to constantly research the meaning of unclear action items. The subject of the action item should *not* require dereferencing; it is most helpful if agenda numbers and bug numbers are accompanied by their titles. ACTION A-623-01 Andy to do what's needed to republish the XQuery CR. ACTION A-623-02 Andy to contact Christian Grün again about his willingness to commit effort to XQuery Update. ACTION A-623-03 on the Serialization editors to add a note to the spec explaining the decision on bug 29270 ACTION A-623-04 on the Serialization editors to make a proposal as to how bug 29272 should be resolved. ACTION A 623-05 on the Serialization editors to make a proposal as to how bug 29273 should be resolved. ACTION A-623-06 Jonathan Robie to add to the spec a note along the lines suggested by Christian in bug 29260 =================================================== Joint XML Query Working Group and XSL Working Group =================================================== J1. Administrative Items J1.1 Selection of secretary(s) Mike Kay has been asked to take the minutes. John Snelson has been asked to stand by. NOTE: The chair will confirm the secretary prior to the start of the meeting. Most recent secretaries (least-recent participants first): ---------------------------------------------------------- (This list identifies the most recent three occasions when each participant acted as Secretary for the Task Force. The person whose name is at the top of the list should plan to take the minutes at the meeting identified by this agenda; if that person is unavailable, then the job will fall to the next person on the list, etc. Mike Kay - 2015-07-15, 2015-04-14, 2015-01-06 John Snelson - 2015-07-16, 2015-06-02, 2015-02-11 Loren Cahlander - 2015-07-17, 2015-05-19, 2015-02-10 Michael Dyck - 2015-09-01, 2015-03-31, 2014-12-16 Josh Spiegel - 2015-09-08, 2015-03-24, 2014-12-09 Tim Mills - 2015-09-15, 2015-04-21, 2015-02-03 Norm Walsh - 2015-09-22, 2015-05-05, 2015-01-27 Jonathan Robie - 2015-10-29, 2015-05-12, 2015-01-13 Liam Quin - 2015-10-06, 2015-06-16, 2015-03-10 Adam Retter - 2015-10-20, 2015-04-21, 2015-01-20 O'Neil Delpratt - 2015-10-27, 2015-06-23, 2015-03-17 Michael Sprbrg-McQn - 2015-10-03, 2015-06-09, 2015-03-03 J1.2 Call the Roll -- NOT DONE DURING TELECONFERENCE Note to secretary: During the meeting, take a note of the Webex participants, then list in the minutes those present and those who sent regrets. All others will be presumed to have been absent without regrets. Roll-call: Andy Coleman, Jonathan Robie, Josh Spiegel, John Snelson, Michael Dyck, O'Neil Delpratt, Michael Kay, Tim Mills, Michael Sperberg-McQueen. XML Query WG membership list: http://www.w3.org/2000/09/dbwg/details?group=18797&order=org XSL WG membership list: http://www.w3.org/2000/09/dbwg/details?group=19552&order=org Regrets: J1.3 Approval of agenda §§ Jonathan referred to an email he was about to send... J1.3.1 Additions, deletions, or corrections? J1.4 Review of recent minutes and administrative items J1.4.1 Minutes of meeting #621 (Michael Sperberg-McQueen) https://lists.w3.org/Archives/Public/public-xsl-query/2015Nov/0011.html §§ Accepted as a true record. J1.5 Review of action items NOTE: Please be prepared to respond quickly on your action items! J1.5.1 Outstanding action items ACTION A-579-18: Jonathan to write change proposal to support update of maps and arrays. (See agenda item Q2.1.1) Status: Pending; ETA 2015-11-24 ACTION A-585-04: Jonathan to write a concrete proposal for XQuery Update 3.1 that makes preservation of node identity implementation defined at the persistence layer. See https://lists.w3.org/Archives/Member/w3c-xsl-query/2014Nov/0012.html Status: Pending; ETA 2015-11-24 ACTION A-618-01: Loren to change the schema for serialization to allow for EQNames. Status: Pending; ETA not specified. §§ no update ACTION A-619-01: Liam to add links to new mailing list onto XQuery group page Status: Pending; ETA not specified. §§ no update ACTION A-621-04: Jonathan to update the words in XQuery for empty expressions in braces Status: Pending; ETA 2015-11-10 ACTION A-622-02: Josh Spiegel to propose changes to XQueryX to support new grammar for empty expressions in braces and return to group with a proposal. Status: Pending; ETA not specified. §§ Josh has made proposals and has applied the changes locally but is asking Jim to review before sharing with the WG as a whole. Jim is on vacation. ETA 2015-11-24 ACTION A-622-03: MSM and AC (as serialization editors) to draft an editorial proposal to resolve 29217 without substantive change to the spec. Status: Pending; ETA not specified. §§ no progress. New ETA 2015-11-17. ACTION A-622-04: MK to apply the changes outlined in comment 1 of bug 29227 (Partially-defined focus) to the F and O spec. Status: Pending; ETA not specified. §§ no progress. ETA 2015-11-17 ACTION A-622-06: JR to make the change proposed by Michael Dyck in comment 1 of Bug 29246 ([XQ31] context item declarations) and then close the bug. Status: Pending; ETA not specified. §§ Done, but there has been subsequent pushback on the way it was done. §§ Action item closed. ACTION A-622-08: JR to change the words of the XQuery spec to implement item (C) of bug 29225 [XQ31] Pragma in no namespace. Status: Pending; ETA not specified. §§ Done. J1.5.2 Completed action items ACTION A-620-01 Jonathan Robie to come up with the wording for solving Bug 4378. Status: Closed; See http://lists.w3.org/Archives/Public/public-xsl-query/2015Nov/0007.html ACTION A-621-01: O’Neil to make change needed in the test case contextDecl-022. See comment 2 in bug 29027 Status: Closed; See http://lists.w3.org/Archives/Public/public-xsl-query/2015Nov/0006.html ACTION A-621-02: On Jonathan to implemented proposal of bug 29225 in the XQuery Spec. Status: Closed; ACTION A-621-03: Michael Dyck to update the grammar for empty expressions in braces. Status: Closed; See http://lists.w3.org/Archives/Public/public-xsl-query/2015Nov/0001.html ACTION A-621-06 Andy to make the change of Serialization of newlines in the spec. Status: Closed; Overtaken by events ACTION A-621-08. Jonathan to make the change described in bug 29227, but limit it to context size and make it XPath only Status: Closed; ACTION A-622-01: Michael Dyck to fix the break in the production system build of XQuery Update which he reported in http://lists.w3.org/Archives/Public/public-xsl-query/2015Nov/0003.html Status: Closed; See https://lists.w3.org/Archives/Public/public-xsl-query/2015Nov/0013.html ACTION A-622-05: MK to propose a resolution to bug 4378 "error in K2-NodeTest-21" (dependency of function bodies on context item). Status: Closed; See https://lists.w3.org/Archives/Public/public-xsl-query/2015Nov/0012.html ACTION A-622-07: Michael Dyck to make the appropriate grammar change(s) for item (C) of bug 29225 [XQ31] Pragma in no namespace. Status: Closed; See https://lists.w3.org/Archives/Public/public-xsl-query/2015Nov/0015.html J1.6 Update on related activities J1.6.1 Update on XSLT WG activities (Sharon, MikeK) §§ MK reported: We have a director's call on Thursday to go to CR. J1.6.2 Update on EXPath/EXQuery CG activities (Loren) §§ Nothing to report. J1.7 Future Meetings J1.7.1 QT Meeting Schedule [V43] Joint XML Query/XSL WG meeting schedule https://lists.w3.org/Archives/Member/w3c-xsl-query/2015Jul/0038.html J1.7.2 Future F2F Meetings J1.7.2.1 Other future F2F meetings §§ Andy Coleman will circulate the WG for further opinions about XML Prague; if no interest then we carry on without F2F meetings. §§ JR asks how the group is expected to operate in future. How will we do maintenance of the existing specs? What about the outstanding work programme e.g. on XQ Update. Need someone to work on the test suite, without this we can't go beyond CR on 3.0 which means we can't really start 3.1. §§ AC Whether we hold a F2F all depends on whether there's a critical mass of people who want to attend. §§ JR Perhaps the majority of the group now feel we've finished but there's a small core who want to finish some things on Update and Full Text. §§ ACTION A-623-02 Andy to contact Christian Gruen again about his willingness to commit effort to XQuery Update. J2. Documents For Review (none) J3. Maintenance Issues J3.0 The XML Query WG and XSLT WG do not intend to maintains specs earlier than the 3.0 suite of documents; when the 3.1 suite reaches Recommendation, maintenance of the 3.0 documents will be terminated. This agenda item is reserved for reporting errors and other problems reported against the 3.0 (later, 3.1) suite of specifications. J3.0.1 Concerns raised by the XSLT working group in regards to potential completion delays of XSLT 3.0 if XPath 3.0 is made obsoleted by 3.1 Status: Pending the outcome of Abel's review of 3.0 bugs/errata. Any change to the status of the 3.0 specs requires explicit XSL WG consultation. J3.1 Bugzilla Bugs filed against the 3.0 suite of joint XML Query WG and XSLT WG documents J3.1.1 Bugzilla Bug 24568, Is the type system really a lattice? Or just a partially ordered set? http://www.w3.org/Bugs/Public/show_bug.cgi?id=24568 Status: Fixed in Data Model 3.1; not expected to be addressed in Data Model 3.0 J3.1.2 Bugzilla Bug 25231, [F+O 3.0 ONLY], ISO 8601, and XSD 1.1 http://www.w3.org/Bugs/Public/show_bug.cgi?id=25231 Status: Fixed in F&O 3.1; not expected to be addressed in F&O 3.0 J3.1.3 Bugzilla Bug 26788, [XPath30] XQuery-only errors in XPath 3.0 specification, like XQST0134" https://www.w3.org/Bugs/Public/show_bug.cgi?id=26788 Status: Fixed in XPath 3.1; not expected to be addressed in XPath 3.0 J4. Active Specification Development J4.1 Full Text 3.0 (Jim) J4.1.0 Internal working draft http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-30/html/Overview.html http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-30/html/Overview-diff.html http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-30/src/changes.txt (none) J4.2 Full Text 3.0 Requirements and Use Cases (Jim) J4.2.0 Internal working draft http://www.w3.org/XML/Group/qtspecs/requirements/xpath-full-text-30/html/Overview.html (none) J4.3 Full Text 3.1 (Zed Zhou) J4.1.0 Internal working draft http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-31/html/Overview.html http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-31/html/Overview-diff.html http://www.w3.org/XML/Group/qtspecs/specifications/xpath-full-text-31/src/changes.txt Zed Zhou should prepare a draft of this document with at least some technical changes (relative to Full Text 3.0) already made so the WGs can consider if they like the direction. J4.4 Full Text 3.1 Requirements and Use Cases (Zed Zhou) J4.4.0 Internal working draft http://www.w3.org/XML/Group/qtspecs/requirements/xpath-full-text-31/html/Overview.html Zed Zhou should prepare a draft of this document with the necessary requirements and at least some use cases for the WGs to consider. We should spend significant time determining which requirements the WGs will accept. J4.5 XPath and XQuery 3.1 Requirements and Use Cases (Jonathan) J4.5.0 Internal working drafts http://www.w3.org/XML/Group/qtspecs/requirements/xquery-31/html/Overview.html (none) J4.6 Data Model 3.1 (Norm) J4.6.0 Internal working draft http://www.w3.org/XML/Group/qtspecs/specifications/xpath-datamodel-31/html/Overview.html http://www.w3.org/XML/Group/qtspecs/specifications/xpath-datamodel-31/html/Overview-diff.html http://www.w3.org/XML/Group/qtspecs/specifications/xpath-datamodel-31/src/changes.txt (none) J4.7 Functions and Operators 3.1 (Mike Kay) J4.7.0 Internal working draft http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/html/Overview.html http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/html/Overview-diff.html http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/src/changes.txt J4.7.1 Bug 29146 - [FO31] fn:transform options update https://www.w3.org/Bugs/Public/show_bug.cgi?id=29146 Status: Pending outcome of XSL WG's discussion on this. J4.8 Serialization 3.1 (Michael Sperberg-McQueen, Andy) J4.8.0 Internal working draft http://www.w3.org/XML/Group/qtspecs/specifications/xslt-xquery-serialization-31/html/Overview.html http://www.w3.org/XML/Group/qtspecs/specifications/xslt-xquery-serialization-31/html/Overview-diff.html http://www.w3.org/XML/Group/qtspecs/specifications/xslt-xquery-serialization-31/src/changes.txt (none) §§ J4.8.1 Bug 29270: omit-xml-declaration §§ MSMcQ: Could argue the value should always be no. But if you want to output a sequence of XML documents with a declaration at the start of each one, that seems a reasonable thing to ask for. Concrete proposal: each time you pass a node into the XML method (specifically, one of the nodes in the sequence being serialized, but not their descendants of course), if omit-xml-decl=no, you get a declaration at the start. If you don't want that, don't ask for it. §§ DECISION: resolve bug 29270 by documenting the expected behaviour that each time a node in the original sequence is serialized, if an XML declaration is requested, then you get a new one. (If you don't want that, don't ask for it). §§ ACTION A-623-03 on the Serialization editors to add a note to the spec explaining the decision on bug 29270 §§ May need thought about the wording in the case where we have nodes within a map, etc. §§ MK: have we said anything about only allowing a BOM at the start of the stream, and requiring a consistent encoding throughout the stream? §§ AC: there appears to be no text saying this. But it comes up in the next bug 29272. §§ J4.8.2 Bug 29272: adaptive serialization of items other than nodes §§ The text that Christian G refers to appears to be a bit of a left-over from the way it was previously done, where the Adaptive method delegated everything to some other method. §§ MSMcQ: We should certainly only do BOM once, at the start. §§ MK: and I think we should have a consistent encoding. (But then you get that automatically because you can only specify encoding once). §§ ACTION A-623-04 on the Serialization editors to make a proposal as to how bug 29272 should be resolved. §§ J4.8.3 Bug 29273: adaptive serialization of items other than nodes §§ Should special characters like ampersand in strings be escaped (e.g. as &)? §§ We need to think about how to handle characters outside the encoding. §§ Also people might want visible representations of control chars (e.g. newline) appearing withing strings. §§ MK: There are arguments both ways – but we don't want an extra serialization parameter! §§ Note also that in XPath, XML escapes are not recognized, but in XQuery they are. §§ ACTION A 623-05 on the Serialization editors to make a proposal as to how bug 29273 should be resolved. J4.9 XPath 3.1 (Jonathan) J4.9.0 Internal working draft http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/html/xpath-31.html http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/html/xpath-31-diff.html http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt (none) J4.10 Grammar Test Applets (Michael Dyck) J4.10.1 Bugzilla Bug 13796, [Applet30] \u escaped characters in grammar applets http://www.w3.org/Bugs/Public/show_bug.cgi?id=13796 Status: Pending J4.11 QT3 test suite (O'Neil) J4.11.1 Status report on test suite, harness, tools J4.11.2 Status of 3.1 tests Status: Coverage is almost complete. J4.11.3 Publication of test suite. Status: Ready to discuss J4.12 FT 3.1 test suite (???) * Need test suite developer/manager * Need tests J5. Progression of Work J5.1 XSLT 3.0, XQuery 3.1, XQueryX 3.1, XPath 3.1, XDM 3.1, F&O 3.1, Serialization 3.1 J5.1.1 Current status * In Candidate Recommendation; awaiting implementation reports J5.1.2 Dependencies inhibiting progression * Completion of test suite minimum-required-to-declare-victory * Sufficient implementation experience and reports thereof * Formal response to all comments, responses accepted by commenters * PR Transition Request and authorization, PR pub request * REC Transition Request and authorization, REC pub request J5.1.3 Vote to publish XQuery 3.1 as revised Candidate Recommendation §§ Vote to re-publish XQuery 3.1 as a CR §§ MK what's the process? AC: we don't need a director's call as we are only republishing, not progressing. Therefore we can do the specs separately, and it's best to do it while there are no open bugs. §§ Approved unanimously. §§ ACTION A-623-01 Andy to do what's needed to republish the XQuery CR. §§ Roll-call for the vote: Andy Coleman, Jonathan Robie, John Snelson, Michael Dyck, O'Neil Delpratt, Michael Kay, Tim Mills, Michael Sperberg-McQueen. J5.1.4 Vote to publish Serialization 3.1 as revised Candidate Recommendation Status: Ready to discuss §§ Given the recent new bug reports, this was deferred to a future meeting. J5.2 Full Text 3.0 J5.2.1 Current Status * Proposed Recommendation J5.2.2 Dependencies inhibiting progression * REC Transition Request and authorization, REC pub request J5.3 Update 3.0 J5.3.1 Current Status * In Last Call Working Draft J5.3.2 Require owner of XQUF 3.0 Test Suite J5.3.3 Dependencies inhibiting progression * CR Transition Request and authorization, CR pub request * Completion of test suite minimum-required-to-declare-victory * Sufficient implementation experience and reports thereof * Formal response to all comments, responses accepted by commenters * PR Transition Request and authorization, PR pub request * REC Transition Request and authorization, REC pub request J6. Any other business J6.1 Consideration of future work J6.1.1 QT 3.2 The WGs decided that we will finish the 3.1 documents presently under way, but undertake no new work. Maintenance work should be planned upon for a period of time after finishing the specifications. J6.1.2 FT 3.1 EMC has expressed interest and is willing to provide resources J6.1.3 Update 3.1 Unclear whether there is adequate interest or resources J7. Adjourn ======================= XML Query Working Group ======================= Q1. The XML Query WG does not intend to maintains specs earlier than the 3.0 suite of documents; when the 3.1 suite reaches Recommendation, maintenance of the 3.0 documents will be terminated. Q1.0 This agenda item is reserved for reporting errors and other problems reported against the 3.0 (later, 3.1) XML Query WG suite of specifications. Status: Pending completion of ACTION A-592-02. Q1.1 Bugzilla Bugs filed against the 3.0 suite of XML Query WG documents (none) Q2. Active Specification Development Q2.1 XQuery Update Facility 3.0 (John) Q2.1.0 Internal working draft http://www.w3.org/XML/Group/qtspecs/specifications/xquery-update-30/html/Overview.html http://www.w3.org/XML/Group/qtspecs/specifications/xquery-update-30/html/Overview-diff.html http://www.w3.org/XML/Group/qtspecs/specifications/xquery-update-30/src/changes.txt * The WG needs to obtain implementation experience with this document. Q2.2 XQuery Update Facility 3.0 Requirements and Use Cases (Andy) See http://www.w3.org/XML/Group/qtspecs/requirements/xquery-update-30/html/Overview.html * The WGs need to be certain that this document is completed (red/yellow/green bullets on requirements, all the use cases intended to be published) and a decision made to advance it to WG Note. Q2.3 XQuery 3.1 (Jonathan) Q2.3.0 Internal working draft http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/html/xquery-31.html http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/html/xquery-31-diff.html http://www.w3.org/XML/Group/qtspecs/specifications/xquery-31/src/changes.txt Q2.3.1 Bug 4378 - error in K2-NodeTest-21 Status: Ready to discuss; See Mike Kay's proposal: https://lists.w3.org/Archives/Public/public-xsl-query/2015Nov/0012.html https://www.w3.org/Bugs/Public/show_bug.cgi?id=4378 §§ There was a lot more discussion (almost an hour), but we didn't make great progress. §§ There seems some level of consensus: (a) we all want to be allowed to raise a static error when a context-dependent expression is used in a function body. (b) We think making it a type error might be an expedient way to achieve this. §§ The disagreement is about how we need to define the static/dynamic context to make this possible. §§ Also need machinery for describing how type errors are raised for things like name() where the reference to the context item is implicit. We can't raise type errors from within the F+O spec of the function, it has to be associated with the function call itself. §§ Feeling that we want to progress and we may have to do so without making progress on this issue: i.e. decide to stick with the status quo. §§ DECISION: close bug 4378 as "works for me". Q2.3.2 Bug 29260 - Array Tests: function tests https://www.w3.org/Bugs/Public/show_bug.cgi?id=29260 Status: Ready to discuss §§ It seems Christian is asking for an improved explanation rather than any spec change. §§ DECIDED to close as editorial with an action on Jonathan to implement the change. §§ ACTION A-623-06 Jonathan Robie to add to the spec a note along the lines suggested by Christian in bug 29260 Q2.3.3 Bug 29263 - if expression: optional else branch? https://www.w3.org/Bugs/Public/show_bug.cgi?id=29263 Status: Ready to discuss §§ MK felt that it was undesirable to introduce a dangling-else ambiguity. §§ Proposed to solve as won't fix §§ MSMcQ felt this wasn't a won't fix, because we didn't think there was a problem to fix. So close as "works for me". §§ DECISION to close bug 29263 as "works for me". Q2.3.4 Bug 29264 - XQuery err details as a map https://www.w3.org/Bugs/Public/show_bug.cgi?id=29264 Status: Ready to discuss §§ JR: this is too late to consider, it's too big a change. §§ We accept the rationale in comments 3 and 6. §§ DECISION: close bug 29264 as "won't fix". §§ Q2.3.5 Empty enclosed expressions, new email from Jonathan. Nov/0032 §§ https://lists.w3.org/Archives/Public/public-xsl-query/2015Nov/0032.html §§ JR proposes aligning the terms "EnclosedExpr" and "enclosed expression" so they are the same by definition; this means enclosed expressions now appear in places like ordered{} and unordered{}. §§ The WG agreed with this direction. §§ Noted that bug 29225 is still open but we have made and implemented a decision on its resolution. Q2.4 XQueryX 3.1 (Josh) Q2.4.0 Internal working draft http://www.w3.org/XML/Group/qtspecs/specifications/xqueryx-31/html/Overview.html http://www.w3.org/XML/Group/qtspecs/specifications/xqueryx-31/html/Overview-diff.html http://www.w3.org/XML/Group/qtspecs/specifications/xqueryx-31/src/changes.txt (none) Q3. Test Suite Development Q3.1 Update Facility 3.0 Test Suite (????) * Need test suite developer/manager * Need tests Q4. Any other business Q5. Adjourn Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Received on Wednesday, 11 November 2015 15:14:57 UTC