Re: Last call announcement for various XPointer related specs

Hello Paul, Ronald,

I just had a quick look at your new documents.
It seems that one very important section from the previous version,
namely "4.1 Character Escaping"
(http://www.w3.org/TR/2001/CR-xptr-20010911/#escaping)
has fallen between the cracks. This section is extremely important
for I18N. If I have missed it, please tell me where to find it.

If it has been lost inadvertedly, it may be worth considering to
asap issue an updated version of http://www.w3.org/TR/xptr-framework/,
where I think it can be easily integrated, probably as Section 3.2
(moving the current 3.2,... up), to make sure that the spec can
be reviewed in its entirety. Some small editorial changes
(such as IURI -> IRI) may be needed but could be deferred to the
next stage.

I very much hope this section has not been removed on purpose.

Regards,    Martin.


At 09:06 02/07/11 -0500, Paul Grosso wrote:

>[Sorry, resending with the correct subject this time. paul]
>
>The XML Linking WG announces Last Call on the following
>three drafts:
>    XPointer Framework [1]
>    XPointer element() Scheme [2]
>    XPointer xmlns Scheme() [3]
>
>These drafts, in combination with the working draft
>    XPointer xpointer() Scheme  [4],
>provide basically the same functionality as the XPointer CR
>draft[5] of 2001-09-11.  The only new functionality is to
>allow XML Schema declaration of ID-type attributes, in
>addition to DTD declarations. Primarily, the XPointer
>draft has been factored into multiple documents so that
>XPointer support will be easier to implement than as a
>monolithic specification.
>
>The decision to go to Last Call is minuted at [6].
>The last call review period ends July 31. Comment should be
>sent to www-xml-linking-comments@w3.org.
>
>Unless the review uncovers substantial problems, the next step
>will be to recommend the documents for publication as Candidate
>Recommendations or Proposed Recommendations, depending on the
>level of implementation experience. (The framework draft, in
>particular, may avoid a second CR period because of its
>simplicity, the way that a number of other W3C specs
>rely only on the functionality from XPointer it provides,
>and because of existing implementation experience.)
>
>Paul Grosso for
>Ron Daniel Jr.
>Acting chair, XML Linking WG
>
>[1] http://www.w3.org/TR/xptr-framework/
>[2] http://www.w3.org/TR/xptr-element/
>[3] http://www.w3.org/TR/xptr-xmlns/
>[4] http://www.w3.org/TR/xptr-xpointer/
>[5] http://www.w3.org/TR/2001/CR-xptr-20010911/
>[6] http://lists.w3.org/Archives/Member/w3c-xml-linking-wg/2002May/0146

Received on Tuesday, 16 July 2002 07:23:53 UTC