OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Created: (TOSCA-83) Broken references in CS01


Broken references in CS01
-------------------------

                 Key: TOSCA-83
                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-83
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: Bug
          Components: Spec
    Affects Versions: CSD07
            Reporter: Thomas Spatzier 
            Assignee: Thomas Spatzier 
            Priority: Minor
             Fix For: V2_CSD01


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 problem with the schema link is that the URL is missing a level
      in
      the hierarchy. It current points to
      http://docs.oasis-open.org/tosca/TOSCA/v1.0/schemas/TOSCA-v1.0.xsd .
      It
      should point to
      http://docs.oasis-open.org/tosca/TOSCA/v1.0/cs01/schemas/TOSCA-v1.0.xsd
       . I
      can give you the proper link to use when preparing the next version.

      - 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


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]