Media content validation using geometrically encoded metadata

According to one implementation, a system for validating media content includes a computing platform having a hardware processor and a system memory storing a media content validation software code. The hardware processor is configured to execute the media content validation software code to search the media content for a geometrically encoded metadata structure. When the geometrically encoded metadata structure is detected, the hardware processor is further configured to execute the media content validation software code to identify an original three-dimensional (3D) geometry of the detected geometrically encoded metadata structure, to extract metadata from the detected geometrically encoded metadata structure, decode the metadata extracted from the detected geometrically encoded metadata structure based on the identified original 3D geometry, and obtain a validation status of the media content based on the decoded metadata.

BACKGROUND

Media content including three-dimensional (3D) data structures, such as 3D models, for example, tend to lose metadata information when utilized in model manipulation software applications. This is because conventional media file transfer techniques rely on format-specific metadata that does not survive conversion to a different format. For example, a 3D model formatted for AUTOCAD® will typically lose all metadata information when converted to virtual reality (VR), 3D printing, or animation formats.

The metadata lost during file conversion may identify the author of the media content, its version, its owners and/or licensees, its storage and transfer history, and other information determining its chain-of-custody, validity, and eligibility for use in movies, television, or Internet based distribution. Without that metadata information, unauthorized or lower quality content may inadvertently be used in place of original media content or authorized copies of that original content approved for use. Moreover, media content approved for distribution through some channels but not others may be improperly distributed in violation of contractual agreement, thereby subjecting the content distributor to legal jeopardy.

SUMMARY

There are provided systems and methods for validating media content using geometrically encoded metadata, substantially as shown in and/or described in connection with at least one of the figures, and as set forth more completely in the claims.

DETAILED DESCRIPTION

The present application discloses automated systems and methods for validating media content that overcome the drawbacks and deficiencies in the conventional art. As stated above, media content including three-dimensional (3D) data structures, such as 3D models, for example, tend to lose metadata information when utilized in a variety of model manipulation software applications. As further stated above, this is because conventional media file transfer techniques rely on format-specific metadata that does not survive conversion to a different format. For example, a 3D model formatted for AUTOCAD® will typically lose all metadata information when converted to virtual reality (VR), 3D printing, or animation formats.

The metadata lost during file conversion may identify the author of the media content, its version, its owners and/or licensees, its storage and transfer history, and other information determining its chain-of-custody, validity, and eligibility for use in movies, television, or Internet based distribution. The loss of such metadata may lead to one or more of a number of undesirable results. For example, unauthorized or lower quality content may inadvertently be used in place of original media content or authorized copies of that original content approved for use. Moreover, media content approved for distribution through some channels but not others may be improperly distributed in violation of contractual agreement, thereby subjecting the content distributor to legal jeopardy.

By contrast, in one solution disclosed by the present application, metadata is carried by a geometrically encoded metadata structure included in media content. That geometrically encoded metadata structure may be deformed or otherwise manipulated concurrently with deformation or manipulation of the media content during file conversion. According to the present inventive concepts, when such a geometrically encoded metadata structure is detected in media content, the original 3D geometry of the geometrically encoded metadata structure is identified, metadata is extracted from it, and that metadata is decoded based on the original 3D geometry of the geometrically encoded metadata structure. The validation status of the media content may then advantageously be obtained based on the decoded metadata.

It is noted that, as used in the present application, the terms “automation,” “automated”, and “automating” refer to systems and processes that do not require human intervention. Although, in some implementations, a human editor or annotator may review media content metadata extracted and decoded by the automated media content validation processes described herein, that human involvement is optional. Thus, validation of media content by the systems and methods described in the present application may be performed under the control of the hardware processing components executing them.

FIG. 1shows a diagram of an exemplary system for validating media content, according to one implementation. System100includes computing platform102having hardware processor104, and system memory106implemented as a non-transitory storage device. According to the exemplary implementation shown inFIG. 1, system memory106stores media content validation software code110and optional media content validation database122.

As shown inFIG. 1, system100is utilized within a use environment including communication network130, user120utilizing user system134having display136, media content124, and media content validation source132providing validation status138of media content124. Also shown inFIG. 1are network communication links131and decoded metadata128that is based on metadata extracted from a geometrically encoded metadata structure included in media content124(geometrically encoded metadata structure not shown inFIG. 1).

