You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What a poor decision invalidating External References for File objects. What about the situation where i have an external BLOB store that i want to connect to my knowledge graph???? How am i meant to store file objects in a knowledge graph????
Based on an arbitrary decision to stop External References for Files (like why????), I cannot support this use case, and have to either reintroduce an illegal property, or use the Artifact object, which has very poorly thought through mechanisms for description
For me to store the file as an artifact, and use the url field, i must hash the file. Worse, I can't name the file or provide a description of it, since there are no fields for this in the Artifact object. So in the case where i want to store a text file, it is a nameless url, while it has to be hashed I am unable to describe it, which is frankly weak for most apparent use cases.
This seems a set of very poor decision without any real rationale. I am not happy about this at all. You make it very hard to utilise Stix 2.1. Sorry if I am over-passionate about this, but it is a blockage for me
The text was updated successfully, but these errors were encountered:
brettforbes
changed the title
Why does File Not have External References??? Very Poor Decision
Why does File Not have External References??? Seems like a poor decision
Apr 14, 2023
Hi,
What a poor decision invalidating External References for File objects. What about the situation where i have an external BLOB store that i want to connect to my knowledge graph???? How am i meant to store file objects in a knowledge graph????
Based on an arbitrary decision to stop External References for Files (like why????), I cannot support this use case, and have to either reintroduce an illegal property, or use the Artifact object, which has very poorly thought through mechanisms for description
For me to store the file as an artifact, and use the url field, i must hash the file. Worse, I can't name the file or provide a description of it, since there are no fields for this in the Artifact object. So in the case where i want to store a text file, it is a nameless url, while it has to be hashed I am unable to describe it, which is frankly weak for most apparent use cases.
This seems a set of very poor decision without any real rationale. I am not happy about this at all. You make it very hard to utilise Stix 2.1. Sorry if I am over-passionate about this, but it is a blockage for me
The text was updated successfully, but these errors were encountered: