W3C home > Mailing lists > Public > public-socialweb@w3.org > April 2015

Re: De-namespace *all stable* microformats and put them in Extended Voc? [was Re: Proposal: de-namespace vcard in the normative AS2 JSON-LD context]

From: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
Date: Tue, 28 Apr 2015 17:17:42 +0200
Message-ID: <553FA496.7060407@wwelves.org>
To: Harry Halpin <hhalpin@w3.org>, public-socialweb@w3.org
Hi Harry,

On 04/28/2015 05:00 PM, Harry Halpin wrote:
> Looking forward to the possibility of using form-encoding in the API,
> maybe it would be useful to de-namespace all stable microformats - which
> TimBL and the W3C agreed it was OK to normatively reference in W3C specs
> - and put them in the ActivityStreams Vocabulary?
> 
> Does that make sense?
IMO it does NOT make sense! microformats.org should publish URIs for
their terms and maintain that vocabulary. We could possibly add extended
documentation on their usage in Social Web context whenever needed in
https://github.com/w3c-social/social-vocab

BTW Did you check you idea with Tantek and other people in Microformats
community?

Once again we should look at
ISSUE-36: Role and evolution of recommended JSON-LD @contexts
https://www.w3.org/Social/track/issues/36

IMO it plays bigger role than in many ways not needed AS2.0 Extended
Vocabulary. Also all the 'de-namespacing' happens in normative JSON-LD
@context, not in the AS2.0 vocab!

> 
> Then, rather than vCard, we'd also just have hCard/vCard (although a
> quick double-check to make sure they line-up 100% is in order.
I think we should decide which URI's we map to in context and only add
there a single term without namespace for single purpose.

e.g. we should NOT add both

* n - vcard:n
* name - mf2:p-name

also family-name can map to only one of the URIs
* vcard:family-name
* mf2:p-family-name

also naming above doesn't follow pattern currently used in AS2.0 vocab,
which follows RDF vocabularies best practice for naming
properties/predicates:

familyName (NOT family-name or family_name)

again JSON-LD @context can very easily map

"familyName": "vcard:family-name"

*or*

"familyName": "mf2:p-family-name"


cheers!
Received on Tuesday, 28 April 2015 15:17:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:26:17 UTC