W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > September 2004

Minutes for XML Core WG telcon of 2004 September 22

From: Paul Grosso <pgrosso@arbortext.com>
Date: Wed, 22 Sep 2004 12:03:36 -0400
Message-ID: <F13E1BF26B19BA40AF3C0DE7D4DA0C03978684@ati-mail01.arbortext.local>
To: "XML Core WG" <public-xml-core-wg@w3.org>

 
Attendees
---------
 Paul 
 Glenn xx:17
 Jonathan
 Dmitry 
 Norm  
 Leonid
 Richard
 François  off at xx:35

[7 organizations (8 with proxies) present out of 12]

Regrets
------- 
Daniel, proxy to the chair
Lew
Sandra

Absent organizations
--------------------
NIST (with regrets)
W3C
Daniel Veillard (with regrets, proxy to the chair)
Lew Shannon (with regrets)
John Cowan

> 1. Accepting the minutes from the last telcon [3] and
>    the current task status [2] (have any questions, comments,
>    or corrections ready by the beginning of the call).

Accepted.

> 2. Miscellaneous administrivia.
> 
> The next W3C Technical Plenary Week will be 28 February 2005
> through 4 March 2005:
>      http://www.w3.org/2002/09/TPOverview.html
> 
> The meeting will be held in the Hyatt Harborside, Boston:
>      http://harborside.hyatt.com/property/index.jhtml
> 
> 
> 3. Problem with xml:space in the Schema document for the XML namespace
> 
> Masayasu Ishikawa <mimasa@w3.org> sent us email on this at:
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Jul/0019
> 
> CONSENSUS to remove the default for xml:space from the schema
> for the xml namespace.
> 
> ACTION to Henry:  Draft a new schema and send it to the XML Core list.

ACTION continued.

> 4. XML errata.  The published 1.0 errata document is [8], the
>    published 1.1 errata document is [9], and the NEW PUBLIC
>    Potential Errata (PE) document is [7]. 
> 
> 
> 5. Namespaces in XML.
> 
>   ACTION to Richard:  Produce a draft for NS1.0 2nd Ed.
> 
> 
> 6. Xinclude CR was published April 13 at:
>    http://www.w3.org/TR/2004/CR-xinclude-20040413
>    The updated test suite cover page is at
>    http://www.w3.org/XML/Test/XInclude/ 
> 
> The PR-ready draft is at:
> http://www.w3.org/XML/Group/2004/07/PR-xinclude/
> 
> The public DoC (aka latest issues list) is at:
> http://www.w3.org/XML/2004/07/ExIT-xinclude/issues.html
> [Note: The Director view displays incorrectly in IE6.0.]
> 
> The implementation report is at:
> http://www.w3.org/XML/2004/xinclude-implementation/report.html
> 
> Paul sent in the PR request at:
> http://lists.w3.org/Archives/Member/chairs/2004JulSep/0090
> 
> We have a PR request for telcon scheduled for Sept 21.

XInclude has been approved to go to PR, but we have spec
cleanup to do.

As an aside, we should plan to make more detailed/careful
implementation reports in the future where it is clearer
what "features" we are testing and whether the results
show interoperable support.

We have spec cleanup to do--see
http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Sep/0060
where Paul outlined what needs to be done.

The new IRI text suggested by Martin removes (relative to 
the text in our draft PR) characters such as space, <, >, `,
and others from IRIs.  Outside the defn of IRIs, do we want
to say one should escape the unwise characters if put into
the href attribute?

Jonathan suggests we can do one of three things:

1.  get rid of mention of IRIs entirely
2.  explain how to transform the href attr value into URI and IRI
3.  consider not escaping delimiters, etc.

Martin's proposal says href attributes are IRIs.  Richard says 
we could say that the href attribute can include "unwise" and
other characters, and we explain how to transform the value
of the href attribute into an IRI.  Glenn prefers to say that
the data type of an href is IRI and not fool with it.  Jonathan
points out we shouldn't make big changes to the spec, and the
spec currently says one should do an escaping process on the
value of the href attribute.

Jonathan suggests we use Martin's words for the IRI part of
the spec, but in the description of the href attribute, we
will change "the href value is an IRI ref" to "the href value
is a string to which some escaping is done" (not literally,
but something to that effect at the editor's discretion).

We talked about adding a note about XML 1.0 versus XML 1.1
versus the fact that XInclude is only working with infosets
(point 6 in Paul's email).  We ran out of time.

We did not get to discussing point 7 in Paul's email.  We
will let Jonathan suggest something in email.

ACTION to Jonathan:  Edit the PR draft per
http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Sep/0060
and the discussion in this telcon.

ACTION to Paul:  Submit the publication request for the
updated PR. 


> 
> 7. xml:id.
> 
> Norm has collected the xml:id issues, now (public) at:
> http://www.w3.org/XML/2004/xml-id/issues.xml
> 
> and put a new version of the draft at
> http://www.w3.org/XML/Group/2004/xmlcore/xmlid/xml-id.html
> 
> ID Strictness 
> -------------
> Commentor figures that non-validating parsers shouldn't have 
> to check for xml:id validity.
> 
> Currently, conformance to xml:id does require non-validating 
> parsers to check for xml:id validity; of course, no parser is 
> required to conform to xml:id.
> 
> Richard send email outlining our options at:
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Aug/0024
> 
> He outlines options of strict, moderate, lax id checking.
> 
> Richard would like to know that ids, for example, don't 
> contain spaces.
> 
> Then we started asking if id values should be NCName or Name.
> 
> Tentative CONSENSUS that we would do "moderate" where id values 
> should be NCName (with some uncertainty).
> 
> We left open what kind of error it would be if the above isn't 
> the case.
> 
> Norm sent email with his latest proposal:
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Sep/0003
> and there was some follow up email discussion.  We discussed this
> a bit last week, but we still need to discuss more.
> 
> 
> There is email from Dan Connolly re:
> how does XInclude mix with XML Schema? XSLT?
> at:
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Sep/0014
> Norm replied, and Dan rebutted, and DV commented; see the thread at:
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Sep/0034
> 
> 
> 8.  XML Profile.  The TAG (via Norm) asks about progress on this:
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Sep/0004
> 
> 
> 
> [1] http://www.w3.org/XML/Group/Core
> [2] http://www.w3.org/XML/Group/Core#tasks
> [3] 
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Sep/0049
> [7]
> http://www.w3.org/XML/2004/02/proposed-xml10-3e-and-xml11-errata.html
> [8] http://www.w3.org/XML/xml-V10-3e-errata
> [9] http://www.w3.org/XML/xml-V11-1e-errata
> 
> 
Received on Wednesday, 22 September 2004 16:04:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:31 GMT