Digital camera and image data recording method
Summary by NHIP
Digital camera metadata synchronization
The digital camera creates metadata and records it in two distinct file formats within a recording medium. An update judgment section compares metadata between these files, and a synchronizing section replaces non-updated metadata with updated metadata only when a change is detected.
Claim Score by NHIP
Abstract
A digital camera includes an image shooting section which obtains at least one set of image data by shooting. A metadata creating section creates metadata including a plurality of data elements indicative of information concerning the at least one set of image data obtained by the image shooting section. A recording section records in a recording medium at least one file having a first format in which metadata is added to the at least one set of image data and a file having a second format including metadata only.

Term
Term ended
Expired 20 August 2026, 0.1 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
11 claims: 3 independent, 8 dependent
- 1A digital camera comprising:an image shooting section which obtains at least one set of image data by shooting;a processor;a metadata creating section of processor-executable instructions which, when executed by the processor, creates metadata comprising a plurality of data elements indicative of information concerning the at least one set of image data obtained by the image shooting section;a recording section which records in a recording medium at least one file having a first format in which the metadata is added to the at least one set of image data and a file having a second format comprising the metadata only;an update judgment section of processor-executable instructions which, when executed by the processor, judges whether one of the metadata included in the at least one file having the first format and the metadata included in the file having the second format is updated;and a metadata synchronizing section of processor-executable instructions which, when executed by the processor, controls the synchronization of the metadata, wherein controlling the synchronization of the metadata includes synchronizing the metadata included in the file having the first format with the metadata included in the file having the second format by replacing the metadata which has not been updated with the updated metadata if the update judgment section judges that one of the metadata included in the at least one file having the first format and the metadata included in the file having the second format is updated, otherwise not synchronizing the metadata.
- 6A digital camera comprising:an image shooting section which obtains at least one set of image data by shooting;a processor;a metadata creating section of processor-executable instructions which, when executed by the processor, creates metadata comprising a plurality of data elements indicative of information concerning the at least one set of image data obtained by image shooting section;a recording section which records in a recording medium at least one file having a first format in which the metadata is added to the at least one set of image data;a metadata judgment section of processor-executable instructions which, when executed by the processor, judges whether a file having a second format comprising the metadata only is recorded in the recording medium, wherein, when the metadata judgment section judges that the file having the second format is not recorded in the recording medium, the recording section creates the file having the second format from the metadata included in the at least one file having the first format and records the created file in the recording medium;an update judgment section of processor-executable instructions which, when executed by the processor, judges whether one of the metadata included in the at least one file having the first format and the metadata included in the file having the second format is updated;and a metadata synchronizing section of processor-executable instructions which, when executed by the processor, controls the synchronization of the metadata, wherein controlling the synchronization of the metadata includes synchronizing the metadata included in the file having the first format with the metadata included in the file having the second format by replacing the metadata which has not been updated with the updated metadata if the update judgment section judges that one of the metadata included in the at least one file having the first format and the metadata included in the file having the second format is updated, otherwise not synchronizing the metadata.
- 10Broadest claimClaim Score 61, broad(NHIP)An image data recording method comprising:obtaining at least one set of image data by shooting;creating metadata comprising a plurality of data elements indicative of information concerning the at least one set of obtained image data;recording in a recording medium at least one file having a first format in which the metadata is added to the at least one set of image data and a file having a second format comprising the metadata only;judging whether one of the metadata included in the at least one file having the first format and the metadata included in the file having the second format is updated;and controlling the synchronization of the metadata, wherein controlling the synchronization of the metadata includes synchronizing the metadata included in the at least one file having the first format with the metadata included in the file having the second format by replacing the metadata which has not been updated with the updated metadata if one of the metadata included in the at least one file having the first format and the metadata included in the file having the second format is judged to have been updated, otherwise not synchronizing the metadata.
Independent claims3
99 paragraphs in 5 sections, as filed
CROSS-REFERENCE TO RELATED APPLICATIONS
p-0002This application is based upon and claims the benefit of priority from prior Japanese Patent Application No. 2004-220602, filed Jul. 28, 2004, the entire contents of which are incorporated herein by reference.
BACKGROUND OF THE INVENTION
p-00031. Field of the Invention
p-0004The present invention relates to a digital camera and a data recording method which record digital image data.
p-00052. Description of the Related Art
p-0006There have been made various kinds of proposals in relation to a technique which adds information concerning image data as metadata in order to retrieve or manage image data. For example, in a proposal of Jpn. Pat. Appln. KOKAI No. 2002-44592, metadata which is repeatedly used is created in advance as attached information of binary data such as image data, and this created metadata is repeatedly added to a plurality of sets of binary data. Such a technique readily enables generation of binary data having metadata.
BRIEF SUMMARY OF THE INVENTION
p-0007According to a first aspect of the present invention, there is provided a digital camera comprising:
p-0008an image shooting section which obtains at least one set of image data by shooting;
p-0009a metadata creating section which creates metadata comprising a plurality of data elements indicative of information concerning the at least one set of image data obtained by the image shooting section; and
p-0010a recording section which records in a recording medium at least one file having a first format in which the metadata is added to the at least one set of image data and a file having a second format comprising the metadata only.
p-0011According to a second aspect of the present invention, there is provided a digital camera comprising:
p-0012an image shooting section which obtains at least one set of image data by shooting;
p-0013a metadata creating section which creates metadata comprising a plurality of data elements indicative of information concerning the at least one set of image data obtained by image shooting section;
p-0014a recording section which records in a recording medium at least one file having a first format in which the metadata is added to the at least one set of image data; and
p-0015a metadata judgment section which judges whether a file having a second format comprising the metadata only is recorded in the recording medium,
p-0016wherein, when the metadata judgment section judges that the file having the second format is not recorded in the recording medium, the recording section creates the file having the second format from the metadata included in the at least one file having the first format and records the created file in the recording medium.
p-0017According to a third aspect of the present invention, there is provided an image data recording method comprising:
p-0018obtaining at least one set of image data by shooting;
p-0019creating metadata comprising a plurality of data elements indicative of information concerning the at least one set of obtained image data;
p-0020recording in a recording medium at least one file having a first format in which the metadata is added to the at least one set of image data and a file having a second format comprising the metadata only;
p-0021judging whether one of the metadata included in the at least one file having the first format and the metadata included in the file having the second format is updated; and
p-0022synchronizing the metadata included in the at least one file having the first format with the metadata included in the file having the second format by replacing the other metadata with the updated metadata when it is determined that one of the two sets of metadata is updated by the judgment.
p-0023According to a fourth aspect of the present invention, there is provided an image data recording method comprising:
p-0024obtaining at least one set of image data by shooting;
p-0025creating metadata comprising a plurality of data elements indicative of information concerning the at least one set of obtained image data;
p-0026recording in a recording medium at least one file having a first format in which the metadata is added to the at least one set of image data;
p-0027judging whether a file having a second format comprising the metadata only is recorded in the recording medium; and
p-0028creating the file having the second format from the metadata included in the at least one file having the first format and recording the created file in the recording medium when it is judged that the file having the second format is not recorded in the recording medium by the judgment.
p-0029Advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Advantages of the invention may be realized and obtained by means of the instrumentalities and combinations particularly pointed out hereinafter.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING
p-0030The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention, and together with the general description given above and the detailed description of the embodiments given below, serve to explain the principles of the invention.
p-0031<figref idrefs="DRAWINGS">FIG. 1</figref> is a block diagram showing a configuration of a digital camera according to a first embodiment of the present invention;
p-0032<figref idrefs="DRAWINGS">FIGS. 2A to 2C</figref> are views showing a file created at the time of shooting a first image;
p-0033<figref idrefs="DRAWINGS">FIG. 3</figref> is a view showing an image information portion;
p-0034<figref idrefs="DRAWINGS">FIG. 4</figref> is a view showing an XML declarative portion;
p-0035<figref idrefs="DRAWINGS">FIG. 5</figref> is a view showing an XSL file;
p-0036<figref idrefs="DRAWINGS">FIGS. 6A to 6C</figref> are views showing a file at the time of shooting a second image;
p-0037<figref idrefs="DRAWINGS">FIG. 7</figref> is a view showing an image information portion at the time of shooting the second image;
p-0038<figref idrefs="DRAWINGS">FIG. 8</figref> is a flowchart showing metafile judgment processing in a second embodiment according to the present invention;
p-0039<figref idrefs="DRAWINGS">FIG. 9</figref> is a flowchart showing metafile creation processing in the second embodiment according to the present invention;
p-0040<figref idrefs="DRAWINGS">FIG. 10</figref> is a view showing an image information portion concerning raw image data in a third embodiment according to the present invention;
p-0041<figref idrefs="DRAWINGS">FIG. 11</figref> is a view showing an image information portion when raw development data and a comment are changed;
p-0042<figref idrefs="DRAWINGS">FIG. 12</figref> is a view showing an image information portion concerning JPEG image data in the third embodiment according to the present invention;
p-0043<figref idrefs="DRAWINGS">FIG. 13</figref> is a view showing the image information portion when still image edit processing is performed; and
p-0044<figref idrefs="DRAWINGS">FIG. 14</figref> is a flowchart showing metafile update processing in the third embodiment according to the present invention.
DETAILED DESCRIPTION OF THE INVENTION
p-0045Embodiments according to the present invention will now be described hereinafter with reference to the accompanying drawings.
First Embodiment
p-0046A first embodiment according to the present invention will now be described. <figref idrefs="DRAWINGS">FIG. 1</figref> is a block diagram showing a configuration of a digital camera (which will be referred to as a camera hereinafter) according to the first embodiment of the present invention.
p-0047A shooting lens <b>1</b> forms an image of a light beam from a non-illustrated subject on a predetermined image forming surface. An aperture diaphragm <b>2</b> is arranged on an optical axis of the shooting lens <b>1</b>. This aperture diaphragm <b>2</b> adjusts an incident light quantity of a light beam which has entered through the shooting lens <b>1</b>. A CCD <b>3</b> is arranged on the image forming surface of the shooting lens <b>1</b>. This CCD <b>3</b> performs photoelectric conversion of an incident light beam to obtain an image signal. A timing generator (TG) <b>4</b> controls a read timing of an image signal obtained by the CCD <b>3</b>.
p-0048An amplifier <b>5</b> amplifies an image signal read from the CCD <b>3</b> with a predetermined gain. An analog-to-digital conversion circuit <b>6</b> performs digital conversion of an output image signal from the amplifier <b>5</b> to obtain image data. A camera signal processing circuit <b>7</b> carries out various kinds of image processing such as white balance (WB) processing or gradation conversion processing based on output image data from the analog-to-digital conversion circuit <b>6</b>. An AE, AF and AWB circuit <b>8</b> performs automatic exposure (AE) detection, automatic focus (AF) detection and automatic white balance (AWB) detection based on output image data from the analog-to-digital conversion circuit <b>6</b>.
p-0049A CPU <b>9</b> is a control section which entirely controls this camera, and carries out processing such as an AE calculation, an AF calculation, a white balance gain calculation and others based on a result obtained by the AE, AF and AWB circuit <b>8</b>. Further, the CPU <b>9</b> also performs driving control of the aperture diaphragm <b>2</b> and driving control of the TG <b>4</b> in accordance with a result of the AE calculation, and focus control of the shooting lens <b>1</b> in accordance with a result of the AF calculation.
p-0050A bus <b>10</b> is a data transfer path through which output image data from the analog-to-digital conversion circuit <b>6</b> or image data subjected to image processing in the camera signal processing circuit <b>7</b> as well as various kinds of data are transferred. To this bus <b>10</b> are connected the camera signal processing circuit <b>7</b>, the CPU <b>9</b>, a JPEG processing circuit <b>11</b>, a memory controller <b>12</b>, a display circuit <b>14</b>, a memory card interface <b>16</b> and a PC interface <b>18</b>.
p-0051The JPEG processing circuit <b>11</b> is a circuit which performs JPEG compression processing of image data processed in the camera signal processing circuit <b>7</b> and expansion processing of image data subjected to JPEG compression. The memory controller <b>12</b> is a circuit which controls storage of data in a DRAM <b>13</b>. The display circuit <b>14</b> is a circuit which performs control when displaying a shot image in an LCD <b>15</b>. The memory card interface <b>16</b> is a circuit which performs recording control when recording an image file or the like in a recording medium (which will be referred to as a memory card hereinafter) <b>17</b> such as a memory card detachably constituted with respect to this camera. The PC interface <b>18</b> is a circuit which mediates communication between this camera and a PC <b>19</b> connected with this camera.
p-0052A flash device <b>20</b> illuminates a subject when, e.g., the illuminance of the subject is low, and comprises a light source and a light source drive circuit.
p-0053An input key <b>21</b> is an operation key group including a power supply button which turns on a power supply of the camera, a release button which starts the shooting and others.
p-0054File creation processing at the time of shooting an image by the camera having such a configuration as shown in <figref idrefs="DRAWINGS">FIG. 1</figref> will now be described.
p-0055A description will be first given as to file creation processing at the time of shooting (which will be referred to as the shooting of a first image hereinafter) when an image file is not recorded in the memory card <b>17</b>. When the shooting of a first image is performed by an image shooting section comprising the shooting lens <b>1</b>, the CCD <b>3</b>, the analog-to-digital conversion circuit <b>6</b>, the camera signal processing circuit <b>7</b> and others, such an image file <b>101</b> as shown in <figref idrefs="DRAWINGS">FIG. 2A</figref> is created, a metafile <b>102</b> and an XSL file <b>103</b> such as shown in <figref idrefs="DRAWINGS">FIGS. 2B and 2C</figref> are also created, and these three files are recorded in the memory card <b>17</b>.
p-0056The image file (a file name: P1000001.JPG) <b>101</b> as a file having a first format shown in <figref idrefs="DRAWINGS">FIG. 2A</figref> comprises an image data portion (which is shown as image data <b>1</b> in the drawing) <b>101</b><i>a </i>in which image data obtained by the shooting of the first image is recorded and an image information portion (which is shown as image information <b>1</b> in the drawing) <b>101</b><i>b </i>in which image information concerning image data obtained by the shooting of the first image is recorded.
p-0057Image data recorded in the image data portion <b>101</b><i>a </i>is image data (JPEG image data) subjected to compression processing in the JPEG processing circuit <b>11</b> or output image data (raw image data) from the analog-to-digital conversion circuit <b>6</b>.
p-0058On the other hand, image information recorded in the image information portion <b>101</b><i>b </i>is information concerning image data obtained in the shooting. In the first embodiment, shooting information indicative of shooting conditions or the like in the shooting and file information concerning an image file created in the shooting are written as image information. In this example, as data elements included in the shooting information, there are, e.g., a shutter speed, an aperture value in the shooting and others. Furthermore, as data elements included in the file information, there are, e.g., a file name, a file size and others.
p-0059Moreover, the image information portion <b>101</b><i>b </i>is created as metadata using an extensible markup language (XML) format. The XML is one of markup languages in which information is written by using a tag. In this XML, information can be written as text data. Additionally, as different from a hyper text markup language (HTML), the XML enables a user to create a tag without restraint.
p-0060<figref idrefs="DRAWINGS">FIG. 3</figref> is a view showing an example of the image information portion <b>10</b><i>b</i>. It is to be noted that <figref idrefs="DRAWINGS">FIG. 3</figref> shows image information when the image data is JPEG image data. As shown in <figref idrefs="DRAWINGS">FIG. 3</figref>, the image information portion <b>101</b><i>b </i>has a hierarchical configuration in which a shooting information tag which is used to write shooting information and a file information tag which is used to write file information are provided in a root tag called an image information tag.
p-0061In the image file created as shown in <figref idrefs="DRAWINGS">FIG. 2A</figref>, the image information written in the image information portion <b>101</b><i>b </i>cannot be extracted unless a dedicated device or application software is used. Therefore, there is almost no possibility of loss of the image information written in the image information portion <b>101</b><i>b </i>from the image file.
p-0062Further, the metafile (a file name: PicInfo.xml) <b>102</b> as a file having a second format shown in <figref idrefs="DRAWINGS">FIG. 2B</figref> comprises an XML declarative portion <b>102</b><i>a </i>and the image information portion <b>101</b><i>b. </i>
p-0063The XML declarative portion <b>102</b><i>a </i>is a portion indicating a version of the XML, a character encoding method or the like, and written as shown in <figref idrefs="DRAWINGS">FIG. 4</figref>. In this example, as the XML declarative portion <b>102</b><i>a </i>shown in <figref idrefs="DRAWINGS">FIG. 4</figref>, one standardized by the World Wide Web Consortium (W3C) can be used as it is. Here, the detailed description thereof will be eliminated.
p-0064Furthermore, in the XML declarative portion <b>102</b><i>a </i>shown in <figref idrefs="DRAWINGS">FIG. 4</figref>, an XSL file (a file name: PicInfo.xsl) <b>103</b> is specified in a style sheet. By specifying the XSL file <b>103</b> in the style sheet, the image information written as the XML data can be converted into HTML data, and a content written in the metafile (PicInfo.xml) <b>102</b> can be thereby displayed in a Web browser.
p-0065The XSL file (PicInfo.xsl) <b>103</b> as a file having a third format shown in <figref idrefs="DRAWINGS">FIG. 2C</figref> is a file written in a format called XSLT shown in <figref idrefs="DRAWINGS">FIG. 5</figref>. This XSLT is also standardized in W3C. Here, the detailed explanation will be eliminated.
p-0066File creation processing at the time of shooting a second image will now be described. The same file creation processing as that of the second image shooting is performed at the time of shooting a third image and subsequent images.
p-0067At the time of shooting the second image, an image file (a file name: P1000002.JPG) <b>201</b> comprising such an image data portion (shown as image data <b>2</b> in the drawing) <b>201</b><i>a </i>in which image data acquired at the time of shooting the second image is recorded as shown in <figref idrefs="DRAWINGS">FIG. 6A</figref> and an image information portion (shown as image information <b>2</b> in the drawing) <b>201</b><i>b </i>in which image information concerning the image data acquired at the time of shooting the second image is recorded is newly created. Furthermore, as shown in <figref idrefs="DRAWINGS">FIG. 6B</figref>, the image information portion <b>201</b><i>b </i>concerning the second image data is added to the metafile (PicInfo.xml) <b>102</b>. <figref idrefs="DRAWINGS">FIG. 7</figref> shows the metafile (PicInfo.xml) <b>102</b> to which the image information <b>201</b><i>b </i>concerning the second image is added. In this example, the XSL file (PicInfo.xsl) <b>103</b> is not changed (see <figref idrefs="DRAWINGS">FIG. 6C</figref>).
p-0068As described above, according to the first embodiment, the image information written as the XML data in the metafile can be readily read by using a universal technique such as a Web browser. Moreover, since the image information is also recorded in the image file, the relevance between the image information and the image data is not lost.
Second Embodiment
p-0069A second embodiment according to the present invention will now be described. The second embodiment according to the present invention is an example of newly creating a metafile (PicInfo.xml) when, e.g., a user accidentally deletes a metafile (PicInfo.xml). It is to be noted that a hardware configuration is the same as that described in conjunction with <figref idrefs="DRAWINGS">FIG. 1</figref>. However, the CPU <b>9</b> in the second embodiment has a function as a metadata judgment section which judges whether a metafile (PicInfo.xml) is recorded in the memory card <b>17</b>.
p-0070<figref idrefs="DRAWINGS">FIG. 8</figref> is a flowchart showing metafile judgment processing which is performed immediately after the power supply of the camera is turned on. This processing of <figref idrefs="DRAWINGS">FIG. 8</figref> is executed in the CPU <b>9</b>.
p-0071After turning on the power supply, the CPU <b>9</b> checks a file in the memory card <b>17</b> (step S<b>11</b>). As a result of the file check at step S<b>11</b>, the CPU <b>9</b> judges whether a metafile (PicInfo.xml) exists in the memory card <b>17</b> (step S<b>12</b>).
p-0072If it is determined that the metafile (PicInfo.xml) exists in the memory card <b>17</b> as a result of the judgment at step S<b>12</b>, step S<b>12</b> jumps to step S<b>13</b> where the CPU <b>9</b> executes regular camera activation processing (step S<b>13</b>). On the other hand, if it is determined that the metafile (PicInfo.xml) does not exist in the memory card <b>17</b> as a result of the judgment at step S<b>12</b>, step S<b>12</b> jumps to step S<b>14</b> where the CPU <b>9</b> executes metafile (PicInfo.xml) creation processing (step S<b>14</b>). Thereafter, the processing advances to step S<b>13</b>.
p-0073<figref idrefs="DRAWINGS">FIG. 9</figref> is a flowchart showing the metafile (PicInfo.xml) creation processing at step S<b>14</b> in <figref idrefs="DRAWINGS">FIG. 8</figref>.
p-0074In <figref idrefs="DRAWINGS">FIG. 9</figref>, the CPU <b>9</b> creates an XML declarative portion of the metafile (PicInfo.xml) and an XSL file (PicInfo.xsl) (step S<b>21</b>).
p-0075Then, the CPU <b>9</b> judges whether an unprocessed image file exists (step S<b>22</b>). Here, the “unprocessed image file” means an image file from which image information is not extracted and in which image information is not added to the image information portion of the metafile (PicInfo.xml). If it is determined that there is an unprocessed image file at step S<b>22</b>, step S<b>22</b> jumps to step S<b>23</b>, and the CPU <b>9</b> extracts image information in the image file (the step S<b>23</b>) and adds the extracted image information to the image information portion of the metafile (PicInfo.xml) (step <b>24</b>). Then, the processing returns to step S<b>22</b>.
p-0076On the other hand, if it is determined that there is no unprocessed image file as a result of the judgment at step S<b>22</b>, the processing of <figref idrefs="DRAWINGS">FIG. 9</figref> is terminated.
p-0077As described above, according to the second embodiment, in cases where a metafile does not exist when the power supply of the camera is turned on, a metafile is created from image information recorded in an image file. As a result, even if a metafile is accidentally deleted, the metafile can be restored.
p-0078It is to be noted that the processing shown in <figref idrefs="DRAWINGS">FIGS. 8 and 9</figref> is executed immediately after the power supply is turned on in the second embodiment, but the present invention is not restricted thereto. For example, this processing may be executed at each predetermined time after the power supply of the camera is turned on.
Third Embodiment
p-0079A third embodiment according to the present invention will now be described. Since data elements constituting a metafile (PicInfo.xml) are written as text data, a content of the data elements can be readily changed by using, e.g., a text editor. On the other hand, image information recorded in an image file is automatically set in accordance with shooting conditions at the time of image shooting or image processing conditions at the time of image processing. In the third embodiment according to the present invention, image information recorded in an image information portion of an image file is synchronized with image information recorded in an image information portion of a metafile so that the image information can be easily changed by universal means.
p-0080Here, it is not preferable that information concerning shooting conditions, e.g., a shooting date and time, a shutter speed in the shooting, an aperture value in the shooting and others is updated since it is information determined in the shooting. Further, it is also desirable that a file name (this file name is a file name automatically given by the camera at the time of image shooting) is not updated in view of retrieval of files and others consideration.
p-0081Accordingly, in the third embodiment, even if a data element included in image information of a metafile (PicInfo.xml) is updated, a data element of an image file is prevented from being updated when the updated data element is a predetermined data element. This predetermined data element is information which is mainly determined at the time of image shooting, and includes information concerning shooting conditions, e.g., a shutter speed at the time of shooting, an aperture value at the time of shooting, sensitivity information at the time of shooting, a shooting mode at the time of shooting, a flash mode at the time of shooting or an exposure mode at the time of shooting, file names given to an image file and a metafile at the time of shooting and others events.
p-0082The hardware configuration in the camera according to the third embodiment is the same as that described in conjunction with <figref idrefs="DRAWINGS">FIG. 1</figref>. However, the CPU <b>9</b> in the third embodiment includes a function as an update judgment section which judges whether a data element of one of an image file and a metafile is updated and a function as a metadata synchronizing section which achieves synchronization between a data element of an image file and a data element of a metafile.
p-0083<figref idrefs="DRAWINGS">FIG. 10</figref> is a view showing an image information portion which is simultaneously created when raw image data is acquired by the camera according to the third embodiment. In the image information portion depicted in <figref idrefs="DRAWINGS">FIG. 10</figref>, a raw development information tag and a comment tag are added in addition to the tag depicted in <figref idrefs="DRAWINGS">FIG. 3</figref>.
p-0084The raw development information tag is a tag in which information to which reference is made by a device having an image processing function, e.g., a PC can be written when developing raw image data by the device having an image processing function, e.g., PC. The comment tag is a tag in which can be written a comment with respect to an image file.
p-0085For example, in cases where the sharpness (an edge emphasizing quantity) when developing raw image data is changed from “strong” to “weak” or where a comment “athletic meeting” is added to an image file, a user changes image information written in the image information portion of a metafile (PicInfo.xml) by using a text editor or the like (see <figref idrefs="DRAWINGS">FIG. 11</figref>). In the third embodiment, when image information of a metafile (PicInfo.xml) is updated as shown in <figref idrefs="DRAWINGS">FIG. 11</figref>, image information of an image file is also updated.
p-0086Further, <figref idrefs="DRAWINGS">FIG. 12</figref> is a view showing an image information portion which is simultaneously created when JPEG image data is acquired by the camera according to the third embodiment. In the image information portion depicted in <figref idrefs="DRAWINGS">FIG. 12</figref>, an editing tag is added besides the tags depicted in <figref idrefs="DRAWINGS">FIG. 3</figref>.
p-0087The editing tag is a tag in which an editing content is written when still image editing such as realization of a monochromatic image or rotation of an image is carried out.
p-0088For example, when a user performs monochromatic image realization processing with respect to image data, information called “monochrome” is newly written in image information written in the image information portion of an image file (see <figref idrefs="DRAWINGS">FIG. 13</figref>). Image information written in a metafile is also updated in accordance with this processing.
p-0089Such file update processing will now be described in detail with reference to <figref idrefs="DRAWINGS">FIG. 14</figref>. When one of an image file and a metafile is updated, the CPU <b>9</b> acquires the updated file (step S<b>31</b>). Then, the CPU <b>9</b> judges whether the updated file is an image file (step S<b>32</b>).
p-0090If it is determined that the updated file is not the image file, i.e., the updated file is the metafile (PicInfo.xml) as a result of the judgment at step S<b>32</b>, step S<b>32</b> jumps to step S<b>33</b>, the CPU <b>9</b> acquires image information concerning the first shot written in the metafile (PicInfo.xml) (step S<b>33</b>). Then, an image file which coincides with a file name written in a file name tag of the acquired image information is opened (step S<b>34</b>). Further, each data element of image information in this opened image file is compared with each data element of image information in the metafile (PicInfo.xml). Then, a data element which differs between the image information in the image file and the image information in the metafile (PicInfo.xml) is detected (step S<b>35</b>). Subsequently, the CPU <b>9</b> judges whether the data element which differs between the image file and the metafile (PicInfo.xml) is a replaceable data element as a result of the comparison at step S<b>35</b> (step S<b>36</b>).
p-0091If it is determined that the data element which differs between the image file and the metafile (PicInfo.xml) is a replaceable data element in the judgment at step S<b>36</b>, step S<b>36</b> jumps to step S<b>37</b>, the CPU <b>9</b> replaces the image information written in the image information portion of the image file with the image information written in the image information portion of the metafile (PicInfo.xml) (step S<b>37</b>), and then the processing advances to step S<b>38</b>. It is needless to say that only the data element which differs between the image file and the metafile (PicInfo.xml) can be replaced at this time.
p-0092On the other hand, if it is determined that the data element which differs between the image file and the metafile (PicInfo.xml) is an irreplaceable data element in the judgment at step S<b>36</b>, the processing advances to step S<b>38</b> without performing replacement of the data element. It is to be noted that replacing the image information of the metafile (PicInfo.xml) with the image information of the image file is more preferable. By doing so, the image information of the image file and the image information of the metafile are always equal to each other.
p-0093Then, the CPU <b>9</b> closes the image file (step S<b>38</b>). Further, the CPU <b>9</b> judges whether the acquired image information is the last image information written in the metafile (PicInfo.xml) (step S<b>39</b>). If it is determined that the acquired image information is not the last image information in the judgment at step S<b>39</b>, step S<b>39</b> jumps to step S<b>40</b>, the CPU <b>9</b> acquires the next image information (step S<b>40</b>), and then the processing returns to step S<b>34</b>. On the other hand, if it is determined that the acquired image information is the last image information in the judgment at step S<b>39</b>, the processing shown in <figref idrefs="DRAWINGS">FIG. 14</figref> is terminated.
p-0094Furthermore, if it is determined that the updated file is an image file in the judgment at step S<b>32</b>, step S<b>32</b> jumps to step S<b>41</b>, and the CPU <b>9</b> opens the metafile (PicInfo.xml) and retrieves a file name (step S<b>41</b>). Then, image information written in the image information portion under the retrieved file name is replaced with image information written in the image information portion of a corresponding image file (step S<b>42</b>). Thereafter, the metafile (PicInfo.xml) is closed (step S<b>43</b>), and the processing shown in <figref idrefs="DRAWINGS">FIG. 14</figref> is terminated.
p-0095As described above, in the third embodiment, image information of an image file can be readily updated by achieving synchronization of image information between an image file and a metafile. As a result, by updating raw development information or the like written in, e.g., a metafile by using, e.g., a text editor, the updated content can be also easily reflected on an image file. Consequently, an effect of improving the image quality when, e.g., subjecting raw image data to image processing can be expected.
p-0096Moreover, when a data element such as shooting conditions in shooting which should not be updated is updated in a metafile, a data element of an image file is prevented from being replaced, thereby updating appropriate image information only.
p-0097Additional advantages and modifications will readily occur to those skilled in the art. Therefore, the invention in its broader aspects is not limited to the specific details and representative embodiments shown and described herein. Accordingly, various modifications may be made without departing from the spirit or scope of the general invention concept as defined by the appended claims and their equivalents.
Contents5
12 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12
Every citation, both waysCites: the store holds 9 of 10
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2006119714A1 | Cited by | United States of America | Pre-grant |
| CN1373602A | Cites | China | Applicant |
| JP2002044592A | Cites | Japan | Applicant |
| US2002116575A1 | Cites | United States of America | Search report |
| US2002118285A1 | Cites | United States of America | Applicant |
| US2003110297A1 | Cites | United States of America | Search report |
| US2004015535A1 | Cites | United States of America | Search report |
| US2004114042A1 | Cites | United States of America | Search report |
| US6523046B2 | Cites | United States of America | Search report |
| US7301658B2 | Cites | United States of America | Search report |
| Chinese Office Action for Chinese Patent Application No. 200510087325.9, mailed on Jun. 13, 2008 (3 pgs.) (with English Translation (4 pgs.)). | Non-patent | – | Applicant |
6 members in 3 offices
Priority claims4
| Document | Office | Kind | Date |
|---|---|---|---|
| 2004220602 | Japan | A | |
| 2004220602 | Japan | A | |
| 2004220602 | – | – | – |
| JP20040220602 | – | – | – |
Members6
| Document | Office | Kind | |
|---|---|---|---|
| CN1728801A | China | A | |
| US2006023082A1 | United States of America | A1 | |
| JP2006042052A | Japan | A | |
| US7499952B2This record | United States of America | B2 | |
| CN100477767C | China | C | |
| JP4262646B2 | Japan | B2 |
46 transactions on the USPTO file
Allowed after 1 non-final rejection and 1 final rejection.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Correspondence Address ChangeC.ADB | C.ADB | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Workflow - Informational Disclosure Statement - FinishFIDS | FIDS | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Response to Reasons for AllowanceREAS | REAS | |
| Mail Examiner's AmendmentMEX.A | MEX.A | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Examiner Interview Summary Record (PTOL - 413)EXIN | EXIN | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Response after Final ActionA.NE | A.NE | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Request for Foreign Priority (Priority Papers May Be Included)RQPR | RQPR | |
| Cleared by L&R (LARS)L128 | L128 | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Referred to Level 2 (LARS) by OIPE CSRL198 | L198 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Initial Exam Team nnIEXX | IEXX |
10 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS |
Numbers
- Publication, DOCDB
- 7499952
- Publication, EPODOC
- US7499952
- Application
- 11176824
- Application, DOCDB
- 17682405
- Application, EPODOC
- US20050176824
Titles
- English
- Digital camera and image data recording method
Patent term adjustment
- A delay
- +411 daysthe office missed an examination deadline
- Applicant delay
- −2 days
- Net adjustment
- 409 days
Classification
- CPC, 3
- H04N5/772
- H04N5/907
- H04N5/9206
- IPC, 1
- G06F17 30
- USPC, 4
- 001001000
- 707999010
- 707999104
- 707999201