[uf-discuss] XMDP inclusions
bigsmoke at gmail.com
Sat May 20 03:56:27 PDT 2006
Is there any progress on (recursively) including XMDP profiles?
From the Wiki I gather:
INCLUDES / AGGREGATE PROFILES 
Methods for including one or more values, properties, or an entire
XMDP into an other XMDP as a way of creating an aggregate profile that
effectively contains definitions from multiple profiles would be quite
useful. They would enable documents with microformats to simply refer
to a single profile URL rather than a complete space separated set of
all the profile URLs of the microformats that may be in use.
* update XMDP with new required features:
o ability for one profile to include/import another (rel="import" ?)
o ability to reference an XMDP via rel="profile" (similar to
XHTML2 rel value by same name)
o ability/suggestion to reference an XMDP using <a href> in
addition to <link>
But, I'm wondering: do we even need anything new? Can the GRDDL
profile, for example, not already be specified in the profile
attribute of a document's XMDP profile?
This requires an example: our document conforms to RDF Site Summaries
 and has its profile set to .
 is an XMDP profile document that has  as its profile and with a
profileTransformation rel set up. If 's profileTransformation
applies to our document, doesn't 's data-view profile  also
apply to our document?
My question, then, is: is this an exception, or could this simply be
extended to a rule? This rule could say: The profile of our document's
profile also applies to our document. As a side effect, this rule
_might_ obliterate the need for the profileTransformation rel value.
I'm wondering if there's anything that would actually be broken by
adding such a rule to XMDP... There probably is, but I need this idea
to be shot down _properly_ before I can get it out of my head ;-)
Thanks for reading this,
Morality is usually taught by the immoral.
More information about the microformats-discuss