You are here: MyURC.org > Tools & Prototypes > URC SDK > Trace URC SDK - Release Notes

Trace URC SDK - Release Notes

Release 3.2 - October 2006

Note: Release 3.2 is a major update for release 3.1.

Page Contents:

New Features
Known Limitations
Known Bugs

New Features

Updated tutorials. Two new tutorial have been added:
- How to write a Target in C/C++/C#
- How to write a URC in Javascript or Flash
A Target may now send accumulated updates to the URC if the TUN supports this feature. See class TargetSession within package edu.wisc.trace.urcsdk.target.
Support for the following additional types for Socket elements:
- xsd:gDay
- xsd:dateTime
- xsd:date
- xsd:duration
- xsd:gMonth
- xsd:gYear
- xsd:gYearMonth
- xsd:gMonthDay
- xsd:time
- xsd:decimal
- xsd:integer
The <static> element is now supported (for values defined in Socket Description)
Support for uis:timedCommand
Support for XML namespace checking (namespace URIs and prefixes)
Support for non-Java Targets through JNI (see tutorial How to write a Target in C/C++/C#)
Support for <operationRef> in Resource Sheets
Support for increment attribute for Interactors
Support for TwonkyMedia 3.x

Code written for release 3.0 and 3.1 of the URC SDK should run on the 3.2 release with minor modifications.

Known Limitations

The Trace URC SDK resource sheet retrieval algorithm currently uses domain, language, format, type and role as scents to determine if a particular resource sheet will be parsed.

The Trace URC SDK implements the ANSI/INCITS standards 389-2005, 390-2005, 391-2005, 392-2005 and 393-2005. However, not all features of these standards are currently implemented.

The following table lists the features that are defined in the standards but not currently implemented in the SDK, and the SDK's Java package where the feature is missing. References to the pertinent sections of the standards are provided.


Java Package (and class)	Features that are not implemented	Reference to ANSI/INCITS Standard and section
edu.wisc.trace.urcsdk.client.uisocket	The parser ignores any tag that is not defined in the standard (with its full QName, including namespace identifier). In addition, all Dublin Core elements are not checked for their proper namespace and are ignored except <`dcterms:conformsTo`>.	390-2005, 5.1
edu.wisc.trace.urcsdk.client.uisocket.types	The `calculate` attribute for socket variables is not supported. If encountered in a Socket Description, it is ignored.	390-2005, 8.7.4
edu.wisc.trace.urcsdk.client.uisocket.types	The following constraining facets are not supported and ignored when encountered in a Socket Description: length, minLength, maxLength pattern whitespace maxExclusive, minExclusive	390-2005, 11.3
edu.wisc.trace.urcsdk.client.uisocket.types	Fundamental facets are not supported.	390-2005, 11.3
edu.wisc.trace.urc.sdk.client.pret	If a Widget is used in modalDialog as well as the main window, when one Widget is interacted with, the other is not updated
edu.wisc.trace.urcsdk.client.pret	Groups with attribute `cohesion="strong"` are not presented separately from other groups as recommended by the standard.	391-2005, 8.4
edu.wisc.trace.urcsdk.client.pret.Select1Interactor, edu.wisc.trace.urcsdk.client.pret.SelectInteractor	For <select1> and <select> interactors, open selections are not supported. The SDK will print a warning if it encounters a `<select1>` or `<select>` interactor with attribute `close="false"`.	391-2005, 9.6 & 9.7
edu.wisc.trace.urcsdk.client.Target	For the `<target>` element in a Target Description, the attribute `hidden` is not supported (ignored). Any available target is displayed to the user, independent of the value of the `hidden` attribute.	392-2005, 7.4
edu.wisc.trace.urcsdk.client.Target	The `<location>` element is not supported in a Target Description. If encountered, it is ignored.	392-2005, 7.7
edu.wisc.trace.urcsdk.client.Target	Dublin Core Metadata terms (except `<dcterms:conformsTo>` and `<dcterms:modified>`) are not supported in a Target Description. If encountered, they are ignored.	392-2005, 7.9
edu.wisc.trace.urcsdk.client.Target	The `<category>` element is not supported in a Target Description. If encountered, it is ignored.	392-2005, 7.10.7
edu.wisc.trace.urcsdk.client.Target	The `<constraints>` element is not supported in a Target Description. If encountered, it is ignored.	392-2005, 7.10.8
edu.wisc.trace.urcsdk.client.resources	The resource manager retrieves resources from local resource sheets only. No resource server is contacted even if `<ResourceServiceDescriptions>` is included in the Target Descriptions.	393-2005, 11
edu.wisc.trace.urcsdk.client.resources	The `rdf:parseType` attribute has no effect. All resources are treated as if they had `rdf:parseType="Literal"`.	393-2005, 8.4.2
edu.wisc.trace.urcsdk.client.resources	The `rdf:dataType` attribute is not supported. A warning is thrown if encountered in a Resource Sheet.	393-2005, 8.4.3
edu.wisc.trace.urcsdk.client.resources	The`<span>`element is ignored in Resource Descriptions. Its`title`attribute,`<value>`subelements and text content are stored by the SDK, but currently cannot be easily accessed.	393-2005, 8.4.4
edu.wisc.trace.urcsdk.client.resources	The`<value>`subelement of`<span>`currently inserts the text where "elementRef" is the attribute, instead of the actual value.	393-2005, 8.4.4.4
edu.wisc.trace.urcsdk.client.resources	Dublin Core elements used in a Resource Directory are not used by the SDK for scent matching when looking for an appropriate Resource Sheet.	393-2005, 12.12
edu.wisc.trace.urcsdk.client.uisocket.FacadeForJs	This class provides an interface to a subset of the URC SDK functionality for UIID implementations in languages other than Java (e.g. Javascript, Flash). Content of Atomic Resource Descriptions (in particular labels) are provided as strings, and contained markup is stripped off. In particular: <span> elements (and attached attributes) are stripped off <value> elements are replaced by the current value of the referenced socket element	393-2005, 8.4
edu.wisc.trace.urcsdk.client.uisocket.FacadeForJs	No updates provided for resource changes (e.g. because of <value> tag)	393-2005
edu.wisc.trace.urcsdk.client	The client reads the target's documents from the local filesystem. Therefore you can only run a client and target from different computers if both computers have the documents stored locally in the same file locations.	N/A
edu.wisc.trace.urcsdk.target	A session request will fail if one or more notifications are open.	389-2005, 7.5.1

Known Bugs

Exceptions are often thrown by the CyberGarage UPnP Library, but do not affect the functionality of the prototype.
In XPath expressions, values of type xsd:integer are handled internally as strings. For example, if the execute dependency is value('elevatorFloor')=1, one must write it as follows to make it work: value('elevatorFloor')='1'.

Please report bugs to zimmer@trace.wisc.edu.

Last update: Gottfried Zimmermann, 2006-10-24