On Jul 7, 2010, at 07:03 , Hugo A.Garcia wrote:

> https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=776
>
> Summary: Component Library
> Product: OCL
> Version: 2.0-mainline
> Platform: All
> OS/Version: All
> Status: NEW
> Severity: critical
> Priority: P1
> Component: Deployment
> AssignedTo: orocos-dev [..] ...
> ReportedBy: hugo [dot] garcia [..] ...
> CC: orocos-dev [..] ...
> Estimated Hours: 0.0
>
>
> Created an attachment (id=606)
> --> (https://www.fmtc.be/bugzilla/orocos/attachment.cgi?id=606)
> XML Schema of Orocos Component
>
> Goal:
>
> To provide a list of available components, a component library, found by the
> Deployment Component in a manner such that the component library can be
> accessed by third party applications.
>
> Implementation:
>
> For each component found there will be a component descriptor which will be
> persisted using a defined XML format. The XML must be defined using an XML
> Schema. The component library will be create3d in the local file system of the
> host where other component are developed. The location of the component library
> in the file system might be set by the Deployment Component. The location of
> the component library might be set by the user of the Deployment Component.
>
> Attached:
>
> * The XML Schema of the Orocos Component Descriptor (OCD)
> * An example of an OCD

Can you provide a larger-picture use case for this? I see what it is, but what is it for, why, and what are the benefits, are the more interesting questions.
S