SourceForge : artf6534: Case in NML objects

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

Artifact artf6534 : Case in NML objects

Tracker:	Schema Progress
Title:	Case in NML objects
Description:	We discussed different casing standards used in different examples. We believe that the following is best: - CamelCase for Classes - lowerCamelCase for attributes See: https://forge.ogf.org/integration/viewcvs/viewcvs.cgi/checkout/201203-schema/case.xml?rev=20&content-type=text% 2Fplain&system=exsy1001&root=nml-examples
Submitted By:	Jeroen van der Ham
Submitted On:	03/14/2012 10:17 AM EDT
Last Modified:	07/11/2012 4:34 PM EDT
Closed:	07/11/2012 4:34 PM EDT

	Status / Comments		Change Log		Associations		Attachments

Status
Status:*	Completed
Category:*	UML schema
Priority: *	4
Assigned To: *	Freek Dijkstra

Comments

Freek Dijkstra: 07/11/2012 4:34 PM EDT
	Action:	Update Closed set to 07/11/2012 Status changed from Need documentation to Completed

Freek Dijkstra: 07/11/2012 7:55 AM EDT
	Action:	Update Status changed from Last Call to Need documentation

Jeroen van der Ham: 03/29/2012 11:37 AM EDT
	Action:	Update Status changed from Under discussion to Last Call

Freek Dijkstra: 03/28/2012 8:51 AM EDT
	Action:	Update Title changed from decide use of case in NML objects to Case in NML objects

Freek Dijkstra: 03/28/2012 3:51 AM EDT

Comment:

Full proposal:

Case in NML objects
===================
https://forge.ogf.org/sf/go/artf6534
https://forge.ogf.org/svn/repos/nml-examples/201203-schema/case.xml (proposal #1) 

Summary: Both XML and RDF are case-sensitive. We should decide on the case convention.

Proposal:
* CamelCase for Objects defined in the NML schema
  (these are usually rendered as XML elements)
* lowerCamelCase for attributes defined in the NML schema
  (these are usually rendered as XML attributes or attribute values)

Example:

<nml:BidirectionalLink id="urn:ogf:network:example.net:2012:between-A-and-B">
    <nml:Link id="urn:ogf:network:example.net:2012:from-A-to-B">
        <nml:capacity units="bps">10000000000</nml:capacity>
        <nml:Relation type="hasSource">
            <nml:Port idRef="urn:ogf:network:example.net:2012:A-egress"/>
        </nml:Relation>
        <nml:Relation type="hasSink">
            <nml:Port idRef="urn:ogf:network:example.net:2012:B-ingress"/>
        </nml:Relation>
    </nml:Link>
    <nml:Link idRef="urn:ogf:network:example.net:2012:from-B-to-A"/>
</nml:BidirectionalLink>

Action:

Update
Assigned To set to Freek Dijkstra
Category changed from Procedural to UML schema
Status changed from New to Work in Progress

Jason Zurawski: 03/27/2012 7:21 PM EDT
	Comment:	This proposal is fine by me.
	Action:	Update

Jeroen van der Ham: 03/14/2012 10:51 AM EDT

Action:

Update
Description changed from

We discussed different casing standards used in different examples. We believe that the following is best:

- CamelCase for Classes
- lowerCamelCase for attributes

We discussed different casing standards used in different examples. We believe that the following is best:

- CamelCase for Classes
- lowerCamelCase for attributes

See: https://forge.ogf.org/integration/viewcvs/viewcvs.cgi/*checkout*/201203-schema/case.xml?rev=20&content-type=text%
2Fplain&system=exsy1001&root=nml-examples

Jeroen van der Ham: 03/14/2012 10:50 AM EDT
	Comment:	see: https://forge.ogf.org/integration/viewcvs/viewcvs.cgi/checkout/201203-schema/case.xml?rev=20&content-type=text%2Fplain&system=exsy1001&root=nml -examples
	Action:	Update

Jeroen van der Ham: 03/14/2012 10:17 AM EDT
	Action:	Create

Return

< Previous

Next >