A Uniform Resource Name Namespace for the EPCglobal Electronic Product Code (EPC) and Related Standards
RFC 5134

Note: This ballot was opened for revision 02 and is now closed.

Lars Eggert No Objection

(Bill Fenner; former steering group member) Discuss

Discuss [Treat as non-blocking comment] (2005-06-08 for -)
No email
send info
I would be OK with 2141-style BNF, or ABNF, but not this partial mix.  Some rules are purely abnf:

EPC-URN                 = "urn:epc:" sub-namespace-name ":" sub-namespace

some are a mix (terminals inside <> are BNF, "=" is ABNF):

   sub-namespace-name = <let-num> [ 1*<let-num-hyp> ]
   sub-namespace      = <URN chars>

and some are purely BNF:

   <let-num-hyp> ::= <upper> | <lower> | <number> | "-"

I assume that it's not intentional that the sub-namespace grammar only accepts a single character; presumably it's missing a "1*"

I'd like to see the grammar unified (presumably all using BNF, since that's what 2141 used) before the document moves forward.

In the ABNF for SGTIN-URI, "/" is the proper alternation character; it looks otherwise-valid.

(Jari Arkko; former steering group member) Yes

Yes (2007-11-15)
No email
send info
FYI, ABNF compiles. But there's some duplication in the
different fragments, which I had to take out first before
succeeding. This may be fine, given that they are different
registry entries.

Also, I found the following paragraph a little bit strange:

6.  Community Considerations

   The EPCglobal Architecture Framework is intended to bring the
   Internet to the world of supply chain management and beyond.  It can
   be used to tie physical objects to their virtual descriptions and as
   such has many wide ranging applications for the average Internet use.
   Thus it is very much the intent that this namespace and the entire
   EPCglobal Architecture Framework considers the entire Internet as the
   scope of its community.

I would suggest a rewrite:

6.  Community Considerations

   The EPCglobal Architecture Framework is intended to bring
   Internet applications to the world of supply chain management.
   It can be used to tie physical objects to their virtual
   descriptions and as such has many wide ranging applications.
   The expected users range from parties involved in the supply
   chain, their customers, and so on.

Or perhaps even delete the entire section.

(Lisa Dusseault; former steering group member) Yes

Yes ()
No email
send info

(Mark Townsley; former steering group member) (was No Objection) Yes

Yes ()
No email
send info

(Ted Hardie; former steering group member) Yes

Yes ( for -)
No email
send info

(Brian Carpenter; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Chris Newman; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(Dan Romascanu; former steering group member) No Objection

No Objection ()
No email
send info

(David Kessens; former steering group member) No Objection

No Objection ( for -)
No email
send info

(David Ward; former steering group member) No Objection

No Objection ()
No email
send info

(Magnus Westerlund; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Ron Bonica; former steering group member) No Objection

No Objection ()
No email
send info

(Ross Callon; former steering group member) No Objection

No Objection ()
No email
send info

(Russ Housley; former steering group member) No Objection

No Objection (2005-06-06 for -)
No email
send info
  I did not compile the ABNF, but it seems to me that the following
  is missing:

     <let-num> ::= <upper> | <lower> | <number>

(Scott Hollenbeck; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Tim Polk; former steering group member) No Objection

No Objection ()
No email
send info

(Cullen Jennings; former steering group member) (was No Objection) No Record

No Record ()
No email
send info