[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xri] XRD Type and Path specification
To close on this thread, the following was
recorded in the minutes of the 2006/05/25 TC telecon: * We discussed Wil's
proposal in http://lists.oasis-open.org/archives/xri/200605/msg00033.html
to add support for wildcard matching. The conclusion was that we will emulate
HTTP Accept headers and add * wildcard parameter support in the QXRI input
parameter. However we will not support publishing wildcards in
the value of a MediaType element in an XRD because the server needs to be more
explicit about what it supports. =Drummond From: Tan, William
[mailto:William.Tan@neustar.biz] Hi folks, We do not seem to mention what normal form should the value
of Type and Path elements be. I would normally prefer XRI-normal form since there is no
issue with XML, but because of the following reasons:
I suggest putting a SHOULD/MUST for URI-normal form. Also, with regards to path matching rules, I’d like to
clarify what I understand from the spec:. E.g. <Path>(+foo)</Path> QXRI: xri://@a/+foo/bar We try:
QXRI: xri://@a/(+foo)/bar We try:
QXRI: xri://@a/(+foo/bar) We try:
Are these processing steps correct? =wil (http://xri.net/=wil) |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]