draft #50
isReference & idRef
Status: | submitted | Start date: | 11/30/2012 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% |
|
Category: | - | |||
Target version: | - |
Description
Taken from: https://forge.ogf.org/sf/sfmain/do/go/artf6583
Proposal 1. Introduce the "isReference" parameter to signify that a given Network Object is defined elsewhere and
augmented here.
Discussion: it is yet unclear if "elsewhere" means "elsewhere in this document", "elsewhere in another document", "
defined by another organisation" or some of these.
Proposal 2: Use the following syntax:
XML:
<nml:Link id="urn:ogf:network:example.net:2012:mylink-a-to-b">
<nml:property name="isReference">true</nml:name>
</nml:Link>
which is equivalent to:
<nml:Link idRef="urn:ogf:network:example.net:2012:mylink-a-to-b" />
RDF:
urn:ogf:network:example.net:2012:mylink-a-to-b nmlprop:isReference "true" .
Related issues
History
Updated by Jeroen van der Ham almost 10 years ago
- Priority changed from Normal to Urgent
Updated by Jeroen van der Ham almost 10 years ago
See: http://www.ogf.org/pipermail/nml-wg/2012-October/001179.html
And other discussions at: http://www.ogf.org/pipermail/nml-wg/2012-October/thread.html
Updated by Jeroen van der Ham almost 10 years ago
- Priority changed from Urgent to Normal
This issue is being shelved, possibly for the experimental extension. We require a better use-case and understanding of this issue before we can complete it.
(Other formats not available in this archive.