Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: CSD07
    • Fix Version/s: CSD07
    • Component/s: Spec
    • Labels:
      None
    • Proposal:
      Hide

      Fix broken links in document as non-material changes in next WD.

      Show
      Fix broken links in document as non-material changes in next WD.

      Description

      We realized some broken references in the current CS01 documents which will be fixed as non-material changes. Below is a copy of an email discussion we had with OASIS staff about this.

      From: Chet Ensign <chet.ensign@oasis-open.org>
      To: Thomas Spatzier/Germany/IBM@IBMDE,
      Cc: "Lipton, Paul C" <Paul.Lipton@ca.com>, Simon D
      Moser/Germany/IBM@IBMDE, Derek Palma <dpalma@vnomic.com>
      Date: 02.04.2013 15:39
      Subject: Re: Noticed some broken links in

      Hi Thomas -

      Those can be fixed as Non-Material Changes if you are going directly
      to
      Candidate OASIS Standard from Committee Spec 01.

      Because these are in the content, the TC will need to fix them. I
      don't
      touch content unless it is an absolutely emergency.

      • The "Error!" means that an intra-document link in the Word source
        file
        doesn't have a matching target. You just need to find the bookmark
        (or
        whatever it is called) associated with part being referenced and use
        that
        in the broken link.

      Best,

      /chet

      On Tue, Apr 2, 2013 at 5:16 AM, Thomas Spatzier <
      thomas.spatzier@de.ibm.com
      > wrote:

      Hi Chet,

      I just noticed some broken links (see below) of the TOSCA v1.0
      CS01
      documents and wanted to make you aware of it. Please let me
      know if
      we have
      to do something as editors, even though I am not aware of any
      changes
      in
      those areas in our last edits.

      Here is the list of broken links I found:
      1) The link to the TOSCA schema at the beginning of Appendix D
      points
      to an
      invalid URL (produces an HTTP 404)
      2) There is a string "Error! Reference source not found" in
      lines 25
      and
      1681 of the .doc and .pdf files.

      Regards,
      Thomas

        Attachments

          Activity

            People

            • Assignee:
              thomas.spatzier Thomas Spatzier
              Reporter:
              thomas.spatzier Thomas Spatzier
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: