Jay,
In an instance like this, where a spec appears to have been inactive
for a few months, I posit that the correct thing to directly approach
the current listed editor of the spec requesting to take over the role
of active editor, or that they attend to open issues.
In this case the editors are Tantek and Rohit.
We have no formal process for taking responsibility for specs, so
simply proceed with good manners.
As editor, you are responsible for following The Process in moving
forward the spec, and responding to issues raised on hlisting-issues.
In the case of hListing, you also need to remember that although
hListing is a draft, it's a specification with a lot of real-world
adoption. Much of the schema is reinforced by actual implementations
and so it is not infinitely flexible. You have to ensure that issues
are resolved with that in mind.
Rohit,
On 3 Nov 2009, at 13:39, [email protected] wrote:
Feel free :) it's a versioned wiki, just be clear about authorship
(as a long-ago contributor to hlisting)
If you're a ‘long-ago contributor’ rather than active editor, please
update the hListing page and move your name from ‘Editors’ to
‘Contributors’. Such gardening helps for these kinds of situations and
contacting the right people.
Thanks,
Ben
------Original Message------
From: Jay Myers
Sender: [email protected]
To: [email protected]
ReplyTo: Microformats Discuss
Subject: [uf-discuss] Process for changes to pre-existing draft
formats?
Sent: Nov 3, 2009 1:15 PM
All,
Several months ago I posted some proposed changes to the
hListing microformat out on the hlisting-brainstorming
(http://microformats.org/wiki/hlisting-brainstorming) page
of the wiki. I am just now revisiting this and would like
to advance this work and incorporate it into the current
hListing draft, but want to do it in a way that would
adhere to the process. However, I don't see much in the
process documentation around changing pre-existing formats
in draft, and would hate to alter the original hListing
draft without some consensus.
Could someone point me in the right direction on this?
Thanks,
Jay Myers
e: [email protected]
b: http://jay.beweep.com
t: @jaymyers
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
Sent via BlackBerry by AT&T
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
