Description |
NML elements and attributes are be defined in a NML schema, identified by a IRI.
The general syntax for IRI is defined in RFC 3987. The syntax of IRI for OGF
schema is defined in GFD.084.
The allowed form MUST be:
namespace = common-part [specific-part ] common-part = scheme customs domain
scheme = ( “http” | extension ) “://” customs = “schemas” | extension
domain = “.ggf.org” | “.ogf.org” | extension specific-part = project
version [ project | part ] project = “/” <project acronym>
version = “/” version-year “/” version-month version-year = 4DIGIT
version-month = 2DIGIT
part =“/”token[part]
extension = token
Thus for the NML base schema, this seems to boil down to:
For the base schema:
http://schemas.ogf.org/nml/2012/10/nml
For subordinate schema:
http://schemas.ogf.org/nml/2012/10/ethernet
Proposal 1: Use http://schemas.ogf.org/nml/2012/10/nml
(guaranteed GFD.84 compliant)
Proposal 2: Use http://schemas.ogf.org/nml/2012/10/base
(GFD.84 compliant if one argues that /base is also a "subordinate" schema)
|
NML elements and attributes are be defined in a NML schema, identified by a URI
(or IRI).
The general syntax for IRI is defined in RFC 3987. The syntax of IRI for OGF
schema is defined in GFD.084.
* We will use the same URI for both XML and RDF.
- It is *best practice* to end a XML namespace in a alphanumeric characters,
thus not in "/" or "#", although it is perfectly valid to do so.
- It is *not possible* to end a RDF namespace in a alphanumeric character, and
it is *best practice* to end an RDF namespace in "#", but other punctuation
marks such as "/" are valid too.
- GFD.084 recommends the syntax "http://schemas.ogf.org/nml/2012/10/nml".
Proposal:
For the base schema:
http://schemas.ogf.org/nml/2012/10/base#
For subordinate schema:
http://schemas.ogf.org/nml/2012/10/ethernet#
After publication, we will publish a HTML document at this schema pointing to (a
) the GFD standard, (b) the XML schema and (c) the RDF schema. Pointers are -if
possible- augmented with computer readable (e.g. RDDL ) pointers.
We will pick a date now, so implementations can start using that. Schemas that
are published before the NML-base document is ratified MUST contain a large
warning "DRAFT SCHEMA", but can use these URIs.
|
09/05/2012 6:28 AM EDT |
Freek Dijkstra |
Description |
NML elements and attributes are be defined in a NML schema, identified by a IRI.
The general syntax for IRI is defined in RFC 3987. The syntax of IRI for OGF
schema is defined in GFD.084.
The allowed form MUST be:
namespace = common-part [specific-part ] common-part = scheme customs domain
scheme = ( “http” | extension ) “://” customs = “schemas” | extension
domain = “.ggf.org” | “.ogf.org” | extension specific-part = project
version [ project | part ] project = “/” <project acronym>
version = “/” version-year “/” version-month version-year = 4DIGIT
version-month = 2DIGIT
part =“/”token[part]
extension = token
Thus for the NML base schema, this seems to boil down to:
For the base schema:
http://schemas.ogf.org/nml/2012/10/nml
For subordinate schema:
http://schemas.ogf.org/nml/2012/10/ethernet
|
NML elements and attributes are be defined in a NML schema, identified by a IRI.
The general syntax for IRI is defined in RFC 3987. The syntax of IRI for OGF
schema is defined in GFD.084.
The allowed form MUST be:
namespace = common-part [specific-part ] common-part = scheme customs domain
scheme = ( “http” | extension ) “://” customs = “schemas” | extension
domain = “.ggf.org” | “.ogf.org” | extension specific-part = project
version [ project | part ] project = “/” <project acronym>
version = “/” version-year “/” version-month version-year = 4DIGIT
version-month = 2DIGIT
part =“/”token[part]
extension = token
Thus for the NML base schema, this seems to boil down to:
For the base schema:
http://schemas.ogf.org/nml/2012/10/nml
For subordinate schema:
http://schemas.ogf.org/nml/2012/10/ethernet
Proposal 1: Use http://schemas.ogf.org/nml/2012/10/nml
(guaranteed GFD.84 compliant)
Proposal 2: Use http://schemas.ogf.org/nml/2012/10/base
(GFD.84 compliant if one argues that /base is also a "subordinate" schema)
|
07/13/2012 10:26 AM EDT |
Freek Dijkstra |
Description |
NML elements and attributes are be defined in a NML schema, identified by a IRI.
The general syntax for IRI is defined in RFC 3987. The syntax of IRI for OGF
schema is defined in GFD.084.
The allowed form MUST be:
namespace = common-part [specific-part ] common-part = scheme customs domain
scheme = ( “http” | extension ) “://” customs = “schemas” | extension
domain = “.ggf.org” | “.ogf.org” | extension specific-part = project
version [ project | part ] project = “/” <project acronym>
version = “/” version-year “/” version-month version-year = 4DIGIT
version-month = 2DIGIT
part =“/”token[part]
extension = token
Thus for the NML base schema, this seems to boil down to:
http://schemas.ogf.org/nml/2012/10/nml-base
|
NML elements and attributes are be defined in a NML schema, identified by a IRI.
The general syntax for IRI is defined in RFC 3987. The syntax of IRI for OGF
schema is defined in GFD.084.
The allowed form MUST be:
namespace = common-part [specific-part ] common-part = scheme customs domain
scheme = ( “http” | extension ) “://” customs = “schemas” | extension
domain = “.ggf.org” | “.ogf.org” | extension specific-part = project
version [ project | part ] project = “/” <project acronym>
version = “/” version-year “/” version-month version-year = 4DIGIT
version-month = 2DIGIT
part =“/”token[part]
extension = token
Thus for the NML base schema, this seems to boil down to:
For the base schema:
http://schemas.ogf.org/nml/2012/10/nml
For subordinate schema:
http://schemas.ogf.org/nml/2012/10/ethernet
|
07/13/2012 8:07 AM EDT |
Freek Dijkstra |