Hello Jonathan, (This does NOT have anything to do with the Microformats aspect of it, but....)
Just out of curiousity, why the "No Derivative" part for the license for the specification? (To be "open" wouldn't anybody need to be able to make derivatives, and not just one person or more group of people?) Here's a good article on "openness" and "specifications"... http://goland.org/buyingopenstandards (I'd probably go further than this article... but it's a good start.) See ya On 10/26/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
Hi. I've recently soft-launched a distributed identity webapp that I've split out of another project, and released several aspects of that application as open standards ( Creative Commons Attribution-No Derivative Works 2.5 License ) I don't know how / where to submit it for potential consideration as a microformat , or even if they qualify ( one supports human readable , but is geared to be machine readable ; the other is more of an interchange format , but works well as semantic markup ) - so I came here. The summaries: findmeon design: essentially a subset of XML-DSIG with some FOAF / XFN semantics tossed in , and coerced to validate in XHTML strict designed for machine readability , but supports human readability (90% of content would usually be hidden though) unfortunately must support a non-standard 'compressed' url- encoding to let it clear as validated text on several social networks and forum software ( required because certain tags/attributes were often stripped ) usage: openly claim / verify / link multiple websites together via RSA 1024 public key pairings within a distributed self-sufficient framework hopefully will end proprietary 'i own this blog/whatever' codes designed so that resources do not need to know about one another or a central server in order to be linked/verified by a public key originated from: a need to map artist/label/venue/etc information on a music site to official sites / online profiles ; map users of a music site onto other sites for verifiability in trading concert tickets or making online requests / contest entries specification status: the current release works as it should, so any feedback/changes would be merged into a future release open_sn design: a dirty dirty hack standardizes the most common social network / dating site / online account profile fields that do not natively appear in existing specifications its really quite a bad 'standard' -- but it serves its purpose primarily designed as an interchange format, but works pretty well in terms of semantic markup usage: mostly an interchange format for migrating data between accounts specification status: very much open for immediate improvement / replacement. its a dirty dirty hack. The full text / description of both standards are available at http://findmeon.org I'd welcome any feedback. Thanks, // Jonathan Vanasco | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | FindMeOn.com - The cure for Multiple Web Personality Disorder | Web Identity Management and 3D Social Networking | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | RoadSound.com - Tools For Bands, Stuff For Fans | Collaborative Online Management And Syndication Tools | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-- Charles Iliya Krempeaux, B.Sc. charles @ reptile.ca supercanadian @ gmail.com developer weblog: http://ChangeLog.ca/ _______________________________________________ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss