Wikidata:Property proposal/ligament insertion

Not done

Description	anatomic structures to which a ligament is anchored
Data type	Item
Domain	ligament (Q39888)
Allowed values	anatomical structure (Q4936952)
Example 1	nuchal ligament (Q519216) → occipital bone (Q16317)
Example 2	Interspinal ligament (Q1824640) → spinous process (Q915235)
Example 3	thyrohyoid membrane (Q7799740) → thyroid cartilage (Q171093)
Example 4	thyrohyoid membrane (Q7799740) → hyoid bone (Q16332)
Distinct-values constraint	yes

Comment @Dbult: muscle origin (P3490) and muscle insertion (P3491) are very rarely used (64 and 58 times right now), I'm wondering if they are really needed. Couldn't we used an other property, for instance connects with (P2789)? (with qualifier if we need more precision) It's already what is done between bones, e.g. Q16317#P2789. Cheers, VIGNERON (talk) 16:51, 15 May 2022 (UTC)[reply]
Muscle origin and insertions are important information for students who learn anatomy. It's therefore information that's useful for a Wikipedia to pull into an infobox. Just storing the information in connects with (P2789) does not allow the information to be easily pulled into an infobox. ChristianKl ❪✉❫ 15:00, 19 July 2022 (UTC)[reply]
I changed the description from "anatomic entities" to "anatomic structures". Insertion inherently is a relationship with entities that have a material inherent 3D shape. Those anatomic entities that are not anatomical structures don't seem to me like valid values.

https://www.orthobullets.com/basic-science/9016/ligaments seems to call this relationship "bone insertion". To what extend does it makes sense to speak of ligaments being anchored to different entities then bones? It's also worthwhile to see the distinctions that are made on that page between different insertion. How do we want to model those? ChristianKl ❪✉❫ 15:08, 19 July 2022 (UTC)[reply]

Not done no support for creation of this property --DannyS712 (talk) 01:33, 3 December 2022 (UTC)[reply]