Status: submitted upstream as linked-art/linked.art#808
Proposed pull request
Title: `Clarify the ULAN predicate in the unmodeled relationship example`
Base: `linked-art/linked.art:v1.1`
Change: add the following line after the existing `aa.assigned` statement in
`docs/model/assertion/index.md`:
aa.assigned_property = "http://vocab.getty.edu/ontology#ulan1102_student_of"
Proposed description
The current unmodeled-relationship example describes Ferdinand Bol as a student
of Rembrandt and recommends `assigned_property` when an appropriate predicate
is known, but the generated example supplies only the display name. This change
adds Getty's existing `ulan1102_student_of` predicate to the example.
The direction matches the example: Ferdinand Bol is the subject carrying
`attributed_by`, `student of` is the predicate, and Rembrandt is the assigned
object. The full URI avoids requiring an additional compact-prefix declaration.
Sun & Rain Works tested the same shape in Meta Museum using the canonical Linked
Art context and the local profile inspector. The fixture and test are documented
in `docs/linked-art/ulan-associative-relationships.md`(../linked-art/ulan-associative-relationships.md).
This is intended as a narrow clarification of the existing pattern, not as a
proposal to add the GVP properties to the Linked Art context.
Verification
- Upstream source branch checked at `fded7e715dcbe7642b6658151a616153dacf84a0`.
- Public fork commit: `84a7203`.
- Exact Getty predicate and inverse direction checked against the Getty Vocabulary Program ontology.
- Meta Museum fixture passes `tests/quality/linked-art-1-1-agenda-fixtures.test.ts`.
- A clean Python virtual environment installed the upstream `requirements.txt` and `python -m mkdocs build --clean` passed.
- The generated Linked Art HTML and graph include the full `ulan1102_student_of` URI.
Publication boundary
Repository policy says significant editorial changes follow community
discussion and consensus. The topic was discussed in the Linked Art Slack
meeting channel and the owner approved public submission. Pull request
#808 is now open for
community review; submission is implementation evidence, not acceptance or
community consensus.