A Uniform Resource Name Namespace for the EPCglobal Electronic Product Code (EPC) and Related Standards
draft-mealling-epc-urn-02
Discuss
Yes
(Lisa Dusseault)
(Mark Townsley)
(Ted Hardie)
No Objection
(Brian Carpenter)
(Chris Newman)
(Dan Romascanu)
(David Kessens)
(David Ward)
(Lars Eggert)
(Magnus Westerlund)
(Ron Bonica)
(Ross Callon)
(Scott Hollenbeck)
(Tim Polk)
No Record
(Cullen Jennings)
Note: This ballot was opened for revision 02 and is now closed.
Bill Fenner Former IESG member
Discuss
Discuss
[Treat as non-blocking comment]
(2005-06-08)
Unknown
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 IESG member
Yes
Yes
(2007-11-15)
Unknown
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 IESG member
Yes
Yes
()
Unknown
Mark Townsley Former IESG member
(was No Objection)
Yes
Yes
()
Unknown
Ted Hardie Former IESG member
Yes
Yes
()
Unknown
Brian Carpenter Former IESG member
No Objection
No Objection
()
Unknown
Chris Newman Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Dan Romascanu Former IESG member
No Objection
No Objection
()
Unknown
David Kessens Former IESG member
No Objection
No Objection
()
Unknown
David Ward Former IESG member
No Objection
No Objection
()
Unknown
Lars Eggert Former IESG member
No Objection
No Objection
()
Unknown
Magnus Westerlund Former IESG member
No Objection
No Objection
()
Unknown
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Ross Callon Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
(2005-06-06)
Unknown
I did not compile the ABNF, but it seems to me that the following
is missing:
<let-num> ::= <upper> | <lower> | <number>
Scott Hollenbeck Former IESG member
No Objection
No Objection
()
Unknown
Tim Polk Former IESG member
No Objection
No Objection
()
Unknown
Cullen Jennings Former IESG member
(was No Objection)
No Record
No Record
()
Unknown