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

Minutes for XML Core WG telcon of 2004 September 29

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

 
Attendees
---------
Paul 
Glenn 
Jonathan
Sandra
Dmitry xx:22
Norm  
Leonid
Richard
Henry
François  off at xx:35
Daniel
John xx:16

[11 organizations (11 with proxies) present out of 12]

Regrets
------- 
Lew

Absent organizations
--------------------
Lew Shannon (with regrets)


Norm gives regrets for next week.


> 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 (dated 2004 Sept 30) is at:
> http://www.w3.org/XML/Group/2004/07/PR-xinclude/
> Please double check it and raise any issues NOW!
> It is being sent in for publication as we speak!

On track to be published tomorrow.

> 
> 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.

We have CONSENSUS on the following:

* Processors MUST check that xml:id values are valid NCNames.

* It is an xml:id error for xml:id values to not be unique.

ACTION to Norm:  Produce another WG WD reflecting this and our
other decisions.

No mention of [references] Infoset property 
-------------------------------------------
Conclusion:  We'd like a motherhood note that suggests that
the [references] Infoset property should be correct for things
recognized by xml:id.

xml:id and fragment identifiers 
-------------------------------
We have CONSENSUS that we don't need to say anything here.
We could add another motherhood note here.

> 
> 8.  XML Profile.  The TAG (via Norm) asks about progress on this:
> http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Sep/0004
> 

9.  Jonathan Marsh sent a question about xpointer for WSDL at:
http://lists.w3.org/Archives/Public/public-xml-core-wg/2004Sep/0078

Can WSDL define/use an unqualified scheme name for use with xpointer?

Per http://www.w3.org/TR/xptr-framework/#scheme given that WSDL is
developing a W3C Rec, they can use an unqualified name.  Since any
such scheme name would "use up" that name for all other Recs, the 
XML Core WG recommends that WSDL use scheme names of the form
wsdl-interface, etc. or something similar.

> 
> [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/0062
> [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, 29 September 2004 16:01:24 GMT

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