Hi Lars,
On 3/3/16 9:00 PM, Svensson, Lars wrote:
>> On application-specific shape and a domain shape, I was thinking of
>> distinction between:
>>
>> - general constraints like 'a ex:book must have at least one dc:creator' -
>> considering that this is a constraint for every instance of a class ex:book
>> defined in an OWL ontology, but that OWL doesn't allow to represent this
>> with the right semantics.
>>
>> - specific constraints like 'a book title must come with a language tag' - which
>> is much more crucial for applications with language-related requirements
>> than for the library domain in general.
>>
>> Does this makes sense?
>
> Yes, that makes sense. So the general idea should be that an application imports the domain shape into its application-specific shape and uses the complete shape to perform the validation (or build the UI or whatever...)?
>
Exactly. Note that this was just an idea I had, just in case people from a domain would agree to create shapes that are worth sharing/reusing among applications. Which is why I've put it in dotted line in the diagram.
Cheers,
Antoine
|