On Oct 21, 2005, at 6:14 PM, Eric Scheid wrote:
Robert raises a pertinent question regarding pub:control, ie. how
to define
what a "public feed" is for purposes of stripping pub:control.
At the moment, I am really against writing spec language trying to
micromanage who sees pub:control information and who doesn't. There
will be some pub:control with a defined semantic (this is a draft).
There will be other pub:control information that will be proprietary
to sixapart or google or whoever. I agree that in most cases, this
would only be involved in editing operations and would be effectively
one-way clint->server. I can think of all sorts of applications
where you might want to pass this information back downstream to a
client. I can think of no scenarios where doing so would actually
harm interoperability. The implementors will sort it out. So why
should we be trying to write rules and define terms? -Tim
