-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add relation #19
Comments
for example, someone may feel that for |
this can be represeted by the statement:
https://www.w3.org/2009/08/skos-reference/skos.html#broader The inference of the relation
is automated and should not be encoded. |
we shall only request that people make the relationship one way |
what does someone need to know in order to propose a link? |
page structure is very similar to #36 |
|
You can propose a link between two concepts. For example: The concept is ‘Pressure reduced to MSL’ You may want to suggest that this has a broader concept and that the broader concept is ‘Pressure’. We only accept suggestions for concepts to be linked in a broader way. To make the suggestion: |
We only accept suggestions for concepts to be linked in a broader way, the inverse relation is inferred, so we do not encode it. |
Before
After
|
highlighter pen: |
#43 has conflicts. updates made to http://test.wmocodes.info/ui/about/broader outstanding work:
close #43 |
|
Updated `_hlist-render-child.vm` to address issue #18.
i want to provide a semantic relationship (skos:broader) between two existing entities
in scope:
The text was updated successfully, but these errors were encountered: