OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xri-editors message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [xri-editors] Proposed revised outline

I guess this is good an outline as any.

The only concern I have is that the "resolution" in RFC2396 is a completley different beast. That section talks about resolving *relative* URIs, which is primarily syntactic.

I'm concerned that by mirroring the structure of the rfc2396 doc, we may be suggesting parallels that don't exist (that our definition of resolution, for example, is related in some meaningful way to the relative resolution part of rfc2396). 

Also, I'm not sure that we have stuff to say about "usage" as the term is used in RFC2396. 

In other words, while the outline looks fine, I'm not sure that its any more than superficially in line with rfc2396bis. I'd reorder Normalization and Comparison to come right after Syntax Components and be really clear about what a "usage" section involves, and be sure we need it.


> -----Original Message-----
> From: Drummond Reed [mailto:drummond.reed@onename.com]
> Sent: Wednesday, June 18, 2003 1:21 AM
> To: xri-editors@lists.oasis-open.org
> Subject: [xri-editors] Proposed revised outline
> It's way past my bedtime but since I got so little spec work 
> done today,
> I want to at least post these key thoughts about the new document
> structure.
> My key hypothesis is that by separating the docs into a tech 
> spec and a
> non-normative primer, we free ourselves in the tech spec to follow RFC
> 2396 and 2396bis format very closely. That way the spec will look very
> familiar to most Webbies, and it will be easy to see where it 
> builds on
> 2396 concepts.
> If you agree, then below is a revised proposed outline for the tech
> spec, based on 2396bis organization. Note that I've included subheads
> only under Introduction. I'd propose we use as many of the subheads in
> 2396bis as make sense, i.e., for all practical purposes use it as a
> template with exceptions for the subject matter differences and the
> OASIS vs. IETF formatting differences.
> (If you just want to review the 2396bis outline directly, it's at the
> start of the doc at
> http://www.apache.org/~fielding/uri/rev-2002/rfc2396bis.html
> <http://www.apache.org/~fielding/uri/rev-2002/rfc2396bis.html> ).
> Please do post your thoughts positive or negative on this ASAP as I'm
> going to be starting on my drafting tomorrow.
> =Drummond 
> Introduction
>   - Overview of XRIs  
>   - Design Considerations
>   - Syntax Notations
> Characters
> Syntax Components
> Usage
> Resolution
> Normalization and Comparison
> Security and Data Protection Considerations
> Acknowledgements
> Appendices
>   - Normative BNF
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xri-editors-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: xri-editors-help@lists.oasis-open.org

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]