${taskforce.name} Avatar
  1. OMG Task Force

XTCE US Government Satellite Conformance Profile 1.0 (XUSP) FTF — All Issues

  • Key: XPUS
  • Issues Count: 6
Open Closed All
All Issues

Issues Descriptions

That's for Earth Orbital Missions

  • Key: XPUS-16
  • Legacy Issue Number: 18368
  • Status: closed  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    Please specify that this is for earth orbital missions

  • Reported: XUSP 1.0b1 — Thu, 13 Sep 2012 04:00 GMT
  • Disposition: Closed; No Change — XUSP 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Wed, 29 Apr 2015 02:51 GMT

XML snippet in 6.2.3.2

  • Key: XPUS-17
  • Legacy Issue Number: 18371
  • Status: closed  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    In 6.2.3.2, specify that the XML snippet is an exemple and unbold the text between the two xml snippets.

  • Reported: XUSP 1.0b1 — Thu, 13 Sep 2012 04:00 GMT
  • Disposition: Resolved — XUSP 1.0
  • Disposition Summary:

    Unbold the text. The XML sequences are already referred to as examples in the text

  • Updated: Wed, 29 Apr 2015 02:49 GMT

Errors in the template

  • Key: XPUS-15
  • Legacy Issue Number: 18372
  • Status: closed  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    The schemaLocation is wrong, it should be (I guess) http://www.omg.org/space/xtce/SpaceSystemV1.1.xsd
    By the way, this file does not exist (today) and it should be an officiel OMG URL
    This template seems too loose a definition for something normative.
    For instance: "Each user based on their mission must change some items. This includes items such as..." there is here a need to list all the items.
    Couldn't it be possible to standardize an XSD defining this template and, btw, including other rules?

  • Reported: XUSP 1.0b1 — Thu, 13 Sep 2012 04:00 GMT
  • Disposition: Resolved — XUSP 1.0
  • Disposition Summary:

    Updated schema location to:
    http://www.omg.org/spec/XTCE/20061101/06-11-06.xsd

  • Updated: Wed, 29 Apr 2015 02:49 GMT

Section 6.1.2 is non normative

  • Key: XPUS-14
  • Legacy Issue Number: 18370
  • Status: closed  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    Section 6.1.2 is non normative since the excel file is normative. So, I propose to move this section to an annex and clearly state that this annex is non normative.

  • Reported: XUSP 1.0b1 — Thu, 13 Sep 2012 04:00 GMT
  • Disposition: Resolved — XUSP 1.0
  • Disposition Summary:

    Delete Section 6.1.2. Table Summary (this is at the end of section 6, so there is no paragraph renumbering required).

  • Updated: Wed, 29 Apr 2015 02:49 GMT

reference to XTCE_v1.1_GovSat Tailoring Guide_Rules Table file is problematic

  • Key: XPUS-13
  • Legacy Issue Number: 18369
  • Status: closed  
  • Source: Anonymous
  • Summary:

    The reference to XTCE_v1.1_GovSat Tailoring Guide_Rules Table file is problematic because this is not the wau the OMG store the files

  • Reported: XUSP 1.0b1 — Thu, 13 Sep 2012 04:00 GMT
  • Disposition: Resolved — XUSP 1.0
  • Disposition Summary:

    The machine readable file containing the rules table will be formatted as a comma-separated value file format

  • Updated: Wed, 29 Apr 2015 02:49 GMT

references to the machine-consumable files

  • Key: XPUS-12
  • Legacy Issue Number: 19594
  • Status: closed  
  • Source: OS/COMET Product Group ( Brad Kizzort)
  • Summary:

    The references to the machine-consumable files on the cover page and in section 6.1 of the XUSP specification should consistently refer to the file(s) by their assigned URL rather than just a file name and/or document number.

  • Reported: XUSP 1.0b1 — Tue, 9 Sep 2014 04:00 GMT
  • Disposition: Resolved — XUSP 1.0
  • Disposition Summary:

    Replace file references on cover page and section 6.1 with assigned URLs.

  • Updated: Wed, 29 Apr 2015 02:48 GMT