* Include support for services that require more than one microformat.

* Include support for services that require more than one microformat.

* Include support for semantic content other than microformats (RDF, RDFa, eRDF)

* Include support for semantic content other than microformats (RDF, RDFa, eRDF)

-

* Should be very identifier prepended by a "microformat" prefix to avoid collisions (e.g. microformat.hCard.adr)?

+

* Should every identifier be prepended by a "microformat" prefix to avoid collisions (e.g. microformat.hCard.adr)?

= OpenService extension to describe Operator User Scripts =

= OpenService extension to describe Operator User Scripts =

Revision as of 22:35, 28 April 2008

To increase the value of web content annotated with microformats (or other semantic web technologies) it is required to define a language that can be used by web applications to describe and publish their services available for different semantic contents (e.g. for a hCard).

OpenService description includes the concept of context which is used to describe the content this service can be applied to. The possible contexts included in the original OpenService specification are selection, document and link.
This specification extends the possible contexts to include microformats. The value used must be the standard microformat name as defined in microformats.org (e.g. hCard, hCalendar, tag). To indicate a required parent for the microformat a dotted notation can be used (e.g. hCard.adr indicates an addr content that must be child of a hCard content)

Other required extension is new variables that can be used to compose the url parameters that will be sent to the service. These new variables include the microformats' properties:

The name of the variables must be the standard property name as defined in microformats.org and prepended by the microformat name to avoid collisions (hCard.fn, hCalendar.location, tag).

The value of the variable must be the value of the microformat's property.

If the property is a composed property.... TBD

If more than one instance of the property is found (plural properties), they must be included separated by commas.

All variables are treated as required unless it the modifier "?". An optional variable that cannot be resolved is treated as an empty string for an inline parameterized URL. In a form-based parameterized URL the entire parameter element is ignored.