Closed fosrias closed 3 years ago
not sure i see a problem here. you mean that the
On Mon, Oct 19, 2015 at 5:45 PM, Mark W. Foster notifications@github.com wrote:
Currently, the spec indicates that if we create a new descriptor referencing another and define a key in the new descriptor, it replaces the prior. This mechanism can lead to changing fundamental meaning in a strict interpretation.
Need a mechanism to expand. E.g.
The color white A spanish friendly variant Possibly contrived. But the second doc significantly changes the resulting descriptor by my current interpretation of the spec.
Something we need to think about.
— Reply to this email directly or view it on GitHub https://github.com/alps-io/spec/issues/77.
Yes. By how I interpret the current spec.
two things.
1) this might be pointing to the difference between "override" (href) and "sameAs" (src). do you mean to actually override id="white" (href) or add an equivalent (src) here?
2) FWIW, i think the doc element is a non-critical element -- at least
for machines. i don't expect ppl to write machine code that sets up a
dependency on the contents of the "doc" element (but i could be just trying
to weasel out of a problem
Well, by my interpretation of the spec, I have overridden the doc. But in this case, I just want to expand on the original descriptor without fundamentally changing its semantic meaning. This later scenario is not afforded in the spec ATM IMO (I have been hanging around you too much using these acronyms).
Yes, the sameAs working like href, or an array of the URIs is an interesting possibility
Sorry for the chain, so href
is inheritance mechanism and src
as an expansion mechanism or something like that.
right - i think this goes back to our thread on the list today.
i'd like to see some kind of "sameAs" pattern and i think it can work along with a single construct - "src" property
http://alps.io/profiles/colors/
http://alps.io/profiles/languages/spanish/
this illustrates reference to a source of the ID, not an override.
just a thought.
@mamund I think we can close this as https://github.com/alps-io/spec/issues/89 could cover this. I think the src
argument above works. I am not sure now that expanding the semantic meaning actually means anything 😛 . If something means more, maybe you have changed the meaning. If you want to define broader understanding, but it means the same, src
should work.
Closed with a ref to issue #89
Currently, the spec indicates that if we create a new descriptor referencing another and define a key in the new descriptor, it replaces the prior. This mechanism can lead to changing fundamental meaning in a strict interpretation.
Need a mechanism to expand. E.g.
Possibly contrived. But the second doc significantly changes the resulting descriptor by my current interpretation of the spec.
Something we need to think about.