[repost of private mail to list]
> We're having a hackfest some time in the new year, though, and I will
> try and make this a priority, as a single point of entry/search for
> OpenGuides is indeed quite important.
Excellent :) It is quite a change from the distributed approach you've
taken so far.
> We tend to export mostly in RDF format with geo namespaces; is this
> likely to be useful? (see the RDF format search on one of the existing
> guides for an example).
RDF sounds fine (XML format), what about the return path, say you've got
WhereAmI (my app) on your phone, you've identified your location with
GPS or GSM CellID, downloaded the map around you, listed the openguides
locations, picked your pub for lunch, routed to it, had a meal, but
found an error in the guide, what is the desired return path? Would it
make sense to have a 'comment' option where you just describe the change
to the entry, then next time someone on the web views that article they
see the suggestion, and can edit the article according to the
suggestion, this would then archive the comment. Or we could go for
allowing editing of the entire article on the phone and then upload the
new version.
I presume that with your distributed architecture you have independant
user accounts on each site, what about supporting openid? or something
else? to let remote users authenticate their changes.
Cheers,
Adam.