You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that currently solid team promotes practice of dropping additional terms to namespaces under control of someone else. I think that creating dedicated namespace for such terms would provide a cleaner way of doing it.
Such terms should have IRIs and definitions in namespace controlled by solid team, if they get adopted by vocab which they patch, combination of owl:equivalentProperty, owl:equivalentClass and schema:supersededBy can help with deprecating term from solid monkey patches.
The text was updated successfully, but these errors were encountered:
It seems that currently solid team promotes practice of dropping additional terms to namespaces under control of someone else. I think that creating dedicated namespace for such terms would provide a cleaner way of doing it.
http://www.w3.org/2006/vcard/ns does not include
AddressBook
orhasIndividual
(as used in solid-contacts)Such terms should have IRIs and definitions in namespace controlled by solid team, if they get adopted by vocab which they patch, combination of
owl:equivalentProperty
,owl:equivalentClass
andschema:supersededBy
can help with deprecating term from solid monkey patches.The text was updated successfully, but these errors were encountered: