Created MRML v3 for SENSE and added new BandwidthService

[jmacauley]

As part of the SENSE project we spawn a new schema version.

Added new BandwidthService to track port capacities and bandwidth utilized by a service.

Closes issue #10.

[xi-yang]

1. Typo: Several occurrences of BandwithService -> should be BandwidthService.

2. capacity had already been defined with domain NetworkObject. It was redefined with domain BandwidthService.

[jmacauley]

BandwithService -> Good catch. Figures I copy the one with the incorrect spelling :-(

The existing capacity definition is:

<!-- http://schemas.ogf.org/mrs/2013/12/topology#capacity -->

<owl:DatatypeProperty rdf:about="http://schemas.ogf.org/mrs/2013/12/topology#capacity">
    <rdfs:domain rdf:resource="http://schemas.ogf.org/nml/2013/03/base#NetworkObject"/>
    <rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
</owl:DatatypeProperty>

Can I remove this one? It is defined as a string instead of a long and is bound to NetworkObject instead of the Bandwidth service. Are you using this definition in any other objects?

[xi-yang]

We used `mrs:capacity` to represent "general" capacity, not limited to network elements. That is why it is a string (with unit embedded). We can either reuse this or add maximumCapacity for BandwidthService.

…

On Aug 2, 2017, at 11:24 AM, John MacAuley ***@***.***> wrote: BandwithService -> Good catch. Figures I copy the one with the incorrect spelling :-( The existing capacity definition is: <!-- http://schemas.ogf.org/mrs/2013/12/topology#capacity --> <owl:DatatypeProperty rdf:about="http://schemas.ogf.org/mrs/2013/12/topology#capacity"> <rdfs:domain rdf:resource="http://schemas.ogf.org/nml/2013/03/base#NetworkObject"/> <rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/> </owl:DatatypeProperty> Can I remove this one? It is defined as a string instead of a long and is bound to NetworkObject instead of the Bandwidth service. Are you using this definition in any other objects? — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#11 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGSnaPHUU196Sq21fg8-VbawqnSFVxkvks5sUJSUgaJpZM4OrJAS>.

[jmacauley]

I am okay with changing "capacity" to "maximumCapacity", however, capacity was also used on the instantiated port to indicate how much capacity that port was using as part of the service. Should I create a "usedCapacity" to identify the capacity used by the service instance?

[xi-yang]

I am fine with adding `usedCapacity`. These attributes are all optional.

…

On Aug 2, 2017, at 12:45 PM, John MacAuley ***@***.***> wrote: I am okay with changing "capacity" to "maximumCapacity", however, capacity was also used on the instantiated port to indicate how much capacity that port was using as part of the service. Should I create a "usedCapacity" to identify the capacity used by the service instance? — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#11 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGSnaPYfct4vbZd3UQtRVBq7j-UnOKg1ks5sUKeOgaJpZM4OrJAS>.

[jmacauley]

I know you like shorter names. Looking at the ones we have now it is possible to shorten them since they are in the context of the BandwidthService:

reservableCapacity == reservable
granularity == granularity
availableCapacity == available
maximumCapacity == maximum
usedCapacity == used
unit == unit

What do you think?

[xi-yang]

These are good in the context of BandwidthService, but could be confusing within the bigger mrs space, unless we expand these attributes to generally apply to other resources and services, and make the `unit' more general as well.

…

On Aug 2, 2017, at 3:17 PM, John MacAuley ***@***.***> wrote: I know you like shorter names. Looking at the ones we have now it is possible to shorten them since they are in the context of the BandwidthService: reservableCapacity == reservable granularity == granularity availableCapacity == available maximumCapacity == maximum usedCapacity == used unit == unit What do you think? — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#11 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGSnaNiPTfJvyby8afKaoxp51XuEt6f9ks5sUMtQgaJpZM4OrJAS>.