This is the location that errata for published standards and specifications will be posted. Bookmark this page and visit as needed.
If you wish, you can add your name to the errata mailing list of the consortium to be notified when changes are made to this page.
If you are not a member of The SPIRITConsortium, you will need to use the email commands to subscribe. For help on this process see the help pages. To simply subscribe from your default email address, send mail to: errata-subscribe@lists.spiritconsortium.org.
The mailing list is archived here.
On 29 October 2008 the schema that is posted on this site was updated to match the schema that was part of the distribution. A web site archive problem caused an earlier version to display. The posted schema at http://www.spiritconsortium.org/XMLSchema/SPIRIT/1.4/ was out of date compared to the release package.
Differences:
- DesignConfig missing 3 identity constraints
- Component missing 2 identity constraints
- Abstractor changed 1 identity constraint
- BusInterface changed type of master/addressSpaceRef/baseAddress
- Documentation and legal header changes to all files
For Version 1.4 The current errata includes:
TGI Messages
- Description: TGI is missing a message for getting if a bus definition is addressable. New message will be added in a future version of the standard.
Work around: Check each port in the abstraction definition with the TGI call getAbstractionDefPortIsAddress to see if this is an addressable interface. - Description: TGI message getConfigurableElementDetails, getComponentInstanceConfigurableElementIDs and getAbstractorInstanceConfigurableElementIDs should not be used and they will return an error if used. These messages will be removed in a future version of the standard.
- Description: getParameterIDs should also take abstractorID & componenID as input for elementID
- Description: Access to service information in an abstraction definition is not clear. The function getAbstractionDefServiceIDs is poorly named, and returns a typeDefID from an abstraction definition when the abstraction definition does not contain the full typeDefID. Therefore the only valid functions for a typeDefID from an abstraction definition are getTypeDefTypeName and getTypeDefImplicit. Other messages may return unknown results.
- Description: setVendorExtensions shall only take designID, componentInstanceID and hierConnectionID as inputs. Description: getVendorExtensions shall add hierConnectionID as input.
- Description: componentInstanceID shall only be used in the documented calls. ComponentID shall return the configured values.
- Description: get getParameterIDs shall also take typeDefID as input.
SCRs (Semantic Consistancy Rules)
- Description: SCR 5.11: If an element has a format attribute with a value of choice, it also needs a choiceRef attribute.
- This SCR is invalid because choice is no longer a legal value for format.
- Addtional SCR: The interface referenced by the masterRef attribute of a subspaceMap element shall be a master interface that is bridged from a slave interface with a valid memory map referenced by its memoryMapRef element.
Schema
-
Description: portAccessType element for transactional ports does not have a default specified. The default shall be 'ref'.
XPATH
- Description: The dependency equations are evaluated each time the data of that element is accessed. Configurable element values are applied to a component's XML when read.
Description: Appendix E.4 example call text should say "pow" and not "log".
XSLT
- Description: While the release transform is valid it does have some extra information in it that may cause the Xalan XSLT processor with Java 1.4 to crash. The extra "//" has not additional meaning in this case. The work around is to change:
-
<xsl:template match="//@spirit:choiceStyle"/>
<xsl:template match="//@spirit:direction"/>
<xsl:template match="//@spirit:crossRef"/> - to be replaced with:
-
<xsl:template match="@spirit:choiceStyle"/>
<xsl:template match="@spirit:direction"/>
<xsl:template match="@spirit:crossRef"/>