Posted by linclark.research on June 14, 2011 at 3:21pm
We discussed the user interface for mapping fields to RDF terms. Currently, it requires Evoc for autocomplete functionality, but Evoc only works if the external vocabulary is published correctly.
Stéphane created a module specifically for schema.org that uses a JSON and jQuery autocomplete instead. It would improve the user experience if we extend this to other vocabs as well. We could ensure that current terms are available in the autocomplete by syncing with a JSON service. This would help users because they wouldn't depend on ARC 2 to have autocomplete and they wouldn't have to worry whether the vocab publishes its terms properly.
Plan
- Create a service that offers JSON representations of different vocabs
- Continue Schema.org module, but use the service's JSON file
- Create a semweb_vocabs module in RDFx which depends on RDF UI
- Consolidate RDF schema code into an RDF Terms module (name TBD), removing tables from RDFx install
Action Items
- Incorporate jQuery UI features and RDF UI extensibility — Miles and Stéph
- Document a simple schema.org use case — Ronald and Clay
- Create JSON service — Stéph and Lin

Comments
Documenting a schema.org use case
I have documentation of a simple use case completed along with some screen shots.
Where should I post it?
Ronald will be adding an schema.org introduction along other informative information ;)
Site Building Guide
That's awesome Clay!
I think the best place is in the Site Building Guide, as a child page of the RDF and data interoperability.
Also relates to SEO
That makes sense. It also seems appropriate to be linked from the Search Engine Optimization, also under the Site Building Guide.
I think most people might end up looking for it on the SEO page.
Maybe both pages could link to it?
will add
I'll go ahead and create a child page of RDF and data interoperability.
I'll do so once Ronald and I have everything together.
Child page added
http://drupal.org/node/1194024
Ronald will review and update the page.
Is this what everyone had in mind?
Good start
Thanks Clay. I think screenshots can wait a little until the UI is more stable. The data markup is not ideal but we should be able to add RDFa support in the date module.