According to the best documentation i could find adding an archetype is based on content from a local file directory structure (in ${STARDOG_HOME}/.archetypes) .
How can one use archetypes in a cloud version where there is no access to this?
adding the named archetypes (prov, prov-inline) to the database properties had no apparent effect and generated no warnings.
If it looks at the stardog repo, then how does one create custom archetypes and load them to a cloud instances.
presuming there is someway to load archetypes, how exactly are they supposed to work - i.e. if I turn on reasoning in Stardog Explorer does the archetype become part of the "default schema" ?
Where do constraints get applied - on adding data - generating an error? Or is it only on a validation query as per Data Quality Constraints | Stardog Documentation Latest