Geoscience Reference
In-Depth Information
1
<ObjectEnvelope><!
-- ObjectEnvelope (OEN)--
>
2
<Object>
3
<Filename>GIS_Case_Study_20090804.jpg</Filename>
4
<Md5sum>...</Md5sum>
5
<Sha1sum>...</Sha1sum>
6
<DateCreated>2010-08-01:221114</DateCreated>
7
<DateModified>2010-08-01:222029</DateModified>
8
<
ID
>...</
ID
><CertificateID>...</CertificateID>
9
<Signature>...</Signature>
10
<Content><ContentData>...</ContentData></Content>
11
</Object>
12
</ObjectEnvelope>
Listing 7. Example for an Object Envelope (OEN).
An end-user public client application may be implemented via a browser plugin, based
on appropriate services. With OEN instructions embedded in envelopes, for example as
XML-based element structure representation, content can be handled as content-stream or as
content-reference. The way this will have to be implemented for different use cases depends
on the situation, and in many cases on the size and number of data objects. Listing 8 shows a
small example for an OEN file using a content DataReference.
1
<ObjectEnvelope><!
-- ObjectEnvelope (OEN)--
>
2
<Object>
3
<Filename>GIS_Case_Study_20090804.jpg</Filename>
4
<Md5sum>...</Md5sum>
5
<Sha1sum>...</Sha1sum>
6
<DateCreated>2010-08-01:221114</DateCreated>
7
<DateModified>2010-08-01:222029</DateModified>
8
<
ID
>...</
ID
><CertificateID>...</CertificateID>
9
<Signature>...</Signature>
10
<Content><DataReference>https://doi...</DataReference></Content>
11
</Object>
12
</ObjectEnvelope>
Listing 8. OEN referencing signed data.
9.8 Implemented solution for integrated systems with massive resources requirements
For most interactive information system components a configuration of the distributed
resources environment was needed. In opposite to OEN use, making it necessary to have
referenced instead of embedded data for huge data sets, for CEN it should be possible to
embed the essential instruction data. So there is less need for minimising data overhead
and communication. Envelope technology is meant to be a generic extensible concept for
information and computing system components (Rückemann, 2011). Figure 12 shows the
workflow with application scenarios from GEXI case studies (Rückemann, 2010b). Future
objectives for client components are:
• Channels for limiting communication traffic,
• Qualified signature services and accounting,
• Using signed objects without verification,
• Verify signed objects on demand.
Search WWH ::
Custom Search