Hi, I have another question about URNs with query part: The proposed usage of a query part is that it is appended to a URN that identifies a Group, so that the whole uniquely identifies an element within that Group. It is evident that the URN of the Group is a valid URN. My question: is a URN with query part also formally a URN? In other words, do we allow a question mark in all URNs? For example, may I identify my PortGroup with "urn:ogf:network:xyz.org:2012:sdfghjk?x=2"? And if so, I need to write "urn:ogf:network:xyz.org:2012:sdfghjk?x=2?vlan=1719" to identify a Port within this PortGroup? The double question mark seems hideous to me. What about network objects that are identified by a non-URN, but another type of URI. We currently allow this. What solution do we want? 1) Follow Aaron's proposal to abandon the query part altogether, and use a child element in XML. (How would this be used in RDF?) 2) Describe/refer to the regular rules to define query parts in URIs. Thus with ampersands as in "urn:ogf:network:xyz.org:2012:sdfghjk?x=2&vlan=1719" 3) Forbid query parts in all URIs (including URNs) to describe network objects. 4) .... ? Thanks, Freek