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


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

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

Subject: RE: [xri] RE: #next: alternate to #replace

> -----Original Message-----
> From: Scott Cantor [mailto:cantor.2@osu.edu]
> Sent: Friday, September 18, 2009 10:04 AM
> To: 'XRI TC'
> Subject: RE: [xri] RE: #next: alternate to #replace
> But I don't understand this idea that Links don't result in something
> with Type information you would process. Following a link to an XRD should
> result in a new XRD that gets processed according to the semantics of XRD,
> which would include Type selection.

They don't according to our current draft. That's how we got into this discussion. We have a very specific way of processing #see-also directives, that is limited to finding links only when the current context document does not include a sufficient match.

In other words, we currently don't have any processing rule that say "the metadata information about this resource is the ordered sum of all the metadata in all the linked XRD documents". When we designed #see-also we explicitly wanted to avoid that to make implementation easier and more efficient. But that approach left all the <XRD> level elements out of the linked XRDs.


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