|
|
@@ -76,7 +76,7 @@ granular_markings Imported from [STIX v2.0 Part 1]: Section 3.1 |
|
|
hashes A list of hash strings. |
|
|
hashes A list of hash strings. |
|
|
lang RFC XXXX language of the properties. |
|
|
lang RFC XXXX language of the properties. |
|
|
parent_refs List of UUIDv4s of MetaData Object that overlay. Any properties on this object override the parent. (allow deletion via None/null?) Any missing properties are passed through to the parent for resolution. The first/earliest object that has a property is used in that objects later in the list are "hidden" by the earlier objects. |
|
|
parent_refs List of UUIDv4s of MetaData Object that overlay. Any properties on this object override the parent. (allow deletion via None/null?) Any missing properties are passed through to the parent for resolution. The first/earliest object that has a property is used in that objects later in the list are "hidden" by the earlier objects. |
|
|
mime-type The mime-type. If the set of bytes is polymorphic, there should be one for each "type". |
|
|
|
|
|
|
|
|
mimetype The mime-type. If the set of bytes is polymorphic, there should be one for each "type". |
|
|
uri List of URI's where the file may be located. |
|
|
uri List of URI's where the file may be located. |
|
|
child_files A dictionary where the keys are the file names and the values are hash strings. (One issue w/ using hashes is that you can't tie YOUR idea of the metadata, but it also allows a person to have metadata about a file that is private and not be forced to share it, nor create a dummy object.) |
|
|
child_files A dictionary where the keys are the file names and the values are hash strings. (One issue w/ using hashes is that you can't tie YOUR idea of the metadata, but it also allows a person to have metadata about a file that is private and not be forced to share it, nor create a dummy object.) |
|
|
|
|
|
|
|
|
|
