In the interests of tidy administration, I'm splitting this thread.
The originally raised and the proposal for including remote content
within microformats are very different issues and it's important that
the original thread stay on track.
Thanks.
On 10 Oct 2007, at 02:59, Michael MD
Sure, just try exporting any contact with a double name from the table found at:
http://www.bo.ingv.it/contents/INGV-Bologna/Staff.html
when added in OS X Address Book such contacts have an empty name;
while exporting them to yahoo contacts works correctly.
...not sure it's an OS X bug though,
On 10/10/07, Ben Ward [EMAIL PROTECTED] wrote:
.. tidy administration .. splitting this thread.
.. including remote content within microformats ..
.. different issues ..
.. important .. stay on track...
Oops. Sorry. =0)
Duncan
___
PS It's then just a small step to allow off-page includes, which is
related to the interlinked hCards on different sites that I was
talking about recently on this list. If anyone can come up with more
real-world use-cases for this type of cross-site uF linkage, I'd be
most grateful.
The microformats community works on the basis of having the data
embedded into the HTML. The RDF/SemWeb approach looks to have a
consistent data model, and then having as many representations as you
like of that data model. The data model for microformats differs based
on which tool you
On Oct 10, 2007, at 4:03 AM, Duncan Cragg wrote:
The microformats community works on the basis of having the data
embedded into the HTML. The RDF/SemWeb approach looks to have a
consistent data model, and then having as many representations as
you
like of that data model. The data model for
I may have come late and missed this - what is this 'common JSON
representation' of which you speak??
It's a hypothetical standard syntax for exchanging microformat
representations, being discussed on the microformats-dev list (as it
would only be used by developers). Just like RDF, it
On Oct 10, 2007, at 9:43 AM, Duncan Cragg wrote:
Now, you made a point of stating that it's only for developers and
being merely syntax and not semantics.
Why is that? If you define hCard in JSON and I get one, I'll know it's
an hCard, surely?
You will, but only because you already know what
