NetworkedPlanet | TMCore Engine API Guide |
This section lists the the major changes introduced in TMCore07
NEW: The ITopicMapObject interface now exposes a new readonly property ID. This presents the object identifier as a 32-bit integer.
NEW: The ITopicMapSystem interface now exposes two overrides for the ExecuteQuery method. These overrides allow you to specify SQL parameters in a TMRQL query string and provide values for those parameters rather than relying on string concatenation. It is STRONGLY RECOMMENDED that you use these overrides in preference to the original ExceuteQuery(String) method. Refer to the section called “Executing Queries” for more details.
NEW: A new assembly NetworkedPlanet.Npcl provides APIs for creating and reading topic map schema information using the Networked Planet Constraint Language (NPCL). Refer to Chapter 12, The NPCL Constraints API for more information about these APIs.
NEW: A new web service application, npclws implements the NPCL Schema Web Service. This provides access to retrieve an XML representation of the NPCL schema governing a topic map or a single topic type within a topic map. Refer to the Web Service Guide for more information. The operations of this web service can be accessed via SOAP or using HTTP GET or POST requests.
NEW: New views have been added to the database to allow querying of the NPCL schema information in a topic map using TMRQL. See the TMCore Query Reference Sheet for an overview of these new views. The new veiws can be easily identified as their names all start with the prefix "tm_npcl".
UPDATED: The serviceclient.dll assembly that in previous versions contained only the SOAP web service stubs for the Topic Map Web Service now also contains the SOAP web service stubs for the NPCL Schema Web Service and classes for representing the structure of input and output XML used by the web services.
NEW: A new database user-defined function, tm_tc3 has been added. This function performs a transitive closure starting from a specified topic and using a set of association types and role types to determine the paths traversed.
UPDATED: The Topic Map Web Service now implements a new operation named ProcessTransaction. This operation allows a set of updates to a topic map to be described as a simple XML document and passed to the web service for processing as a single update transaction. This operation is, in most cases, far more efficient at updating specific topics and associations than the previously supported Save operation. However, the Save operation remains part of the Topic Map Web Service interface to enable efficient creation of new topics and associations in a topic map. For more details about this operation, please refer to the Web Services Guide.
NEW: The Topic Map Web Service now provides an ASP.NET-based implementation of the service allowing access to the operations using HTTP GET or HTTP POST requests. Unlike the SOAP HTTP transport, these interfaces implement all of the operations of the Topic Map Web Service.