V4 #20
V4 #20
Conversation
acdh:BinaryContent within collections.
Non-linked variants were created only for optional and recommended properties as for required ones we would be unable to properly express the cardinality requirement. We can also look at it in a way that if a property is required, it's so imporant we want it to be LOD and don't allow non-linked data.
|
I do agree with introducing acdh:hasOrder and dropping acdh:hasLocationPath The introduction of non-linked counterparts to |
|
Could you maybe please remind me on how the folder structure of downloaded collections is now determined without |
It's based on |
|
@zozlak and I talked and came to this conclusion: Introduce the following properties:
Why not the others as well? Because it seems that most messy named entities (Agents) are coming in via As for Thus, remove |
|
For For Also: should |
* drop acdh:hasNonLinkedCoverage, acdh:hasNonLinkedSpatialCoverage, acdh:hasNonLinkedContributor, acdh:hasNonLinkedCreator, acdh:hasNonLinkedDigitisingAgent, acdh:hasNonLinkedEditor, acdh:hasNonLinkedFunder, and acdh:hasNonLinkedPrincipalInvestigator * fix acdh:ordering, rdf:comment and skos:altLabel for acdh:hasOrder and acdh:hasNonLinkedActor
…ypes and lang tags
…h:automatedFill "true" so they are easy to filter out
|
@bellerophons-pegasus I have a doubt regarding the My second doubt is about the |
acdh-schema.owl
Outdated
| @@ -212,14 +242,26 @@ Kardinalität von acdh:hasCategory für acdh:BinaryContent gändert zu 0-n, um m | |||
|
|
|||
| <owl:AnnotationProperty rdf:about="https://vocabs.acdh.oeaw.ac.at/schema#defaultValue"> | |||
| <rdfs:comment xml:lang="de">Gibt den Standardwert einer Eigenschaft an. Der Standardwert wird verwendet, wenn diese Eigenschaft in einer Klasse verwendet wird, aber kein Wert angegeben wurde.</rdfs:comment> | |||
| <rdfs:comment xml:lang="en">Indicates a default property value. The default value is assigned when a class matches property's domain but no property value has been provided.</rdfs:comment> | |||
| <rdfs:comment xml:lang="en">Indicates a default property value. The default value is assigned when a class matches property&apos;s domain but no property value has been provided.</rdfs:comment> | |||
There was a problem hiding this comment.
I think there is a small typo here, &apos; should be corrected to '
acdh-schema.owl
Outdated
| <rdfs:domain rdf:resource="https://vocabs.acdh.oeaw.ac.at/schema#BinaryContent"/> | ||
| <rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#anyURI"/> | ||
| <rdfs:comment xml:lang="de">Gibt das IIIF-Manifest (B) an, das für die Darstellung der Ressource (A) verwendet werden soll. Der Wert ist entweder die URL des zu verwendenden IIIF-Manifests (externe URLs sind möglich, wir empfehlen jedoch Ressourcen aus dem Repositorium) oder, wenn das IIIF-Manifest automatisch auf der Grundlage der Metadaten der Ressource generiert werden soll, die URI des Dissemination-Services: https://id.acdh.oeaw.ac.at/dissemination/iiifmanifest.</rdfs:comment> | ||
| <rdfs:comment xml:lang="en">Indicates the IIIF manifest (B) to be used for the presentation of the Resource (A). The value is either an URL of the IIIF manifest to be used (we recommend it to be another Resource in the repository but it can also be external) or, if the IIIF manifest should be generated automatically based on the Resoure's metadata, the URI of the dissemination service: https://id.acdh.oeaw.ac.at/dissemination/iiifmanifest.</rdfs:comment> |
There was a problem hiding this comment.
Two small typos:
- remove double white space between
external)andor - correct
ResouretoResource
Backward incompatible changes
acdh:hasLocationPathas we don't use it for quite some time already. Triples with that property (e.g. 55k on apollo) can be just removed.New properties
acdh:hasOrderacdh:orderingvalueacdh:hasCoverage(acdh:hasNonLinkedCoverage),acdh:hasContributor(acdh:hasNonLinkedContributor) and their subproperties (acdh:hasActor-acdh:hasNonLinkedActor,acdh:hasSpatialCoverage-acdh:hasNonLinkedSpatialCoverage,acdh:hasCreator-acdh:hasNonLinkedCreator,acdh:hasDigitisingAgent-acdh:hasNonLinkedDigitisingAgent,acdh:hasEditor-acdh:hasNonLinkedEditor,acdh:hasFunder-acdh:hasNonLinkedFunder,acdh:hasPrincipalInvestigator-acdh:hasNonLinkedPrincipalInvestigator)achd:hasContact,acdh:hasDepositor,acdh:hasHosting,acdh:hasLicensor,acdh:hasMetadataCreator,acdh:hasOwner,acdh:hasRightsHolder) we won't be able to express the cardinality restriction. We can also look at it in a way that compulsory properties so important that we require them to be LOD.acdh:recommendedClassannotations but if we think they should, we can add them.owl:inverseOfannotations because they are datatype properties.acdh:hasNonLinked{originalProperty}because we already hadacdh:hasNonLinkedIdentifierbut I'm not personally attachedacdh:orderingvalues