Linked Data

Simplistically linked data can be thought of as a mechanism to link resources in different repositories, where the link is owned by one resource with a role. So as shown in the image, the gear "ABC" product in the blue "PDM" repository has a link to the simulation "123" in the orange "SDM, and that link has a role "hasSimulation".

Web services are then use the link to Get/Read information about that resource.

Key features are linked data are:

• No information or data is contained in the link.
• The link is used to accesses information and services on-the-fly from provider repository, thereby always retrieving the latest information, and removing the need to replicate data and services across repositories.
• Security is provided using authentication on the web service request.
• Information returned can include links to other resources, leading to progressive discovery.
• Issue: maintenance of link references - if the resource moves then the link is broken and the host has no way to notify the consumers of the resource.
• Allowing routes from Extended Enterprise directly into repositories raises security concerns.

Key features are shared/exchanged data are:

• Selected information and/or data sent between repositories and stored locally
• Suitable for hub+firewall installations to minimize security concerns
• Schedule/managed synchronization is needed for updates or changes
• Issue: services and data need to be replicated across repositories

OSLC

OSLC defines standard services (RESTful) e.g. Create, Query, Select, Display Preview/Dialog. Rather than use an existing standard, OSLC has started to define its own OSLC-specific domain language for the content (payload) of the resources.

One of the tasks for the MoSSEC project is to determin if it is possible to use the OSLC standard services, but use a MoSSEC payload rather then the OSLC-specific payload.