On 18-07-2012 16:11, Aaron Brown wrote:
To me IdRef is only for referencing/reusing or
chaining existing elements. That's all. Without inheritance. Simple use
case: a resource X is defined in a topology storage/service TS1. X is
pointed in a topology storage/service TS2 (e.g. to describe multi-domain
link). Use of IdRef for X in TS2 is very useful.
So you want to use idRef ONLY for pointers to another document, or also
pointers within the same document?
[...]
I think the difference is in saying "i've created a new element right
here with id X" vs. "i'm referencing an element with id X that is
defined elsewhere". I think this is where it dovetails with inheritence.
It's basically letting people know "i'm defining 0 or more attributes
about this element, but you need to go elsewhere to find the rest of the
attributes".
So how to put this info into RDF? Remember, there is no id/idRef in RDF.
I previously proposed something along the lines of:
urn:ogf:network:example.net:2012:somepointer nml:isauthoritative "False"
but that got rejected, since "authority" was not the correct wording.
Could either of you come up with a better proposal or wording?