object identifier
=================

schema:
http://ogf.org/schema/nml/base/20101025


Freek will check wil Joel the syntax of the object identifier namespace
(see GFD 84)
Jason has better idea, will put that forward as counter proposal


instance identifier
===================

<nml:link>urn:ogf:network:domain.name:2143567</nml:link>
<nml:port>urn:ogf:network:domain.name:2143567</nml:port>
NOT allowed

No additional length restrictions on urns

colons CAN be used in opaque part

opaque part is unique within the given domain

RFC 2141 / RFC 3986 / RFC 3987

"urn:ogf:network:" will be used as prefix
Long: not a problem
Not a problem that it is in urn:ogf namespace


references
==========

id = ....
idRef = 

NOT using the build-in XML schema ref-id(?) since that can only be used within a document

Questions
=========

Question 1. Should the schema end with a / or #?
a) http://schemas.ogf.org/nml/base/2013/10   (common for XML)
b) http://schemas.ogf.org/nml/base/2013/10/  (current proposal)
c) http://schemas.ogf.org/nml/base/2013/10#  (common for RDF)

Freek:  b, c
Jeroen: b
Jason:  b


Question 2b. What attribute to use for references in XML?
a) id and idref in NM-WG namespace
b) id and idref in NML base namespace
c) id and idref in NML Ethernet namespace
d) id and idref in new (OGF) namespace (created for just these attribs)
e) about and resource in RDF namespace

Freek:  a, d, e
Jeroen: b
Jason:  c


Question 3. What characters are allowed in <opaque string>?
a) GLIF:       A-Z a-z 0-9 - .
b) unreserved: A-Z a-z 0-9 - . _ ~
c) RFC2141:    A-Z a-z 0-9 - . _ ( ) + , : = @ ; $ ! * ' %hex
d) RFC2141bis: A-Z a-z 0-9 - . _ ~ ( ) + , : = @ ; $ ! * ' & %hex

Freek:  d, c
Jeroen: c
Jason:  ?


Question 4. MUST all object have an id?
a) All Network Objects MUST have an identifier.
b) All Network Objects SHOULD have an identifier.

Freek:  a (was: b)
Jeroen: b
Jason:  a


Question 5. MUST urn:ogf:network syntax be used?
a) All identifiers MUST follow the urn:ogf:network syntax
b) All identifiers MUST be a URI, and SHOULD follow the urn:ogf:network syntax
c) All identifiers MUST be a unique, and MAY follow the urn:ogf:network syntax
(some more variants are possible)

Freek:  c (was: b)
Jeroen: c
Jason:  ?