Académique Documents
Professionnel Documents
Culture Documents
Version: 1.0.14 File: EIP Job Model Attributes Last Revised: 07/25/11 Release Status: Approved
Generated by: Xerox Common Print Semantics Specification Working Group (CPSS WG) and the Extensible Interface Platform Team (EIP) Contact: Christine Miyachi Xerox Corporation Global Business Group (GBG)/ Solutions Business Team (SBT)/ Applications and Solutions Delivery Unit (ASDU)
ii
Table Of Contents
1. Introduction .................................................................................................................................... 7
1.1 Conformance Terminology .................................................................................................................................. 7 1.2 Terminology ........................................................................................................................................................ 7 1.3 Structure of the EIP Job Model ........................................................................................................................... 7 1.4 Processing an EIP Job Ticket ............................................................................................................................ 11 1.5 Attribute Types .................................................................................................................................................. 11
ColorEffectsType ................................................................................................................. 14 Copies (integer(1:MAX)) ..................................................................................................... 15 DateTimeAtCompleted (dateTime) ..................................................................................... 16 DateTimeAtCreation (dateTime)......................................................................................... 17 Finishings (keyword) ........................................................................................................... 18 InputTraysCol (1setOf collection) ........................................................................................ 22 Member Attributes for the InputTraysCol Device Description Attribute ............................................. 22 InputTrayName ( keyword | name(MAX)) .............................................................................................. 22 TrayLevel (integer(-1:100)) ..................................................................................................................... 22 JobId (name(MAX)) ............................................................................................................ 24 ClientId (name(MAX)) ......................................................................................................... 25 Job Forwarding ........................................................................................................................................ 25 JobIdentifier (collection) ...................................................................................................... 26 JobIdentifierType (type2 keyword) ......................................................................................................... 26 JobIdentifierString (name) ....................................................................................................................... 26 JobName (name(MAX))...................................................................................................... 27 JobState (keyword) ............................................................................................................. 28 Forwarding Servers: .................................................................................. Error! Bookmark not defined. Job Phases: Job Not Completed, Job Completed, Job Retention, Job History, Job Removal Error! Bookmark not define JobStateReasons (keyword)............................................................................................... 31 JobType (keyword) ............................................................................................................. 38 MediaCol (collection) .......................................................................................................... 40 FeedOrientation (type2 keyword) ............................................................................................................ 40 MediaColor (type3 keyword | name(MAX)) ............................................................................................ 40 MediaSize (collection) ............................................................................................................................. 42 XDimension(integer((1:MAX)) ........................................................................................................... 42 YDimension(integer((1:MAX)) ........................................................................................................... 42 MediaType (type3 keyword | name(MAX))............................................................................................. 42 SheetCollate (keyword) ...................................................................................................... 47 Sides (keyword) .................................................................................................................. 48 Scaling (collection) .............................................................................................................. 49 ScalingType (type2 keyword) .................................................................................................................. 49 ScaleProportional (collection) ................................................................................................................. 50
iii
iv
vi
1. Introduction
This specification defines the schemas assocated with the EIP Job Model. The Model defines data structures that describe job status, job status details, and job tickets. The semantics of the EIP Job Model are based on the CPSS (Common Print Semantic Specification) and have been extended to include attributes for other job types besides . The EIP Job Model also borrows its design from the Device Working Group (www.pwg.org) which has recently defined a job model for a Multi-Function Device (MFD).
2 3 4 5 6
7 8 9 10 11
12 13
1.2 Terminology
This section contains definitions of terminology used in this document.
Device In CPSS the term Device is the object that accepts CPSS operations that implement a Service, such as a Print Service or a Fax-Out Service. The Fax-Out Service may be implemented in a Multifunction Device (MFD), a dedicated Server, or as a software package running on a PC. In other parts of CPSS, the term Printer is used, since CPSS was originally focused only on the Print Service. However, any CPSS attribute conformance requirements specified for a Printer apply to a Fax-Out Server, if the Fax-Out Servier support the CPSS attribute in question. Conformance requirements are specified using the terms Device, Printer, Server, and Fax-Out Server, interchangeably. Output Device is the output module of the Device and a marker is the system that puts dots on output. These terms are NOT interchangeable with Device.
14 15
16 17 18 19 20 21
3 4 5 6 7 8
Figure 1 - The Job Queue Schema Each job in the queue, both active and completed, will contain the same information for each job. The one difference is that the completed job log will contain the time the job completed. The job ticket for the Copy Service is shown below. This schema defines the XML document which will be submitted to initiate a copy.
1 2 3 4 5 6 7 Figure 2 - The Copy Job Ticket Note all the optional attributes. If the attribute is not specified, the device default will be used on the MFD. The copy job ticket is limited in size to 10240 when used with the WS-CopyService WSDL. If details about a particular job are requested of the copy service, an XML document defined by the following schema is returned.
1 2 3 4 5 6 Figure 3 - The Copy Job details The JobInfo is the same JobInfo as defined in the job-queue. The copy-job-receipt is exactly the same as the copy-jobticket but all attributes are required. This receipt defines what actually was set on the job. The figure below represents basic Job Information returned in a job queue:
10
3 4 5 6 7 8 9
10 11 12
11
Same as XML schema dateTime 500 (five hundred) completed application/octetprint-stream Billy Lower-bound value is 1 Upper-bound value is 99,999
2 3
12
13
ColorEffectsType
Vernacular Names Service type Summary Output Color Print, Copy Render full color document in full color or grayscale.
Description
This attribute indicates whether a color document should be rendered in full color or should be rendered using an algorithm that maps the full range of colors to alternate values, such as gray scale or monochrome. This capability allows a full color document to render to a color document in monochrome or grayscale or black and white as a way to save time, toner, or cost when proofing a document. If the Device supports this attribute, it MUST support the Color and MonochromeGrayscale values. If a color Device does not support this attribute, the Device MUST provide the Color behavior. Black and white Devices and highlight color Devices MUST NOT support this attribute. Standard keyword values are:
Keyword Color Monochrome Grayscale Description all color content of the document MUST be preserved and rendered in color. the color content of the input document should be identified and an implementation-dependent algorithm MUST be applied to map the document colors to various intensities of black and white. Automatically detect the color when scanning the document and use that setting on the output.
Auto
19 20 21 22 23
14
Copies (integer(1:MAX))
Vernacular Names Service type Description Copies, Quantity Print, Copy This attribute specifies the number of copies to be printed. On many devices the supported number of collated copies will be limited by the number of physical output bins on the device, and may be different from the number of uncollated copies which can be supported
15
DateTimeAtCompleted (dateTime)
Service type Description Generic This OPTIONAL attribute indicates the date and time at which the Job completed (or was cancelled or aborted).
16
DateTimeAtCreation (dateTime)
Service type Status Description Generic Draft This OPTIONAL attribute indicates the date and time at which the Job was created..
17
Finishings (keyword)
Vernacular Names Service type Finsihings Print, Copy This finishings attribute identifies the finishing operations that the Device uses for each copy of each document in the Job This element contains three subelements StapleFinishing PunchFinishing FoldFinishing Standard values are: Table 5-2: Generic "Finishings" values
Name and Description of Finishing Values Name and Description of Staple Finishing Values None: Perform no finishing OneStaple: Add one staple TwoStaple: Add two staples ThreeStaple: Add three staples FourStaple: Add four staples Staple: Bind the document(s) with one or more staples. The exact number and placement of the staples is site-defined. StapleTopLeft: Bind the document(s) with one or more staples in the top left corner. StapleBottomLeft: Bind the document(s) with one or more staples in the bottom left corner. StapleTopRight: Bind the document(s) with one or more staples in the top right corner. StapleBottomRight: Bind the document(s) with one or more staples in the bottom right corner. EdgeStitchLeft: Bind the document(s) with one or more staples (wire stitches) along the left edge. The exact number and placement of the staples is implementation and/or sitedefined. EdgeStitchTop: Bind the document(s) with one or more staples (wire stitches) along the top edge. The exact number and placement of the staples is implementation and/or sitedefined. EdgeStitchRight: Bind the document(s) with one or more staples (wire stitches) along the right edge. The exact number and placement of the staples is implementation and/or sitedefined.
Description
18
19
Punch2HoleLeft: Punch two holes along the left edge. The exact placement of the
holes is implementation and/or site-defined
Punch2HoleTop: Punch two holes along the top edge. The exact placement of the
holes is implementation and/or site-defined
Punch2HoleRight: Punch two holes along the right edge. The exact placement of the
holes is implementation and/or site-defined
Punch2HoleBottom: Punch two holes along the bottom edge. The exact placement
of the holes is implementation and/or site-defined
Punch3HoleLeft: Punch three holes along the left edge The exact placement of the
holes is implementation and/or site-defined
20
Punch3HoleRight: Punch three holes along the right edge. The exact placement of
the holes is implementation and/or site-defined
Punch3HoleBottom: Punch three holes along the bottom edge. The exact
placement of the holes is implementation and/or site-defined
Punch4HoleLeft: Punch four holes along the left edge. The exact placement of the
holes is implementation and/or site-defined
Punch4HoleTop: Punch four holes along the top edge. The exact placement of the
holes is implementation and/or site-defined
punch-4-hole-right: Punch four holes along the right edge. The exact placement of
the holes is implementation and/or site-defined
Punch4HoleRight: Punch four holes along the bottom edge. The exact placement of
the holes is implementation and/or site-defined
Punch4HoleBottom: Punch four holes along the bottom edge. The exact placement
of the holes is implementation and/or site-defined Name and Description of Fold Finishing Values None: Perform no finishing Fold: Fold the document(s) with one or more folds. The exact number and orientations of the folds and whether or not they are concave or convex with respect to Side 1 of the sheet is implementation and/or site-defined.
21
Description
This attribute uses collections to identify the current state of input trays. Each collection returned by the InputTraysCol attribute in the future, will identify the media configured for each tray of the Device, plus device capability and status information including tray name, feed orientation, tray capacity, tray status, the current level of media in the tray, and the position of the tray relative to the fuser. For EIP presently only the input tray name is in this collection.
integer (-1:100)
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
TrayLevel (integer(-1:100))
The TrayLevel element indicates the percentage of the capacity remaining in the tray. The value returned is a percentage of the maximum of media that can be put into the tray. A value of 0 indicates that there is no media remaining, or that only a small amount of media remains in the tray which cannot be fed by the device without more sheets being loaded, depending on the implementation. Whether the defaults switches to another tray or faults when it tries to feed from this tray when the value is 0 is implementation dependent.
22
23
JobId (name(MAX))
Service type Status Description Print, Copy Draft This REQUIRED attribute contains the ID of the job. The Device, on receipt of a new job, generates an ID which identifies the new Job on that Device. The Device returns the value of the JobId attribute as part of the response to a create request. The 0 value is not included to allow for compatibility with SNMP index values which also cannot be 0.
24
ClientId (name(MAX))
Service type Status Summary Generic draft Allows the client to supply a job identifier that clients can query to determine status of the job by scanning jobs returned by the Device in obtain job status and/or use for human communication with the Devices operator.
Description
The client OPTIONALLY supplies this attribute. The Device object OPTIONALLY supports this attribute. It contains a job identifier created by the client. The client MAY automatically include any information that will help the client distinguish amongst the jobs that it has submitted.
Job Forwarding
When a Device forwards a job, the jobs ClientId is forwarded as received by the Device. In other words, these values are preserved throughout the workflow that involved Job Forwarding (rather than being changed to the JobId value generated by the Device that is performing the Job Forwarding).
25
JobIdentifier (collection)
Service type Status Description Generic draft The JobIdentifier attribute is used to specify what type of job identification is being used and the value for that identifier.
8 9 10 11 12 13 14 15 16 17 18 19 20
JobIdentifierString (name)
The JobIdentifierString member attribute specifies the vlaue for the identifier specified in the JobIdentifierType member attribute.
26
JobName (name(MAX))
Service type Status Description Generic Draft The client OPTIONALLY supplies this attribute. The Device object MUST support this attribute. It contains the client supplied Job name. If this attribute is supplied by the client, its value is used for the JobName attribute of the newly created Job object. The client MAY automatically include any information that will help the enduser distinguish amongst his/her jobs, such as the name of the application program along with information from the document, such as the document name, document subject, or source file name. If this attribute is not supplied by the client, the Device generates a name to use in the JobName attribute of the newly created Job object
27
JobState (keyword)
Service type Description Generic This REQUIRED attribute identifies the current state of the job. Implementations only need to support those states which are appropriate for the particular implementation. Standard enum values are:
Symbolic Name and Description Pending: The job is a candidate to start processing, but is not yet processing. PendingHeld: The job is not a candidate for processing for any number of reasons but will return to the pending state as soon as the reasons are no longer present. The jobs JobStateReasons attribute MUST indicate why the job is no longer a candidate for processing. Processing: One or more of: 1. The job is using, or is attempting to use, one or more purely software processes that are analyzing, creating, or interpreting a PDL, etc., 2. The job is using, or is attempting to use, one or more hardware devices that are interpreting a PDL, making marks on a medium, and/or performing finishing, such as stapling, etc., 3. The Device object has made the job ready for printing, but the output device is not yet printing it, either because the job hasnt reached the output device or because the job is queued in the output device or some other spooler, awaiting the output device to print it. When the job is in the processing state, the entire job state includes the detailed status represented in the Device objects Device-state, Device-statereasons, and Device-state-message attributes. Implementations MAY, though they NEED NOT, include additional values in the jobs JobStateReasons attribute to indicate the progress of the job, such as adding the job-printing value to indicate when the output device is actually making marks on paper and/or the processing-to-stop-point value to indicate that the CPSS object is in the process of canceling or aborting the job. Most implementations wont bother with this nuance. ProcessingStopped: The job has stopped while processing for any number of reasons and will return to the processing state as soon as the reasons are no longer present. The jobs JobStateReasons attribute MAY indicate why the job has stopped processing. For example, if the
28
1 2 3 4 5 6 7 8 9 10 11 12
The final value for this attribute MUST be one of: Completed, Canceled, or Aborted before the Device removes the job altogether. The length of time that jobs remain in the Canceled, Aborted, and Completed states depends on implementation. The following figure shows the normal job state transitions
+ Canceled / + Pending Processing --------- + Completed | ^ ^ \ + | | + Aborted | v v / + PendingHeld ProcessingStopped --+
29
30
JobStateReasons (keyword)
Service type Summary Generic Augments the "JobState" attribute to give more detailed information about this Jobs state. There can be more than one keyword in this element.
Description
This REQUIRED attribute provides additional information about the job's current state, i.e., information that augments the value of the job's "JobState" attribute. These values MAY be used with any job state or states for which the reason makes sense. Some of these value definitions indicate conformance requirements; the rest are OPTIONAL. Furthermore, when implemented, the Device MUST return these values when the reason applies and MUST NOT return them when the reason no longer applies whether the value of the Job's "JobState" attribute changed or not. When the Job does not have any reasons for being in its current state, the value of the Job's "JobStateReasons" attribute MUST be 'none'. Note: While values cannot be added to the 'JobState' attribute without impacting deployed clients that take actions upon receiving "JobState" values, it is the intent that additional "JobStateReasons" values can be defined and registered without impacting such deployed clients. In other words, the "JobStateReasons" attribute is intended to be extensible. When this attribute contains more than one reason, the reasons MUST be ordered with the most important first and the least important last. The most important is usually the reason that caused the last state transition. The determination of the importance of a state reason is implementation specific. The level of severity associated with a reason indicates its importance. Error is more important than warning and warning is more important than report. The following standard keyword values are defined. For ease of understanding, the values are presented in the order in which the reasons are likely to occur (if implemented), starting with the 'JobHoldUntil-specified' value: None: There are no reasons for the jobs current state. This state reason is semantically equivalent to JobStateReasons without any value and MUST be used when there is no other value, since the 1setOf attribute syntax requires at least one value. JobHoldUntilSpecified: The value of the jobs JobHoldUntil attribute was specified with a time period that is still in the future. The job MUST NOT be a candidate for processing until this reason is removed and there are no other reasons to hold the job. This value SHOULD be supported if the JobHoldUntil Job Template attribute is supported. JobHeldOnCreate: The job is currently being held in the PendingHeld state because the operator had previously issued a Hold-New-Jobs Device operation (see Section 2.4 of CPSS
31
ResourcesAreNotSupported: At least one of the resources needed by the job, such as media, fonts, resource objects, etc., is not supported on any of the physical Devices for which the job is a candidate. This condition MAY be detected when the job is accepted, or subsequently while the job is pending or processing, depending on implementation. The job may (1) remain in its current state, (2) be moved to the PendingHeld state, depending on implementation and/or job scheduling policy, or (3) scheduled normally, but the Device is put into the stopped state when the job is attempted to be processed on the Device. ResourcesAreNotReady: At least one of the resources needed by the job, such as media, fonts, resource objects, etc., is not ready on any of the physical Devices for which the job is a candidate. This condition MAY be detected when the job is accepted, or subsequently while the job is pending or processing, depending on implementation. The job may remain in its current state or be moved to the PendingHeld state, depending on implementation and/or job scheduling policy. JobIncoming: Either (1) the Device has accepted the Create-Job operation and is expecting additional Send-Document and/or Send-URI operations or (2) the Device is retrieving/accepting document data as a result of a Print-Job, Print-URI, SendDocument or Send-URI operation. JobSpooling: Same as JobIncomingwith the specialization that the Device is spooling the document data before processing it. This value corresponds to the spool or automatic value of the jobspooling-supported Device Description attribute.
32
33
34
35
36
37
38
JobType (keyword)
Vernacular Names Service type Description Job Type Generic This attributre defines the type of job being returned.
39
40
MediaCol (collection)
Vernacular Names Service type Status Description MediaCol Print, Copy Draft This MediaCol attribute identifies the characteristics of a media. . Each member attribute of the collection identifies a media characteristic.
10 11 12 13 14 15
16 17 18 19 20 21
41
42
1 2 3 4 5 6
MediaSize (collection)
The OPTIONAL MediaSize member attribute is a collection that explicitly specifies the numerical XDimension(short edge) and YDimension(long edge) of the media instance. The MediaSize collection member attributes are:
Member Attribute Name XDimension YDimension Attribute Syntax
integer((1:MAX) integer((1:MAX)
7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
XDimension(integer((1:MAX)) The XDimension member attribute indicates the size of the media in hundredths of a millimeter along the bottom(short) edge of the media. This unit is equivalent to 1/2540 th of an inch resolution. YDimension(integer((1:MAX)) The YDimension member attribute indicates the size of the media in hundredths of a millimeter along the left(long) edge of the media. This is equivalent to 1/2540 th of an inch resolution. The specified XDimension value MUST be less than or equal to the YDimension value.
Cardstock
43
CardstockExtraHeavyweightGlossy
CardstockExtraHeavyweightGlossyReloaded
CardstockHeavyweight
CardstockHeavyweightGlossy
CardstockHeavyweightGlossyReloaded
CardstockHeavyweightReloaded
CardstockLightweight
CardstockLightweightReloaded
CardstockPostcard
44
Coverstock
Custom1 Custom10 Custom11 Custom12 Custom13 Custom14 Custom15 Custom16 Custom17 Custom18 Custom19 Custom2 Custom20 Custom3 Custom4 Custom5 Custom6 Custom7 Custom8 Custom9 Drilled
45
LabelsHeavyweight
Other
PaperBackedTransparency
Photographic
PreCutTabs
PreCutTabsHeavyweight
StationeryHeavyweightGlossyReloaded
StationeryLetterhead
46
StationeryLightweightGlossy
StationeryLightweightGlossyReloaded
StationeryLightweightReloaded
StationeryPrePrinted StationeryRecycled
StationeryReloaded
StationeryRoughSurface
47
SheetCollate (keyword)
Vernacular Names Service type Status Description Collated Print, Copy Draft This attribute specifies whether or not the media sheets of each copy of each document in a job are to be in sequence, when multiple copies of the document are specified by the Copies attribute. For example, suppose a document produces two media sheets as output, and copies is equal to 6, For the uncollated case, six copies of the first media sheet are ed followed by six copies of the second media sheet. For the collated case, one copy of each of the six sheets are ed followed by another copy of each of the six media sheets. Whether the effect of sheet collation is achieved by placing copies of a document in multiple output bins or in the same output bin with implementation defined document separation is implementation dependent. Also whether it is achieved by making multiple passes over the job or by using an output sorter is implementation dependent. Standard keyword values are:
Keyword Uncollated Description Each print-stream sheet is printed a number of times in succession equal to the value of the Copies attribute, followed by the next printstream sheet. Each copy of each document is ed with the printstream sheets in sequence, followed by the next document copy.
Collated
21 22 23
48
Sides (keyword)
Vernacular Names Service type Description Sides Imaged Print, Copy This attribute specifies how print-stream pages are to be imposed upon the sides of an instance of a selected medium, i.e., an impression. It also specifices how pages are interpreted when being scanned. Thus it is used as both an input and an output attribute for a job ticket. The Standard keyword values are:
Keyword OneSided TwoSidedLong Edge Description imposes each consecutive print-stream page upon the same side of consecutive media sheets. imposes each consecutive pair of print-stream pages upon front and back sides of consecutive media sheets, such that the orientation of each pair of print-stream pages on the medium would be correct for the reader as if for binding on the long edge. imposes each consecutive pair of print-stream pages upon front and back sides of consecutive media sheets, such that the orientation of each pair of print-stream pages on the medium would be correct for the reader as if for binding on the short edge.
TwoSidedShort Edge
10
TwoSided imposes each consecutive pair of print-stream pages upon front and back sides of consecutive media sheets; used when the orientation specification does not matter to the service, sucy as copy.
11 12
49
Scaling (collection)
Vernacular Names Service type Description Magnification, ReduceEnlarge, Scaling Copy This Scaling attribute specifies how the images should be scaled. The image may be scaled in both the x and the y directions.
8 9 10 11 12 13
AutoIndependent
Proportional
Independent
50
ScaleProportional (collection)
The OPTIONAL ScaleProportional member attribute is a collection that is used to specify that the sides of the image will be scaled proportionally. This member attribute must only be used when the ScalingType attribute is set to Proportional. The ScaleProportional collection member attributes are:
Member Attribute Name ScalingValue Attribute Syntax
rangeOfInteger
7 8 9 10 11 12 13 14 15 16
ScalingValue(rangeOfInteger) The ScalingValue member attribute specifies the percentage an image should be scaled. The valid values can be from 25% all the way up to 400%.
ScaleIndependent (collection)
The OPTIONAL ScaleIndependent member attribute is a collection that is used to specify that the sides of the image will be scaled indepently. This member attribute must only be used when the ScalingType attribute is set to Independent. The ScaleIndependent collection member attributes are:
Member Attribute Name XScaling YScaling Attribute Syntax
rangeOfInteger rangeOfInteger
17 18 19 20 21 22 23 24 25
XScaling(rangeOfInteger) The XScaling member attribute specifies the percentage an image should be scaled in the x direction. The valid values can be from 25% all the way up to 400%. YScaling(rangeOfInteger) The YScaling member attribute specifies the percentage an image should be scaled in the y direction. The valid values can be from 25% all the way up to 400%.
51
3. APPENDIX A: References
This Appendix provides additional references to documents. References to this Appendix are indicated in square brackets using hot links. Cross Reference Symbol (in alphabetic order) Access Token Auditron Reference Document Title, Description, and URL
2 3 4
Multimedia systems and equipment - Colour measurement and management - Part 21: Colour management - Default RGB colour space - sRGB ISO 838: 1974. Paper -- Holes for general filing purposes -- Specifications. Specifies the hole sizes and spacing. Job Definition Format (JDF), Versions 1.0, 1,1, 1,2, 1.3, and 1.4 are available from http://www.cip4.org. The Lightweight Directory Access Protocol, or LDAP (pronounced el dap) is an application protocol for querying and modifying directory services running over TCP/IP. Its current version is LDAPv3, which is specified in a series of Internet Engineering Task Force (IETF) Standard Track Requests for comments (RFCs) as detailed in [RFC 4510]. http://en.wikipedia.org/wiki/Pluggable_Authentication_Modules. http://www.opengroup.org/onlinepubs/8329799/chap4.htm PWG 5101.1-2002 Standardized Media Type Names. Available as: ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn10-20020226-5101.1.pdf Device Working Group - Semantic Model, PWG IEEE-ISTO 5100.1-2004 [RFC 2806] Vaha-Sipila, A., URLs for Telephone Calls, RFC 2806, April 2000. Available at: http://tools.ietf.org/html/rfc2806 which describes the tel: and fax: URL schemes, among others. This RFC is obsoleted by [RFC 3966]
[Error! Reference source not found.] [Error! Reference source not found.] [PWG5101.1-2002] [pwg-sm] [RFC 2806]
52
53
1.0.4 1.0.5
8/11/10 8/24/10
J. Howell C. Miyachi
1.0.13
04/20/11
C. Miyachi
54