Repository navigation
Brainstorm: where a term records the standard it corresponds to (rdfs:comment, skos:note, a definition/commentary split, or a dedicated property) #265
BH-Tianyang
started this conversation in
Ideas
Replies: 1 comment
|
Decision: option C. A term's definition moves to This answers the questions above:
Options A, B and D are not taken. A dedicated citation property (D) can still be added later if a consumer needs to select terms by standard; nothing here prevents it. The change is #273: tooling first, then one module per pull request. Until a module is split, the sub-issues of #262 (#264, #268, #272) append their sentence to |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Motivation
#262 records, per term, which drawing standard (ISO, EN, UK, US) the term corresponds to, and #264 is the first set of changes. Each change is a citation such as "Corresponds to ISO 7200:2004 §5.2.2 (title)". The question here is where in the Turtle a term records that citation. It affects every module that #262 covers, so it is worth deciding once before the citations spread.
What exists
rdfs:commentis ADIRO's definition vocabulary (Usage of annotation properties). Many comments already carry more than the definition (examples, design rationale, issue links), and two cite a standard:assertsClient(ISO 7200) andassertsOriginator(ISO 19650-2).skos:definitionfor the definition,rdfs:commentfor the commentary. pyLODE renders both.skos:noteis used once, onTitleblockFieldScheme. No class or property carries one. The Markdown pages (ttl2md) showskos:noteon schemes and concepts, but on a class or property only for annotation properties the module declares, and no module declares a SKOS property; whether pyLODE shows it is not verified.skos:closeMatchand for alternative labels on properties: theskos:closeMatchlinks on properties inadiro_provenanceand theskos:altLabels on properties inadiro_drawing_metadataappear on neither page.skos:closeMatchinheritsrdfs:domain skos:Concept, which is one reason a mapping triple was not used there. SKOS's documentation properties (skos:note,skos:scopeNote,skos:definition) have no domain.TitleblockFieldScheme's scope note says a per-itemdcterms:sourceis to follow once an anonymised source dataset is public: a precedent for recording a source in its own property.Options
rdfs:commentskos:noteon the termttl2md(and possibly pyLODE) is changed; no ADIRO term uses it todayskos:definitionfor the definition,rdfs:commentfor the commentary, citations in the commentarydcterms:source, or an ADIRO annotation property)dcterms:sourceis meant for a resource the term is derived from, which a standard clause is not exactlyA and D can be combined later: a sentence for the reader now, a property for tools when a consumer needs it.
Questions
skos:closeMatchlinks and property alternative labels visible.Out of scope
Which standards and clauses each term cites (that is #262 and its sub-issues), and alternative labels taken from standards (proposed on Discussion #64).
Until this is decided, the sub-issues of #262 use option A, so they are not blocked; if another option is chosen, moving the sentences is mechanical.
All reactions