Media content124may include any of a wide variety of content types, such as digital images, audio content, audio-visual content, an electronic book or document (e-book or e-document), or a data structure, to name a few examples. In some implementations, media content124may include a 3D data structure, such as a 3D model. For example, media content124may include a 3D model of an animated character, or a 3D representation of a living person or historical figure. Alternatively, media content124may be a 3D model of an object such as a costume or prop used in a movie or television (TV) programming content. As yet another alternative, media content124may include a 3D model of an edifice such as a building or monument, or a 3D model of a vehicle, such as a wheeled vehicle, a track driven vehicle, a watercraft, an aircraft, or a spacecraft.

It is noted that, although the present application refers to media content validation software code110and optional media content validation database122as being stored in system memory106for conceptual clarity, more generally, system memory106may take the form of any computer-readable non-transitory storage medium. The expression “computer-readable non-transitory storage medium,” as used in the present application, refers to any medium, excluding a carrier wave or other transitory signal that provides instructions to a hardware processor of a computing platform, such as hardware processor104of computing platform102. Thus, a computer-readable non-transitory medium may correspond to various types of media, such as volatile media and non-volatile media, for example. Volatile media may include dynamic memory, such as dynamic random access memory (dynamic RAM), while non-volatile memory may include optical, magnetic, or electrostatic storage devices. Common forms of computer-readable non-transitory media include, for example, optical discs, RAM, programmable read-only memory (PROM), erasable PROM (EPROM), and FLASH memory.

It is further noted that althoughFIG. 1depicts media content validation software code110and optional media content validation database122as being mutually co-located in system memory106, that representation is also merely provided as an aid to conceptual clarity. More generally, system100may include one or more computing platforms, such as computer servers for example, which may be co-located, or may form an interactively linked but distributed system, such as a cloud based system, for instance.

For instance, computing platform102may correspond to one or more web servers, accessible over a packet-switched network such as the Internet, for example. Alternatively, computing platform102may correspond to one or more computer servers supporting a wide area network (WAN), a local area network (LAN), or included in another type of private or limited distribution network. In other words, hardware processor104and system memory106may correspond to distributed processor and memory resources within system100. Moreover, media content validation software code110and optional media content validation database122may be stored remotely from one another within the distributed memory resources of system100.

It is also noted that although user system134is shown as a desktop computer inFIG. 1, that representation is provided merely as an example as well. More generally, user system134may be any suitable mobile or stationary computing device or system that implements data processing capabilities sufficient to implement the functionality ascribed to user system134herein. For example, in other implementations, user system134may take the form of a laptop computer, tablet computer, or smartphone, for example. Furthermore, display136of user system134may be implemented as a liquid crystal display (LCD), a light-emitting diode (LED) display, an organic light-emitting diode (OLED) display, or another suitable display screen that performs a physical transformation of signals to light.

FIG. 2shows a more detailed exemplary diagram of media content validation software code210suitable for use by system100, inFIG. 1, according to one implementation. As shown inFIG. 2, media content validation software code210includes metadata structure detection module212, geometry analysis and restoration module214, metadata extraction module216, metadata decoding module218, and validation module248. In addition,FIG. 2shows media content224and validation status238of media content224received by media content validation software code210, and decoded metadata228provided as an output by media content validation software code210. Also shown inFIG. 2are geometrically encoded metadata structure240included in media content224, original 3D geometry242of geometrically encoded metadata structure240, and metadata244extracted from geometrically encoded metadata structure240.

Media content validation software code210corresponds in general to media content validation software code110, inFIG. 1, and those corresponding features may share the any of the characteristics attributed to either corresponding feature by the present disclosure. That is to say, like media content validation software code210, media content validation software code110may include features corresponding respectively to metadata structure detection module212, geometry analysis and restoration module214, metadata extraction module216, metadata decoding module218, and validation module248.

In addition, media content224, decoded metadata228, and validation status238of media content224, inFIG. 2, correspond respectively in general to media content124, decoded metadata128, and validation status138of media content124, inFIG. 1. That is to say, media content224, decoded metadata228, and validation status238of media content224may share any of the characteristics attributed to respective media content124, decoded metadata128, and validation status138of media content124by the present disclosure, and vice versa.

FIG. 3shows an exemplary diagram of geometrically encoded metadata structure340for use in validating media content124/224, according to one implementation. As shown inFIG. 3, exemplary geometrically encoded metadata structure340is a 3D structure having original 3D geometry342including unit marker 1 (hereinafter “UM1”), unit marker 2 (hereinafter “UM2”) perpendicular to UM1, and unit marker 3 (hereinafter “UM3”) perpendicular to UM2 and co-linear to UM1. It is noted that the co-linearity of UM1 and UM3 appears distorted inFIG. 3due to rendering of 3D geometrically encoded metadata structure340on the 2D drawing ofFIG. 3. It is further noted that UM1, UM2, and UM3 define endcap370aof geometrically encoded metadata structure340.

