AgentShape confusion

[dennisvang]

The default FDP Resource schema defines an AgentShape:

FAIRDataPoint/src/main/resources/nl/dtls/fairdatapoint/database/mongo/migration/production/0016_shape-resource.ttl

Lines 65 to 73 in 6587b09

	:AgentShape a sh:NodeShape ;
	sh:targetClass foaf:Agent ;
	sh:property [
	sh:path foaf:name ;
	sh:nodeKind sh:Literal ;
	sh:minCount 1 ;
	sh:maxCount 1 ;
	dash:editor dash:TextFieldEditor ;
	] .

However, if we define additional AgentShapes such as the following, the FDP gets confused and applies constraints from the default AgentShape:

...

hri:AgentShape a sh:NodeShape;
  rdfs:label "Agent"@en;
  sh:targetClass foaf:Agent;
  sh:property <http://data.health-ri.nl/core/p2/AgentShape#foaf:name> .

<http://data.health-ri.nl/core/p2/AgentShape#foaf:name> sh:path foaf:name;
  sh:name "name"@en;
  sh:description "A name of the agent."@en;
  sh:minCount 1;
  sh:nodeKind sh:Literal;
  dash:viewer dash:LiteralViewer;
  dash:editor dash:TextAreaEditor .

See details here: FAIRDataTeam/FAIRDataPoint-client#201 (comment)

Actually I'm not sure if this is expected behavior, based on this set of schemas, or if it's the FDP getting confused...

[dennisvang]

This issue arose while doing a quick&dirty test of a small part of the health-ri schema in a default fdp, with default Resource schema. This leads to a conflict.
The full health-ri schema overrides the Resource, so this issue should not arise when using the full health-ri schema.