Knowledge forces any documents into the Document entity type; however it may be more appropriate to model the documents as multiple entity types. For example, a construction company may have multiple documents for a project (each with their own distinct attributes): bids, closing documents, permits, designs, ROW references, parcel scans, status reports, etc. Grouping all of these documents into a single entity type may limit (or complicate) analysis of a network. Another way to think of this is allowing documents to be added as properties of an entity, rather than entities themselves (in the same way shape is a property of an entity, rather than a separate entity).