As shown inFIG. 3, edge371joins UM1 and UM2, edge372joins UM2 and UM3, and edge373, which is represented by a dashed line because edge373is not visible from the perspective shown inFIG. 3, joins UM3 and UM1.FIG. 3also points to endcap370b, which, like edge373, is not visible from the perspective shown inFIG. 3. However, it is noted that endcap370bis defined by vertices or points (hereinafter “points”)356a,356b, and356c.

Geometrically encoded metadata structure340having original geometry342corresponds in general to geometrically encoded metadata structure240having original 3D geometry242, inFIG. 2, and those corresponding features may share any of the characteristics attributed to either corresponding feature by the present disclosure. That is to say, like geometrically encoded metadata structure340, geometrically encoded metadata structure240may include features corresponding respectively to UM1, UM2, and UM3, endcaps370aand370b, points351a-356aand351b-356b, checksums362-366, and checksum361of checksums362-366.

Geometrically encoded metadata structure240/340has a manifold continuous outer surface and encodes a right-angle+normal rule that allows media content validation software code110/210to detect geometrically encoded metadata structure240/340and restore its original 3D geometry342if it has been deformed or otherwise modified by animation processes and/or file conversion. That is to say, if geometrically encoded metadata structure240/340has been changed geometrically, i.e., deformed, that deformation can be detected and geometrically encoded metadata structure240/340can be restored to original 3D geometry242/342.

Geometrically encoded metadata structure240/340is small enough to be contained within the surface bounds of the 3D model or other 3D data structure included in media content124/224while advantageously having no effect on the final usage of media content124/224. That final usage of media content124/224may include scene rendering, as-built Building Information Modeling (BIM) planning, engineering processes including computer numerical control (CNC) milling, or 3D printing, for example.

One example of encoding of geometrically encoded metadata structure240/340will now be discussed with reference toFIG. 4, which shows American Standard Code for Information Interchange (ASCII) table400used as an exemplary reference table for encoding and decoding geometrically encoded metadata structure240/340. Encoding of geometrically encoded metadata structure240/340may include determining normalized numerical values corresponding to each of the characters assigned to points351a-356aand also assigned to points352a-356bfor redundancy, i.e., the respective letters M, A, S, C, O, and T based on ASCII table400. However, it is emphasized that use of ASCII table400is merely exemplary, and one of ordinary skill in the art will readily recognize that other analogous encoding techniques may be used.

Referring to ASCII table400, inFIG. 4, a normalized numerical value for the letter “M” at point351ainFIG. 3may be obtained by using the inverse of the number of entries in ASCII table400, i.e., 1/256, as a multiplier applied to the ASCII value assigned to the letter “M.” Thus, the encoded numerical value corresponding to the letter “M” at point351ais UVM*77= 1/256*77=0.301, where UVM is a Unit Value Multiplier. The numerical value 0.301 may then be used to provide the dimension for the quadrilateral defined by points351a,351b,352a, and352bthat geometrically encodes the letter “M” at points351aand351b.

By analogy, a normalized numerical value for the letter “A” at points352aand352bmay be obtained by using 1/256 as a UVM applied to the ASCII value assigned to the letter “A.” Thus, the encoded numerical value corresponding to the letter “A” at point352ais UVM*65= 1/256*65=0.254. The numerical value 0.254 may be used to provide the dimension for the quadrilateral defined by points352a,352b,353a, and353bthat geometrically encodes the letter “A” at points352aand352b, and so forth.

It is noted that in some implementations, it may convenient to define the origin of the 3D space occupied by geometrically encoded metadata structure240/340to correspond with UM2 of original 3D geometry342. With respect to checksums362-366, and checksum361of checksums362-366, it is noted that checksum361of checksums362-366at the location (UM3, 1, 0) in original 3D geometry242/342is held for processing until each of checksums362-366is independently computed. The checksum361of checksums362-366allows one more level of validation, as this value is correct only if it matches the independently computed checksums362-366of all of the metadata characters.

