Repository navigation
Replies: 1 comment
What Croissant can say about licences and terms (questions 3 and 4)Checked against the Croissant 1.1 specification (published 2026-01-29) and the open issues of mlcommons/croissant. Several licences: yes, but only for the whole dataset. Terms for part of a dataset: yes, through Provenance on any part: yes. PROV-O properties ( Still open upstream. #544 (the manifest's own licence, What it means hereA published set can be laid out like this, with nothing added to the ADIRO TBox:
Two caveats: |
Uh oh!
There was an error while loading. Please reload this page.
Motivation
A drawing collected from a public source comes with terms: who holds the rights, whether it may be redistributed, what credit line it needs. When an ADIRO-annotated set of drawings is published, those terms decide what can be shipped. Some sources allow the files to be redistributed; others allow only a link to the original. The set as a whole then has terms of its own: the annotations' licence, and the combined terms of everything in it.
ADIRO cannot record any of this today. This Discussion is a brainstorm: what to record, where, and how it relates to what exists. It is not a proposal to add terms yet. Once a direction is agreed here, a GitHub issue records the decision and a pull request implements it.
What already exists
sourceLocation(where a file's bytes were obtained from) andsourcePage(the catalogue record or landing page that describes it at its origin) toadiro_provenance:DrawingFile. A file made from another file points back to it throughprov:wasDerivedFrom.croissant-comparison.mddecided that dataset-level metadata (files, splits, licence, creator, version) belongs in a Croissant manifest (schema.orgDataset) at publication time, outside the ADIRO TBox. The direction here is to keep that decision if it can hold what is needed.adiro_drawing_metadatahasProjectandDrawingPackage. They group drawings as their authors did (a project, a submission package), not as a curated set for publication, which mixes drawings from many projects and sources.Where the terms are stated
Terms are rarely stated per file. A public archive states them on an item (a catalogue record that holds many scanned drawings) and on the collection the item belongs to; a publisher of a drawing set states them once for the set. Recording them on every file would repeat the same statement thousands of times. Recording them once per source item, with each file pointing at its item, keeps one statement per unit the publisher actually licensed.
sourcePagefrom #229 already names that item's page, so the item is reachable from every file.Questions
adiro_provenance(then a competency question is needed, see 5) or only in the publication manifest?dcterms:license);Which of these does Croissant (or schema.org, Dublin Core) already have a field for?
licenseand conditions? Can a Croissant manifest list several licences, or state terms for a part of a set (a file set or record set) rather than the whole?licenseseems the natural place. Is a separate field needed to tell the annotations' licence from the drawings' terms?adiro_provenance(the source item of question 1), a use case has to name it: probably a new use case for publishing an annotated set.sourceLocationandsourcePage, with no guarantee that the address stays stable: the original address is kept for reference and trust, not as a promise. When a source allows redistribution and a copy is published elsewhere, the copy is astorageLocationand the original address is still kept. Is anything else needed for that case?Not in scope here
Where a published set is hosted, and which licence a given set's annotations carry: both are decided later, set by set.
All reactions