- markup (52)
- xml (7)
- xslt (21)
- atom (8)
- overlapping markup (2)
- schema (9)
- creole (4)
- xforms (1)
- pipelines (7)
- coding (2)
- dtll (1)
- genealogy (3)
- gtd (1)
- hardware (1)
- legislation (1)
- ontologies (2)
- unicode (1)
- web (24)
- google (3)
- rdf (6)
- rest (3)
- wikis (1)
- work (1)
- xpath (1)
- xquery (1)
- xtech2008 (3)
- life (26)
- children (5)
- equality (6)
- environment (4)
- gadgets (5)
- software (3)
- xlinq (2)
- conferences (7)
- xtech (6)
- blog (7)
- drupal (3)
Re: RDFa, sure, but now?
Before you decide on meta data instantiation; ask yourself ‘whom is going to consume this data’….if u find that in your internal Process there are going to be internal consumers of this data, try to identify integration routes and correlate which approach would be best. Same thing goes for external consumers of metadata.
The next issue, is what will happen when this meta data is let out ‘into the wild’ e.g. with respect to search engines, other applications gleaning information from it….it will be relatively easy to reconfigure your meta data format (e.g. RDFa or GRDDL), the problem will be what to do with cached assumptions. I would propose you plan for multiple meta data formats.
gl, Jim Fuller