[Nml-wg] References

[Roman Łapacz]

W dniu 2012-10-05 16:06, Jeroen van der Ham pisze:
> Yes indeed.
> Freek is now out of the running, so it is up to us to finalize things and close this issue.
>
> Summarizing:
> - "isReference <URL>" solution is off the table, this is a control-plane construct, I'm proposing to move this to NSI topology constructs, so this will be an NSI issue.

fine by me

> - id/idRef solution seems to boil down to extra parser logic, i.e. whether or not an id is defined in some place or not.
>
> For the RDF/OWL syntax this is a non-issue, because statements about objects can be made everywhere.
> In my opinion this should also hold true for the XML syntax. You can not stop me from stating properties of a certain object, therefore, you can not state that a certain definition is only in one place.
>
> Also, how do we enforce the id / idRef construct? What to do when you encounter an id statement in two different places?

I see it simple: multiple use of the same id would be for adding new 
information/properties of the same element (for example, if the are two 
elements in one or two different locations with the same id they form 
just one object). This requires unique ids and assumption that ids are 
correctly assigned to elements.

IdRef  would be used only for references (no definition inside).

Roman



>
> Jeroen.
>
>
>
> On 5 Oct 2012, at 12:12, Roman Łapacz <romradz at man.poznan.pl> wrote:
>
>> Correct me if I'm wrong but I think that the references issue could be the last major one to solve and announce the first stable official version of NML. Other issues could be discussed afterwards and belong to the next version (I remember that October has been a deadline).
>>
>> Roman
>>
>>
>> W dniu 2012-09-20 17:13, Jeroen van der Ham pisze:
>>> Hi,
>>>
>>> We've been discussing references, meaning things that are not defined locally, but you do want to provide additional information about them. For XML there has been a proposal to use id / idRef to denote something like that. Unfortunately it is not very easy to port that construct to RDF/OWL.
>>> The only way to express something like that in RDF/OWL is by using a relation. Fortunately a relation like that already exists in the form of rdfs:isDefinedBy. This states that an object is actually defined by another description, and conveniently provides the URL of that description to reference it.
>>>
>>> Could we perhaps use the isDefinedBy construct also in XML to make the reference definition somewhat more explicit? This would really help keeping the difference between the two syntaxes at a minimum also.
>>>
>>> Jeroen.
>>>
>>> _______________________________________________
>>> nml-wg mailing list
>>> nml-wg at ogf.org
>>> https://www.ogf.org/mailman/listinfo/nml-wg
>> _______________________________________________
>> nml-wg mailing list
>> nml-wg at ogf.org
>> https://www.ogf.org/mailman/listinfo/nml-wg