Concepts for SharePoint 1.3 released
Version 1.3 of Concepts for SharePoint is now available. This package introduces a number of features and enhancements. The full change list and upgrade instructions can be found below.
The Concepts for SharePoint package can be downloaded from the NetworkedPlanet download page.
Upgrading instructions
------------------
Unzip the download package and run the STSADM -upgradesolution command. The exact command-line you use will depend on how you want to schedule the upgrade, but will be similar to:
stsadm -o upgradesolution -name ConceptsForSharePoint.wsp -filename ConceptsForSharePoint.wsp -allowgacdeployment -local
Restart IIS and the SharePoint 2010 Timer Service
If running CfS on a separate server to that of the Web3 Platform, you will also need to upgrade the additional web3.wsp file contained in the upgrade package and restart the services.
For full upgrade and usage instructions, please refer to the documentation contained in the downloaded package
Change Log
----------
FEATURE: Setting a Site Page to be about a particular topic : by adding a column to the Site Pages library columns collection (and adding the internal name of the field to the CfsServerConfig file, that Site Page can then be set to a particular term in the CfS Term Store. Web Parts placed on that page will then use the topic for that term as their starting topic, unless specifically overridden.
FEATURE: New Abstract Xml SPARQL Web Part class for use by developers to do server side processing of SPARQL queries.
FEATURE: New Abstract Xml One Hop Web Part class for use by developers to do server side processing of the results of a one hop query.
FEATURE: New Abstract Xml Two Hop Web Part class for use by developers to do server side processing of the results of a two hop query.
FEATURE: New Ajax SPARQL Web Part to display the results of a SPARQL query with all processing done client-side and no server-side processing of the query.
FEATURE: New Ajax One Hop Web Part to display the results of a one hop query with all processing done client-side and no server-side processing of the query.
FEATURE: New Ajax Two Hop Web Part to display the results of a two hop query with all processing done client-side and no server-side processing of the query.
FEATURE - New Topic Connector Web Part which loads the full topic representation of a topic (includes all associations)
FEATURE: New daily synchronisation timer job that performs a full synchronisation between the topic map and the SharePoint Managed Metadata Store.
ENHANCEMENT - Changed the profile scraper so that different user topic types can be used for different topic maps that may be in use on SharePoint Site Collections
ENHANCEMENT: External content types can now be created for multiple topic maps in SharePoint Search.
data.networkedplanet.com
The Web3 Platform is a great way to publish data sets online or within the enterprise. We have setup a new service at http://data.networkedplanet.com that exposes publically available data sets using Linked Open Data principles.
These data sets along with the Web3 Platform act as examples of how to best publish data so that others can make use of it.
Some of the key things that the Web3 Platform offers in this regard is:
1) The ability to address the concepts being published by a persistent, robust URI.
2) Full text concept searching for humans to find published concepts.
3) Human and Machine readable versions of every published concept.
4) SPARQL query endpoints for each data set allowing machines and people to formulate and execute queries over the data.
If you have a data set that you would like to see on data.networkedplanet.com please let us know, if you would like to know more about how the Web3 Platform can be used to publish Linked Open Data then please drop us an email.
LOS on data.networkedplanet.com
The service at data.norge.no provides metadata about data sets that are published by a variety of organisations and aims to facilitate the sharing and reuse of data and vocabularies. The service at data.norge.no is very well put together allowing developers and organisations to find out about data sets that may be of use to them. However, the quality and way in which the organisations listed expose the actual data sets could be better and doesn’t make it easy for third parties to utilise the data.
Consider the LOS hierarchy for example. This simple hierarchy of concepts and topics is described at data.norge.no and the actual data set resides at difi.org. The LOS hierarchy is category scheme and suggested navigation structure for local government in Norway. The data, sadly, is published as an open document format spreadsheet file.
So, with data.networkedplanet.com and the Web3 Platform we have tried to demonstrate how organisations should publish data for it to be useful and easy for others to work with. To accompany the service we describe the key principles that have guided us.
1) Give unique persistent identifiers in the form or URLs to the terms in a vocabulary or ontology. E.g. http://data.networkedplanet.com/difi/los/themes/Arbeid. Is the immutable URI we have assigned to the concept for ‘work’ in the theme hierarchy.
2) Have human and machine representations for all the ‘things’ being published. Again consider the Arbied concept in Los. If developers creating mashups want to make use of the term in an application why would they want to create and store and manage a static copy when it is intended to be a common data set? At data.networkedplanet.com using the Web3 Platform we expose both human and machine representations of all concepts. See http://data.networkedplanet.com/difi/los/themes/Arbeid?format=rdf for the data representation of the Arbied/Work concept.
3) Make the data searchable. Developers and other users (CMS editors perhaps) want to know if certain terms exist. Exposing a full text concept search allows them to find the concepts that are interesting to them.
4) Make the data queryable. Full text search is useful for looking up, or checking that a given term is there. But structured data queries are what developers need to be able to best make use of the data. The Web3 Platform allows SPARQL queries to be run to explore and query the data. To see a list of all themes in LOS the follow URL encoded query can be used …
data.norge.no provides a great hub to discover data sets published by different organisations, but the value of the data they publish is only as good as the tools they offer to users to make use of that data. Networked Planet’s Web3 Platform allows organisations to quickly and easily publishing Linked Open Data in a way that is robust, long lasting and provides developers with data the way they want it.
Networked Planet Linked Data Article
A recent article about Linked Data has been published at Business Computing World.
Web3 Platform LOS Kommune Demo
To show how Linked Data and Semantic Technologies can help organisations publish richer information services we have created a small demonstrator at http://demo.networkedplanet.com/los. This demo uses the LOS theme hierarchy as a way to organise the access to services provided by local government. All the services, contacts and themes are accessible as Linked Data and there is a Linked Data SPARQL endpoint.
The following video provides a quick introduction to the features in the demo.
Concepts for SharePoint 1.2 released
Version 1.2 of Concepts for SharePoint is now available. This package introduces a number of features and enhancements. The full change list and upgrade instructions can be found below.
The Concepts for SharePoint package can be downloaded from the NetworkedPlanet download page.
Upgrading instructions
------------------
Unzip the download package and run the STSADM -upgradesolution command. The exact command-line you use will depend on how you want to schedule the upgrade, but will be similar to:
stsadm -o upgradesolution -name ConceptsForSharePoint.wsp -filename ConceptsForSharePoint.wsp -allowgacdeployment -local
Restart IIS and the SharePoint 2010 Timer Service
If running CfS on a separate server to that of the Web3 Platform, you will also need to upgrade the additional web3.wsp file contained in the upgrade package and restart the services.
For full upgrade and usage instructions, please refer to the documentation contained in the downloaded package
Change Log
----------
FEATURE: Added Concepts for SharePoint License Manager
FEATURE: User Profile Scraper SharePoint timer job added to pull SharePoint site collection users into the Web3 Platform
FEATURE: New Topic Web Part - adds a new topic from within the SharePointenvironment and redirects to the concept pahe for that topic.
ENHANCEMENT: Changes to the way the topic map is synchronized with the ManagedMetadata Service to speed up the overall synchronization process
ENHANCEMENT: Template mappings can now be configured to load up custom templatesfor concept pages for specific topics based on a topic's PSI
ENHANCEMENT: Related concepts added as a refinement to SharePoint Search
ENHANCEMENT: Additional language strings for Web Parts added to language resource file
ENHANCEMENT: Web Parts that use a starting topic can now be set to "Current User"
ENHANCEMENT: Base topic type concept page allows a new instance of that type to be added from within the SharePoint environment
New Releases of Web3 Platform and Concepts For SharePoint
NetworkedPlanet is pleased to announce the release of new versions of the Web3 Platform and Concepts for SharePoint products.
Web3 1.2
Web3 Platform 1.2 provides a number of bug fixes and performance enhancements over the previous 1.1 release and is a recommended download for all users. Links to the installation packages can be found on the NetworkedPlanet download page.
Upgrading from Web3 1.1
To upgrade from 1.1, unzip the installation package and run the installer application in Web3/setup.exe. During installation you will be prompted for database and service configuration information as you were during the initial installation. After installing Web3, you should also upgrade the Web3Admin package on any client machines that use the Powershell administration snap-in. Full installation and upgrade information can be found in the installation package.
Change Log
ENHANCEMENT: SPARQL query implementation now features partial query caching and query execution plan caching for significant performance improvements when processing repeated queries.
ENHANCEMENT: Major performance improvements for XTM import.
ENHANCEMENT: It is no longer necessary to specify the syntax of the uploaded data to the import job processor. The processor will probe the received data to determine the syntax of the content. As a result, the -Xtm20 flag has been removed from the Import-TopicMap cmdlet.
ENHANCEMENT: TopicRef representations now include a link to the referenced topic's type(s).
ENHANCEMENT: TMSPARQL queries now support the DISTINCT keyword.
BUGFIX: Fixed an issue with round-tripping XTM files through a Web3 export/import cycle
BUGFIX: Fixed the deletion of associations to ensure that all child roles are deleted from the database.
BUGFIX: Fixed rendering of RDF/XML topic representation when an item has a subject identifier that uses a fragment identifier.
BUGFIX: Fixed an issue with the License Manager that resulted in the registration form not displaying on some machines.
BUGFIX: Fixed problem with processing SPARQL queries with literal strings that contain special characters escaped by a backslash.
BUGFIX: Fixed jobs list to include failed jobs and to display jobs in descending order of last updated date/time.
Concepts for SharePoint 1.2
Concepts for SharePoint 1.2 provides a number of bug fixes and performance enhancements over the previous 1.1 release and is a recommended download for all users. Links to the installation packages can be found on the NetworkedPlanet download page.
Upgrading from CfS 1.1
The following steps must be completed to successfully upgrade from Concepts for SharePoint 1.1 to 1.2.
Further information about how to perform these steps is provided elsewhere in the Installation
documentation.
1.Install the License Manager found at <InstallDir>/ConceptsForSharePointLicenseManager.msi
2.Enter your license serial number and activate your license (or run in trial mode)
3.Upgrade the Concepts for SharePoint solution found at <InstallDir>/ConceptsForSharePoint.wsp
4.[OPTIONAL] If Concepts for SharePoint is not installed on the same server as the Web3 Platform, you
must also upgrade the web3.wsp solution (<InstallDir>/web3.wsp) to deploy the updated Web3
Platform assembly files to the local GAC
5.Add the assembly redirection configuration to the SharePoint Web Application's web.config file
(details of which are provided in the "Configuration" section of this document)
6.Restart IIS
7.Reactivate the NPConceptsForSharePoint feature on all site collections that use Concepts for
SharePoint using the force command where appropriate
8.Restart IIS
9.Restart the SharePoint 2010 Timer Service
Change Log
FEATURE: Added Concepts for SharePoint License Manager
FEATURE: User Profile Scraper SharePoint timer job added to pull SharePoint site collection users into the Web3 Platform
FEATURE: New Topic Web Part - adds a new topic from within the SharePoint environment and redirects to the concept pahe for that topic.
ENHANCEMENT: Changes to the way the topic map is synchronized with the Managed Metadata Service to speed up the overall synchronization process
ENHANCEMENT: Template mappings can now be configured to load up custom templates for concept pages for specific topics based on a topic's PSI
ENHANCEMENT: Related concepts added as a refinement to SharePoint Search
ENHANCEMENT: Additional language strings for Web Parts added to language resource file
ENHANCEMENT: Web Parts that use a starting topic can now be set to "Current User"
ENHANCEMENT: Base topic type concept page allows a new instance of that type to be added from within the SharePoint environment
REST in the Web3 Platform
One of the goals of the Web3 Platform was to adhere to as many of the architectural principles of REST that was possible. In our minds the key things were that:
1) Given a start URI and a description of all the content types and valid transitions a client could interact with the topic map store.
Yep, there is only that one point.
Given the URI of a topic map a client that is aware of the different content types that can be returned can interact with the entire topic map without guessing at, or constructing URIs.
For the Web3 Platform we introduced a new syntactic representation for Topic Maps because XTM is an interchange syntax for Topic Maps and not an effective Hypertext representation for the TMDM.
I'll walk through some interactions starting from a topicmap URL to demonstrate why we introduced the new syntax and how a client behaves.
Starting with the topicmap URL:
GET http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b?format=xml
When addressing Web3 Resources content negotiation can be done through accept headers or via a format parameter. The above GET returns the following representation.
<?xml version="1.0" encoding="utf-8"?>
<TopicMap xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
Id="e518129d-b458-4171-99cc-5e4941dafc7b"
Version="49"
LastModified="2010-09-22T08:44:56.65"
Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b"
WebLabel="myfilms"
Reifier="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/75746aa2-61a1-4303-9d4e-d9832e366e82"
Schema="http://localhost/web3/schemas/0df562f3-f86b-4fbb-a4d3-66679f2df0fa"
Associations="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/associations"
Topics="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics">
<Labels>
<Label Lang="en-gb">Films</Label>
</Labels>
</TopicMap>
There are a couple of things to notice in this representation.
- We use full URLs for everything, no Ids that need turning into URLs based on some defined URL space.
- We are exposing the collections of Topics and Associations as resources in their own right. This allows clients to POST to these collections to create new Topics and Associations and also to fetch these collections. (The full representation documentation also specifies the allowed query parameters for these resources).
Now a client can navigate the topic collection using:
GET http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics?format=xml
This returns the following collection:
<?xml version="1.0" encoding="utf-8"?>
<TopicRefList xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
Start="0" Count="29" Length="25"
ListUrl="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics"
Next="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics?skip=25&take=25"
Previous="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics?skip=-25take=25">
<Items>
<TopicRef Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/2a8a2182-f8b7-427a-9f7f-ef206b775606">
<Labels>
<Label Lang="en-gb">Harrison Ford</Label>
</Labels>
<Identifiers />
</TopicRef>
<TopicRef Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/dee5c82f-a6ab-4dcc-9e2b-4fbfcaefdc41">
<Labels>
<Label Lang="en-gb">Witness</Label>
</Labels>
<Identifiers />
</TopicRef>
<TopicRef Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/fc914a45-915c-49b1-baa8-8cf523de3425">
<Labels>
<Label Lang="en-gb">Star Wars</Label>
</Labels>
<Identifiers />
</TopicRef>
</Items>
</TopicRefList>
The interesting things in the snippet above are:
- We have introduced a generic list container for topics, in fact topic refs. This gives us control over thing like collection size and paging.
- We have introduced a lightweight topic reference structure for use in listing topics. This is a subset of the full topic representation and is used in many places.
- We are explicit about the topic's web address.
- We provided explicit links to navigate through the collection
All of the above means that a client who understands this content type can navigate to a topic, and find more results or the previous page of results.
Following a link to a topic using:
GET http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/2a8a2182-f8b7-427a-9f7f-ef206b775606?format=xml
Returns the following XML
<?xml version="1.0" encoding="utf-8"?>
<Topic xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
Id="2a8a2182-f8b7-427a-9f7f-ef206b775606" Version="54" LastModified="2010-09-22T08:46:34.36"
Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/2a8a2182-f8b7-427a-9f7f-ef206b775606"
TopicMapAddress="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b"
TopicAssociations="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/2a8a2182-f8b7-427a-9f7f-ef206b775606/associations">
<Labels>
<Label Lang="en-gb">Harrison Ford</Label>
</Labels>
<Identifiers />
<Types>
<Type Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/5c3c037f-0c13-457e-b177-fa3328d13370">
<Labels>
<Label Lang="en-gb">Person</Label>
</Labels>
<Identifiers>
<Identifier Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/5c3c037f-0c13-457e-b177-fa3328d13370/identifiers/32fafe54-0363-4e3a-bb3b-f8a565fc7e26" IdentifierType="ii">
http://localhost/web3/schemas/0df562f3-f86b-4fbb-a4d3-66679f2df0fa/types/16f22191-5fd7-4f15-8014-f4fc28b1563e
</Identifier>
<Identifier Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/5c3c037f-0c13-457e-b177-fa3328d13370/identifiers/5ab286fc-3e7b-43bd-949f-1766860fb2f3" IdentifierType="si">
http://www.myfilms.com/types/person
</Identifier>
</Identifiers>
</Type>
</Types>
<Properties>
<Property Id="526c5a91-302c-4138-b8cb-35e5b7b19d2e" Version="54" LastModified="2010-09-22T08:46:34.36" Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/2a8a2182-f8b7-427a-9f7f-ef206b775606/properties/526c5a91-302c-4138-b8cb-35e5b7b19d2e" TopicAddress="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/2a8a2182-f8b7-427a-9f7f-ef206b775606">
<Type Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/cb3832ab-7c9b-4ec7-a20e-112dd9b133c3">
<Labels>
<Label Lang="en-gb">Biography</Label>
</Labels>
<Identifiers>
<Identifier Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/cb3832ab-7c9b-4ec7-a20e-112dd9b133c3/identifiers/a2b3bb57-3313-4432-b485-bd08703f1495" IdentifierType="si">
http://www.myfilms.com/types/biography
</Identifier>
<Identifier Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/cb3832ab-7c9b-4ec7-a20e-112dd9b133c3/identifiers/a314af53-a940-4b7a-a92b-ad2d761ef2c7" IdentifierType="ii">
http://localhost/web3/schemas/0df562f3-f86b-4fbb-a4d3-66679f2df0fa/types/45ba8b1a-a80c-40c6-8fb6-7d1692c0da7b
</Identifier>
</Identifiers>
</Type>
<Value xsi:type="xsd:string">Born in the 1940's</Value>
<Scope />
</Property>
</Properties>
</Topic>
Points of interest in the above snippet are:
- The link to the associations for the topic. With this we have created a resource that can be navigated to return the associations in which the topic plays a role. (There are optional query parameters on this as well.)
- We use inline topic ref elements to minimise round trips for common things, such as property types and topic types.
- All contained resources, property (is name or occurrence) and identity expose their web address.
- We have also included version information to help with ETag processing.
Finally, following the associations link using:
http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/2a8a2182-f8b7-427a-9f7f-ef206b775606/associations?format=xml
We get back the following XML structure:
<?xml version="1.0" encoding="utf-8"?>
<AssociationList xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
Start="0" Count="0" Length="3"
ListUrl="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/2a8a2182-f8b7-427a-9f7f-ef206b775606/associations?type="
Next="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/2a8a2182-f8b7-427a-9f7f-ef206b775606/associations?type=&skip=3&take=3"
Previous="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/2a8a2182-f8b7-427a-9f7f-ef206b775606/associations?type=&skip=-3take=3">
<Items>
<Association Id="033426d3-90fb-4501-9372-cafa7e46cc53" Version="53" LastModified="2010-09-22T08:45:44.507"
Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/associations/033426d3-90fb-4501-9372-cafa7e46cc53"
TopicMapAddress="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b">
<Type Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/042c8aad-1d32-48d8-9d71-2ed5a9a30b04">
<Labels />
<Identifiers>
<Identifier Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/042c8aad-1d32-48d8-9d71-2ed5a9a30b04/identifiers/be689f59-e07a-4594-abd1-6d4d0457ee1d" IdentifierType="si">http://psi.topicmaps.org/iso13250/model/type-instance</Identifier>
</Identifiers>
</Type>
<Scope />
<Roles>
<Role Id="6bb8e97c-ad0a-469f-8578-e77e2b383e27">
<Player Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/2a8a2182-f8b7-427a-9f7f-ef206b775606">
<Labels>
<Label Lang="en-gb">Harrison Ford</Label>
</Labels>
<Identifiers />
</Player>
<Type Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/65239824-ebdb-4f14-bd10-7bc66ffb772e">
<Labels />
<Identifiers>
<Identifier Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/65239824-ebdb-4f14-bd10-7bc66ffb772e/identifiers/a9cbb6c7-7729-4834-bc0d-cba517ad4672" IdentifierType="si">http://psi.topicmaps.org/iso13250/model/instance</Identifier>
</Identifiers>
</Type>
</Role>
<Role Id="82cf9263-4951-4c0f-a536-e940ce9f17f0">
<Player Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/5c3c037f-0c13-457e-b177-fa3328d13370">
<Labels>
<Label Lang="en-gb">Person</Label>
</Labels>
<Identifiers>
<Identifier Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/5c3c037f-0c13-457e-b177-fa3328d13370/identifiers/32fafe54-0363-4e3a-bb3b-f8a565fc7e26" IdentifierType="ii">http://localhost/web3/schemas/0df562f3-f86b-4fbb-a4d3-66679f2df0fa/types/16f22191-5fd7-4f15-8014-f4fc28b1563e</Identifier>
<Identifier Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/5c3c037f-0c13-457e-b177-fa3328d13370/identifiers/5ab286fc-3e7b-43bd-949f-1766860fb2f3" IdentifierType="si">http://www.myfilms.com/types/person</Identifier>
</Identifiers>
</Player>
<Type Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/e3746d43-ce02-45c5-9d2d-c244fcbbd9e3">
<Labels />
<Identifiers>
<Identifier Address="http://localhost/web3/topicmaps/e518129d-b458-4171-99cc-5e4941dafc7b/topics/e3746d43-ce02-45c5-9d2d-c244fcbbd9e3/identifiers/d3d79a3b-84fc-433a-8251-306a8bcc3e74" IdentifierType="si">http://psi.topicmaps.org/iso13250/model/type</Identifier>
</Identifiers>
</Type>
</Role>
</Roles>
<Identifiers />
</Association>
</Items>
</AssociationList>
So the key things we wanted to do was to create a set of content types that along with a description allowed a client to interact with a Topic Map without the need to refer to or know how to generate ANY URIs.
The examples above have shown how we have updated the core TMDM items, topic, association, occurrence etc to be better REST citizens, and we have also introduced new resources for collections of things in the topic map model. These collections are key to connecting together the basic topic map building blocks.
The full content type descriptions, including update semantics, are available as part of the Web3 Documentation which can be downloaded from http://www.networkedplanet.com/Products/Web3/
We also recently posted about how we support transactions in a RESTful way. This can be seen here.
Web3 Platform Video – Getting Started No 1.
We are putting together a series of short videos that show how to do different things with the Web3 Platform and Concepts for SharePoint. The first of these videos, Web3 Platform Getting Started No 1. is now available.
The Web3 Platform is a complete data driven environment. This means that with no code you can create a data model and immediately begin to add data either through the generated UI or via the RESTful interface. The first video shows how to create a simple schema using the Silverlight editor and then create topics and associations through the schema driven editor.
Concepts for SharePoint 1.1 now available
Version 1.1 of Concepts for SharePoint is now available. This package addresses a small number of bugs and enhancements. The full change list and upgrade instructions can be found below.
The Concepts for SharePoint package can be downloaded from the NetworkedPlanet download page.
Upgrading from 1.0
------------------
To upgrade from 1.0, unzip the download package and run the STSADM -upgradesolution command. The exact command-line you use will depend on how you want to schedule the upgrade, but will be similar to:
stsadm -o upgradesolution -name ConceptsForSharePoint.wsp -filename ConceptsForSharePoint.wsp -allowgacdeployment -local
Restart IIS and the SharePoint 2010 Timer Service
If running CfS on a separate server to that of the Web3 Platform, you will also need to upgrade the additional web3.wsp file contained in the upgrade package and restart the services.
Change Log
----------
BUGFIX: Query amended to ensure sure that deleted associations whose roles still exist do not get returned in the results of the One Hop Web Part.
FEATURE: New Topic List Web Part renders gridview of topics of type, with custom propertie to show occurrences and/or identifiers in the results set.
DOCS: Amended documentation error that specified the wrong format for message
queues on remote machines.
LOGGING: Additional logging added to make it clear if there has been a security problem when activating the feature through the GUI.
BUGFIX: Documents were not being returned in the content query web parts along with list items.
ENHANCEMENT: Allowed sparql results to be picked up and used by classes which inherit from web parts doing SPARQL queries.
BUGFIX: Null reference exception for starting topic when first adding a TopicInformationWebPart to a page
DOCS: Added full documentation of the NetworkedPlanet.Web3.SharePoint.WebParts class
BUGFIX: Fixed error that was reported about thread aborted after setting topic map in CfS site settings
BUGFIX: template mapping bug fix
BUGFIX: Privileges error fixed when deriving from the BaseTopicWebPart
BUGFIX: adding a second label for a newly installed language pack had a bug which was causing the additional label(s) not to be added to the topic term
BUGFIX: Fixed bug that was causing the SPARQL web part not to render any content in certain situations
BUGFIX: content query web parts were displaying unhelpful error if the topic map had not yet been synchronised with the term store