Checksum362at location (UM3, 2, 0) in original 3D geometry242/342is computed using any one of numerous suitable algorithms, for example, a decimal sum of the numbers assigned to the characters at points351aand352aby ASCII table400may be used, for example (77+65)*UVM (or another specified value). By analogy, checksum363may be (77+65+68)*UVM, checksum364may be (77+65+68+67)*UVM, checksum365may be (77+65+68+67+65)*UVM, and checksum367may be (77+65+68+67+65+84)*UVM.

In one implementation, metadata244is extracted from geometrically encoded metadata structure240/340and is decoded based on original 3D geometry242/342to produce decoded metadata128/228for use in obtaining validation status138/238of media content124/224. For example, decoded metadata128/228may include a Uniform Resource Identifier (URI), such as a Uniform Resource Locator (URL), for use in obtaining validation status138/238of media content124/224from media content validation source132.

Media content validation source132may provide validation status138/238in the form of authorship, revision history, descriptive information, ownership, licensing history, and distribution rights, for example. Thus, validation status138/238of media content124/224, when obtained based on metadata extracted from geometrically encoded metadata structure240/340and decoded, may be used to confirm that media content138/238is suitable for its intended use. For example, where media content124/224is intended for distribution over the Internet, validation status138/238can be used to confirm that Internet distribution rights for media content are in order. As another example,

Moreover, in some implementations, validation status138/238may include a link to other database elements such as the original version of media content124/224(for such purposes as reverting changes), or to variations of media content124/224suitable for specific use cases. For example, validation status138/238for media content124/224including an architectural model used for Building Information Modeling may include a link to another version of the model tailored to 3D printing or VR applications. In such implementations, validation status138/238may be used to confirm that the version of media content124/224carrying geometrically encoded metadata structure240/340is in a format appropriate to its intended application. Alternatively, or in addition, in those implementations, validation status138/238may be used to obtain an original version of media content124/224, a more current version of that media content, or a version of media content124/224formatted for a specific application.

The functionality of system100including media content validation software code110/210will be further described by reference toFIG. 5in combination withFIGS. 1, 2, 3, and 4.FIG. 5shows flowchart580presenting an exemplary method for use by a system for validating media content, according to one implementation. With respect to the method outlined inFIG. 5, it is noted that certain details and features have been left out of flowchart580in order not to obscure the discussion of the inventive features in the present application.

Referring now toFIG. 5in combination withFIGS. 1, 2, 3, and 4, flowchart580begins with receiving media content124/224(action581). For example, media content124/224may be received by system100from user120, via user system134, communication network130, and network communication links131. More specifically, media content124/224may be received by media content validation software code110/210, executed by hardware processor104.

As noted above, media content124/224may include any of a wide variety of content types, such as digital images, audio content, audio-visual content, e-books or e-documents, or a data structure, to name a few examples. As also noted above, in some implementations, media content124/224may include a 3D data structure, such as a 3D model of an animated character, a 3D representation of a living person or historical figure, a 3D model of an object such as a costume or prop used in a movie or TV program, a 3D model of an edifice such as a building or monument, or a 3D model of a vehicle.

Flowchart580continues with searching media content124/224for geometrically encoded metadata structure240/340(action582). In some implementations, action582may include searching substantially all of media content124/224for the presence of geometrically encoded metadata structure240/340. However, in some implementations, or in some specific use cases, the searching performed in action582may be restricted to a predetermined portion of media content124/224.

Geometrically encoded metadata structure240/340may be isolated via an algorithm that compares an arbitrary point in the object in which geometrically encoded metadata structure240/340is included, assuming but not limited to it having no other identifying markers, such as “layer”, color, or other features, to all other points in the object in order to find the set(s) of points that are disconnected spatially from the entire dataset, for which geometrically encoded metadata structure240/340acts as spatial metadata. Essentially this process, which can be computed with any number of suitable algorithms, divides the points of the object as a whole into two or more subsets of objects by assigning an identifying variable to the starting point and all other points found to be connected to the starting point either directly or by establishing that additional points are connected to other points that have been tested to connect with the starting point. The process can be repeated recursively by incrementing the identifying variable and applying the same process to the set of points that were not identified as having a connection with the starting point. The result should include more than one set of points i.e., multiple disconnected objects. If the outcome is just one set of points identified as being an attached collection, then the process has failed.

Assuming that multiple detached objects have been found, action582may include identifying one of them as being likely to be geometrically encoded metadata structure240/340based on any number of pre-established parameters unlikely to be part of a common 3D model, and fitting in with the intrinsic parameters of the identifier definition. There may be an exact quantity of points established extrinsically, as part of the metadata specification. Any other objects can thus be eliminated from consideration. There may be other specification rules that will be established, such as, per the example illustration ofFIG. 3, having precisely six points (two polygons with three points each) that have three attached neighbor points, the rest having four points. It may be ideal to establish the endcaps370aand370b(endcap polygons) as the basis for repairing models that have been “triangulated,” i.e., models that have been forced to be deconstructed from quadrilateral-faces into objects being entirely made of triangles, because the endcaps370aand370bwill have four connections on each point, and any other face will have at least one neighbor connecting to five other points. With the knowledge of which faces are endcaps370aand370b, the triangle endcap/quadrilateral identifier face construct needed to read the metadata encoding can be re-established. It is noted that, in order to expedite decoding, a specification that requires certain character(s) be encoded as a header sequence may be established such that erroneous or impossible configurations are ruled out in order to optimize processing.

As a specific example of limited or restricted searching, where media content124/224includes a 3D model of an animated character, it may be predetermined that geometrically encoded metadata structure240/340, when present, is contained within an eye of the animated character. In that use case, action582may be limited to searching one or both eyes of the animated character included in media content124/224for geometrically encoded metadata structure240/340. Searching of media content124/224for geometrically encoded metadata structure240/340may be performed by media content validation software code110/210, executed by hardware processor104, and using metadata structure detection module212.

Flowchart580continues with, when geometrically encoded metadata structure240/340is detected, identifying original 3D geometry242/342of detected geometrically encoded metadata structure240/340(action583). In some use cases, the original 3D geometry of geometrically encoded metadata structure240/340may be unaltered, in which cases action583corresponds to recognizing the geometry of detected geometrically encoded metadata structure240/340as original 3D geometry242/342. For example, the geometry of geometrically encoded metadata structure240/340may be identified as original 3D geometry242/342based on comparison of checksums362-366and checksum361of checksums362-366to their respective known values.

In some use cases, however, original 3D geometry242/342of geometrically encoded metadata structure240/340may have been deformed, either unintentionally during use or as a result of file conversion, or intentionally through editing or manipulation. For example, in some cases, after being created but before being received by system100in action581, media content124/224may have been converted from a first data format to a second data format. As a specific example, where media content124/224includes a 3D model created using a software application such as Maya®, AutoCAD®, Houdini®, 3ds MAX®, or SolidWorks®, geometrically encoded metadata structure240/340may be deformed when media content124/224is manipulated or otherwise processed using another of those software applications before being received by system100in action581.

Where deformation of geometrically encoded metadata structure240/340has occurred, action583may include restoring original 3D geometry242/342of geometrically encoded metadata structure240/340. For example, restoration of original 3D geometry242/342may include moving endcap370ato the origin in Cartesian space, (0, 0, 0) so that UM2 is located at the origin.

UM1, along with all other points except UM2, may then be transformed via rotation on the origin so that UM1 is posed at a 90° angle to the X-axis and is resting on the Y-intercept co-linear to UM2 and in a positive offset. UM1, along with the points attached to UM1 that are not attached to UM2 or UM3, and rest on the outward-facing polygon's neighbors as defined by the clockwise arrangement of point ordering of the first polygon attached to UM1 not attached to UM2 or UM3, are normalized by scaling geometrically encoded metadata structure240/340so that the distance along the Y-Axis of UM1 is 1.0 (out to any specified digits of accuracy) units from the origin at UM2.

UM3 and its child points are rotated along the UM1-UM2 axis to be at a 90° angle to the X-Y plane in the positive Cartesian space. The points of UM3 along with its children should now be coplanar in the X-Z orientation, in other words the point UM3 should be resting at zero in the X and Y-axes, and its attached points along the X-direction should lay coplanar to the X-Z plane intersecting UM2. The distance from UM3 to UM2 should ideally be 1 unit, i.e., (x, y, z)=(0, 0, 1) as it should have maintained its relationship to UM1 as UM1 was scaled to be one unit from UM2. If this is not the case, it is possible that some manner of squash-and-stretch animation has been applied to the model including geometrically encoded metadata structure240/340at some point. The points along the X-Axis corresponding to and including UM3 will be scaled to make UM3 be at the location 1.0.

The points connecting to and coplanar with UM1 should now match the points connecting to and coplanar with UM2 because they are meant to be redundant encoding and therefore identical. The initial “n” number of encoded ASCII values can now be read from the initial set of points along and coplanar to UM1. These values are verified to have corresponding checksum values in the plane of points at the same X-offset as any particular character and coplanar+connected to UM3. It is noted that in some implementations, it may be advantageous or desirable to add an additional reconstruction variable in addition to our example's three-dimensions, or to replace the redundant encoding along UM2 with another value that may be found to aid in reconstruction.

