Difference between revisions of "C 0000016 mmmv folder structure for ID labeled artifacts t2"

From commentsarchive
Jump to: navigation, search
m
m
Line 3: Line 3:
 
* Related pages: [[C_0000007 mmmv_btreelike_folder_structure_t1]]
 
* Related pages: [[C_0000007 mmmv_btreelike_folder_structure_t1]]
  
<span style="color:red;>This specification is UNUSABLE due to being INCOMPLETE. It is still being written.</span>
+
<!-- span style="color:red;>This specification is UNUSABLE due to being INCOMPLETE. It is still being written.</span -->
  
 
It's the same as the [[C_0000013 mmmv_folder_structure_for_ID_labeled_artifacts_t1|mmmv_folder_structure_for_ID_labeled_artifacts_t1]], except that the folders that contain an artifact also contain a folder that is named  
 
It's the same as the [[C_0000013 mmmv_folder_structure_for_ID_labeled_artifacts_t1|mmmv_folder_structure_for_ID_labeled_artifacts_t1]], except that the folders that contain an artifact also contain a folder that is named  
Line 10: Line 10:
 
     <artifact file name>_artifact_record
 
     <artifact file name>_artifact_record
 
</syntaxhighlight>
 
</syntaxhighlight>
 +
 +
The format of the contents of the artifact record folder is intentionally left unspecified by this specification.
  
  

Revision as of 12:59, 14 April 2021


It's the same as the mmmv_folder_structure_for_ID_labeled_artifacts_t1, except that the folders that contain an artifact also contain a folder that is named

    <artifact file name>_artifact_record

The format of the contents of the artifact record folder is intentionally left unspecified by this specification.


Implementation Comments

If the artifact is a file, then the artifact name and its records folder name related parsing can be avoided by looking, which of them is a file and which of them is a folder. In the general case the parsing can be avoided by using 2 mmmv_folder_structure_for_ID_labeled_artifacts_t1 instances: one for artifacts and another one for artifact record folders.