This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6260 - roll up CR changes made during publication process
Summary: roll up CR changes made during publication process
Status: RESOLVED FIXED
Alias: None
Product: SML
Classification: Unclassified
Component: Core+Interchange Format (show other bugs)
Version: CR
Hardware: PC Windows XP
: P2 normal
Target Milestone: PR
Assignee: Kumar Pandit
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords: editorial
Depends on:
Blocks:
 
Reported: 2008-12-01 13:33 UTC by John Arwe
Modified: 2009-03-09 08:21 UTC (History)
1 user (show)

See Also:


Attachments

Description John Arwe 2008-12-01 13:33:26 UTC
We ran into a couple of problems this morning in connection with our CR
publication.  This is to record the last-minute changes I made to the  
HTML
(not to the XML) versions of our specs.  Most of these should also be  
made
in the main XML source of our specs, so the problems don't recur in the
PR draft.

(1) changed the target of the link on "5 February 2004 Patent Policy"
to the patent policy itself (was the IPP status page)
(2) linked "public list ... disclosures" to the IPP status page for
the WG
(3) linked the words "Essential Claim(s)" to the definition of that term
in the Patent Policy
(4) Made manual cosmetic changes to break long lines in examples and
schema documents (bug 5492 and similar places)
(5) Added a brief paragraph summarizing the most important changes:

   The major substantive change since the previous publication of this
   specification as a Last Call Working Draft has been the introduction
   of what are expected to be the final namespace names for the SML and
   SML-IF namespaces; previously each new Working Draft used a new pair
   of namespace names.  Other editorial and cosmetic changes have also
   been made.

(6) in SML-IF, corrected the targetNamespace attribute of the schema
document in appendix A to take the SML IF namespace name as its value.

Sorry not to have noticed all of these earlier.

Michael
Comment 1 Kumar Pandit 2009-03-09 08:21:16 UTC
(1)
Already being done. No change required.

(2)
Already being done. No change required.

(3)
done

(4)
Cannot make manual changes because the examples are generated by the build.

(5)
List of changes not required because the PR doc status already has a link to diffs between CR and PR docs.

(6)
Already being done. No change required.