Project

General

Profile

« Previous | Next » 

Revision 5268

Fixed typos in metacat documentation.

View differences:

docs/dev/metacat/source/identifiers.txt
22 22
  the syntax 'scope.object.revision', such as 'foo.34.1' (we will refer to
23 23
  these as 'LocalIDs'). We now want Metacat to support identifiers that are 
24 24
  arbitrary strings, but still enforce uniqueness and proper revision
25
  handling (referred to these as GUIDs).  Metacat must be able to accept 
25
  handling (refer to these as GUIDs).  Metacat must be able to accept 
26 26
  these strings as identifiers for all CRUD operations, and reference them 
27 27
  in search results.
28 28

  
......
32 32
and that LocalID has a constrained structure that includes semantics about
33 33
revisions in the identifier, it is difficult to wholesale replace it with
34 34
less-constrained string identifiers without re-writing much of Metacat.
35
Thus, our alternate strategy would is to wrap the Metacat APIs with a
35
Thus, our alternate strategy is to wrap the Metacat APIs with a
36 36
identifier resolution layer that keeps track of the unconstrained GUIDs and
37 37
maps them to constrained local identifiers which are used internally within
38 38
Metacat. The basic identifer table model is shown in Figure 1, while the
39
basic strategy for retrieving an object is shown in Figure 2.
39
basic strategy for retrieving an object is shown in Figure 2, creating an 
40
object is shown in Figure 3, updating an object in Figure 4, and deleting
41
an object is shown in Figure 5.
40 42

  
41 43

  
42 44
Identifier Table Structure

Also available in: Unified diff