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] Reviewing RC1c


Drummond-

All in all, changes were good. I'm a little nervous about the constant references to the metadata document (see below) - as I'm worried that it may *appear* like we are deferring required specification. Maybe we need to have a sentence giving the "line" between whats specified in this doc and whats in the metadata doc and why they are separate. 

Comments below. 

dsr12: The "Note that..." part is confusing - "results from" - what does this mean? 

dsr14: Have you talked about the equivalence of "dot-subsegments" and "reassignable segments" (and "colon-subsegments" and "persistent segments"). It seems like it might be a little confusing if you use them interchangably without having mentioned they are the same thing already. Is it goo dto use two different terms for each type of subsegment? 

dsr18: The rule for interpreting $! (#4 on the second list in sectoin 2.2.4.2) seems odd. If I get handed an XRI, how am I supposed to know how to render it? Are we saying that the only way I can know how to render it is to query some authority? That seems odd to me - you'd like generic processing rules not to differ on a per-authority basis. 

Also, its not clear what "the authority response for this segment" means. Is that the identifier authority for the XRI (if the $! is in the local part), and the identifier authority to the left of the $! if the $! cross reference appears in the identifier authority part? Need to make this more clear. 

dsr22: Whats the principle for whats being discussed in this doc vs the metadata doc w/r/t HFI's and metadata. You've said in a couple of places that "further details will be discussed in the metadata spec", but its not clear to me why these details aren't discussed here - it risks looking like we just ran out of time to discuss all the details and decided to put off discussion in a separate document for convenience sake. 

dsr32: Resolved - yes, it should. This should be quite easy though - insert <Resolved>.example</Resolved>,<Resolved>.home</Resolved>, <Resolved>.base</Resolved> in each of the examples in 3.2.5 after the <IdentifierAuthority xmlns="..."> line in each example. 

As for the "credits" section - still on my plate, but I want to get these comments back to you asap, as I'm thinking figuring out exactly what is required for being in the credits section will take me a bit of time.

	-Gabe


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