This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-18
Channels
- # announcements (17)
- # babashka (42)
- # beginners (34)
- # calva (78)
- # cherry (1)
- # cider (7)
- # clojure (64)
- # clojure-europe (19)
- # clojure-nl (2)
- # clojure-norway (54)
- # clojure-uk (3)
- # clojurescript (21)
- # cloverage (1)
- # conjure (1)
- # core-async (11)
- # cryogen (16)
- # cursive (1)
- # data-oriented-programming (1)
- # datahike (5)
- # fulcro (2)
- # girouette (1)
- # helix (10)
- # hyperfiddle (1)
- # jobs (1)
- # kaocha (4)
- # nbb (7)
- # off-topic (6)
- # pathom (4)
- # polylith (21)
- # rdf (9)
- # releases (2)
- # shadow-cljs (3)
- # sql (12)
- # squint (68)
- # vim (33)
- # xtdb (29)
I would like to link to a prior version of an attribute as defined in the prior version of my schema. There is owl:priorVersion
which is used in lexinfo in this manner, however that usage seems to be incorrect as the domain and range of owl:priorVersion
are both owl:Ontology
. Is there some other well-known attribute which accomplishes this?
The way I read the OWL 2 recommendation, that's indeed not a suited choice. Section 5.5 describes all annotation properties, and I think you're right there's nothing suitable there. I'm interested in your case though. Could you elaborate why you want to do this?
Would any of the relationships discussed here make sense?
I’m not sure the dcat property is quite right :thinking_face:
I think rdfs:seeAlso
might be a little better and also carries less entailment baggage than the dcat property; though arguably the intention is for ?objects
to provide more information about ?subjects
; than for ?additional_properties
to provide more information about them; which I think is closer to the intent you want…
I’d be tempted to find something in prov-o:
https://www.w3.org/TR/2013/REC-prov-o-20130430/