If the values in UM2 do not match the values in UM1 after reconstruction, reprocessing may be attempted using UM1 or UM3 as UM2, i.e., as the (0, 0, 0) origin point, (assuming they have been rotated during deformation). In a situation where geometrically encoded metadata structure240/340has been inverted (mirrored) or rotated 180° from the original encoding, reprocessing may be attempted by using the opposite endcap's points as UM2. In another example, reprocessing may be attempted by scaling UM1's children as well as UM2's children until they can be used to accurately compute UM3's checksum (testing for valid data), or by processing only UM1 or UM2 (i.e., one without the other) to see if valid metadata results. Additional transformations via translation or rotation of the points of each character of the children of UM1, UM2, and UM3 may be made in attempts to extract metadata from extremely deformed models, with the potential for success or failure. In this case the potential of placing multiple redundant metadata objects in various non-obtrusive positions (e.g., inside a character) may be examined, and the differential variation of or metadata object's clones may be used to further aid the possible potential of reconstructing the message in cases of extreme modification of the overall object including geometrically encoded metadata structure240/340.

Identification of original 3D geometry242/342of detected geometrically encoded metadata structure240/340may be performed by media content validation software code110/210executed by hardware processor104, and using geometry analysis and restoration module214.

Flowchart580continues with extracting metadata244from geometrically encoded metadata structure240/340(action584). Metadata244may be an encoded metadata, for example. Moreover, metadata244may be encoded by original 3D geometry242/342of geometrically encoded metadata structure240/340, which may be a 3D geometry, for example. Extraction of metadata244from geometrically encoded metadata structure240/340may be performed by media content validation software code110/210executed by hardware processor104, and using metadata extraction module216.

Flowchart580continues with decoding metadata244extracted from detected geometrically encoded metadata structure240/340based on original 3D geometry242/342identified in action583(action585). Decoding of metadata244based on original 3D geometry242/342of geometrically encoded metadata structure240/340may be performed by media content validation software code110/210, executed by hardware processor104, and using metadata decoding module218. For example, metadata decoding module218may be configured to translate geometric values included in metadata242into decoded metadata128/228in the form of descriptive metadata and/or a URI of a repository of descriptive metadata unique to media content124/224.

Flowchart580can conclude with obtaining validation status138/238of media content124/224based on decoded metadata128/228(action586). In some implementations, hardware processor104may execute media content validation software code110/210to obtain validation status138/238of media content124/224using validation module248. As discussed above, validation status138/238may take the form of one or more of authorship, revision history, descriptive information, ownership, licensing history, and distribution rights for media content124/224, for example. In some implementations, media content validation software code110/210may utilize validation module248to obtain validation status138/238from media content validation database122optionally stored by system memory106. However, and as noted above, in some implementations, decoded metadata128/228may include a URI, such as a URL, for use in obtaining validation status138/238from a remote source, such as media content validation source132accessible via communication network130.

Media content validation source132may provide validation status138/238in the form of authorship, revision history, descriptive information, ownership, licensing history, and distribution rights for media content124/224. Moreover, and as also noted above, in some implementations, validation status138/238may include a link to other database elements such as the original version of media content124/224(for such purposes as reverting changes), or to variations of media content124/224suitable for specific use cases. For example, validation status138/238for media content124/224including an architectural model used for Building Information Modeling may include a link to another version of the model tailored to 3D printing or VR applications.

In some implementations, user120may be authorized to modify validation status138/238for media content124/224by adding information, deleting information, or updating existing information included in validation status138/238. In one such implementation, a blockchain protection protocol may be implemented by system100to prevent unauthorized or unintentional modification of validation status138/238for media content124/224when validation status138/238is stored in media content validation database122of system100.

Although not included in the exemplary outline provided by flowchart580, in some implementations, the present method may further include providing validation status138/238as an output to user system134for rendering on display136. In those implementations, validation status138/238may be output to user system134by media content validation software code110/210, executed by hardware processor104, and via communication network130. Furthermore, in one implementation, system100may include user system134, and may utilize user system134to render validation status138/238of media content124/224on display136. As noted above, display136may be implemented as an LCD, an LED display, an OLED display, or any other suitable display screen that performs a physical transformation of signals to light.