Re: [xri] inline schema fragments

[Peter Davis <peter.davis@neustar.biz>]

I personally prefer inline schema... but then, i actually enjoy  
parsing schema... sigh.

=peterd

On May 27, 2009, at 4:34 PM, Will Norris wrote:

> I have a style question for the TC regarding the XRD spec.   
> Currently, the schema section of the spec includes inline schema  
> fragments for each element.  See:
>  http://www.oasis-open.org/apps/org/workgroup/xri/download.php/32686/xrd-1.0-wd01.html
>
> I took my cues on this from the SAML 2.0 spec, which embeds XSD  
> snippets for each element.  I like the fact that it provides the  
> authoritative schema right there alongside each element.  However,  
> it does kind of break the reading flow a bit (especially if the  
> reader is not familiar with RELAX NG), and it can be slightly  
> confusing when the fragments refer to things not yet defined (like  
> the sections for the XRD and Link elements).  Whether the schema  
> fragments are included in the text of the spec or not, we'll still  
> have the authoritative schema document.
>
> So, any feelings one way or the other on embedding the schema  
> fragments in the spec?
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

Peter Davis: NeuStar, Inc.
Director & Distinguished Member of the Technical Staff
45980 Center Oak Plaza Sterling, VA 20166
[T] +1 571 434 5516 [E] peter.davis@neustar.biz [W] http://www.neustar.biz/ 
  [X] xri://@neustar*pdavis [X] xri://=peterd
The information contained in this e-mail message is intended only for  
the use of the recipient(s) named above and may contain confidential  
and/or privileged information. If you are not the intended recipient  
you have received this e-mail message in error and any review,  
dissemination, distribution, or copying of this message is strictly  
prohibited. If you have received this communication in error, please  
notify us immediately and delete the original message.