- From: Paul Grosso <pgrosso@arbortext.com>
- Date: Wed, 23 Oct 2002 16:59:42 -0500
- To: www-xml-linking-comments@w3.org
Forwarding to the comment list to archive. >Date: Mon, 21 Oct 2002 16:39:39 -0700 >From: Michael Dyck <jmdyck@ibiblio.org> >Subject: further comments on XPointer EDITOR'S COPY >To: Paul Grosso <pgrosso@arbortext.com> >============================================================================ > >element() > >2 Conformance > >para 2 > You can delete this whole paragraph, since it's implied by the normative > dependence on the Framework spec. If you want to retain it, you should > at least delete the word "normatively", for the same reason you deleted > it from the corresponding para in the Framework spec. > >3 Language and Processing > >para 2 >"does not return a subresource." > Change "return" to "identify". > >syntax > Use initial capitals for both symbols. > Use camel case for both symbols. > i.e.: "ElementSchemeData" and "ChildSeq" > >para 4 >"exactly as for the Name shorthand form defined in the XPointer Framework >[XPtrFrame] specification" > The Framework spec doesn't call it "the Name shorthand form". How about: > "exactly as it would in a shorthand pointer, as defined in ..." > >"failure to identify a subresource" > Change "a subresource" to "an element", which ties it back to "a single > element" earlier in the sentence. > >"no subresource being returned" > Change "returned" to "identifed by the pointer part,". > >============================================================================
Received on Wednesday, 23 October 2002 17:59:49 UTC