SourceForge : artf6555: Non-authoritative statements

Project: NML-WG Trackers > Schema Progress > View Artifact

Artifact artf6555 : Non-authoritative statements

Tracker:	Schema Progress
Title:	Non-authoritative statements
Description:	It is useful to include non-authoritative statements in NML messages. For example: "I think that your Port A is the source of my Link A" Currently, this statement is written as: <nml:Link id="urn:ogf:network:provider.com:2012:PortA"> <nml:Relation type="isSource"> <nml:Port idRef="urn:ogf:network:client.net:2012:LinkA"/> </nml:Relation> </nml:Link> There is currently no means to convey that the client is not authoritative for urn:ogf:network:provider.com:2012:PortA. The following 2 proposals can be used to signify authority or non-authority. Proposal 1) XML: The client is authoritative for every element with an "id" attribute. RDF: The client is authoritative for every element mentioned as a subject in a triplet Proposal 2) Add a new "authoritative" property to the NML Network Object. XML: <nml:Port idRef="urn:ogf:network:client.net:2012:PortA"/> <nml:authoritative /> </nml:Port> RDF: urn:ogf:network:client.net:2012:PortA nml:authoritative True .
Submitted By:	Freek Dijkstra
Submitted On:	04/02/2012 10:28 AM EDT
Last Modified:	07/30/2012 7:48 AM EDT
Closed:	07/30/2012 7:48 AM EDT

	Status / Comments		Change Log		Associations		Attachments

Status
Status:*	Duplicate
Category:*	Procedural
Priority: *	4
Assigned To: *	None

Comments

Freek Dijkstra: 07/30/2012 7:48 AM EDT
	Comment:	I'm closing this in favour of artf6583 and artf6553
	Action:	Update Closed set to 07/30/2012 Status changed from Under discussion to Duplicate

Freek Dijkstra: 04/02/2012 10:34 AM EDT

Comment:

I see a problem with proposal A for RDF:

If indeed, the intended proposal 2 for RDF boils down to "The client is authoritative for any Network Object that is the subject of a RDF triplet",
 then the following example is wrong:
 urn:ogf:network:client.net:2012:LinkA a nml:Link .
 urn:ogf:network:client.net:2012:LinkA nml:isSource urn:ogf:network:provider.com:2012:PortA .
 urn:ogf:network:provider.com:2012:PortA a nml:Port .
and the last line must be removed:
 urn:ogf:network:client.net:2012:LinkA a nml:Link .
 urn:ogf:network:client.net:2012:LinkA nml:isSource urn:ogf:network:provider.com:2012:PortA .
This is a change in RDF, and it is no longer possible to explicitly list the type of a referred Network Object.

Action:

Update

Freek Dijkstra: 04/02/2012 10:32 AM EDT

Comment:

A known problem with proposal 1 is that it is not possible to make every statement.

For example, the given statement "I think that your Port A is the source of my Link A" is not possible with an id and idRef at the correct place.

There are two proposals to allow such statements:
artf6553: Allow idRef in parent / allow id in child of a Relation
artf6554: Define all inverse relations

Action:

Update

Freek Dijkstra: 04/02/2012 10:28 AM EDT
	Action:	Create

Return