Useful breakdown of same key factors in the use of Health Documents v. Health Messages by John Moehrke:
 Healthcare Security/Privacy: Critical aspects of Documents vs Messages or Elements
Healthcare Security/Privacy. Discussions of Privacy and Security in Healthcare by John Moehrke. Topics: Consent, Access Control, Audit Control, Accounting of Disclosures, Identity, Authorization, Auth...
|
Thursday, October 27, 2011
Health Documents v. Health Messages or Elements
Michael Geist on Canada's National Digital Strategy
Canada's National Digital Strategy: Hidden in Plain Sight
Earlier this month, I had the pleasure of delivering a keynote address at the Cybera Summit in Banff, Alberta. The conference focused on a wide range of cutting edge technology and network issues. My opening keynote discussed Canada digital economy legal strategy. While the formal digital strategy has yet to be revealed, I argued that the digital economy legal strategy is largely set with legislative plans touching on lawful access, privacy, online marketing, and copyright. 
youtube.com - 2011 Cybera Summit introductory keynote by Michael Geist, Law Professor and Canada Research Chair in Internet and E-commerce Law at the University of Ottawa.
|
Electrolux Bio Robot Refrigerator
Thursday, October 13, 2011
Curate something!
So, here's an idea: curate something. Anything. In my case, due to an odd concatenation of circumstances, I have taken it upon myself to curate stories about people and their refrigerators. This activity consists of periodically querying Google+ and Twitter and the www at large for a single word, and republishing anything particularly exciting or funny this turns up. A single word. That's all. I suppose I label the post for posterity as well. Try it. Curate something.
Originally posted on Google+ by Adam J. Cohen:
Originally posted on Google+ by Adam J. Cohen:
Tuesday, October 11, 2011
Haha! Defiantly so!
via +Joseph Lee, via +Wil Wheaton on Google+
We all know Oreos are delicious, but did you know they make a great canvas for cameos? Dating as far back as 332 BC, cameos are defined by contrast, usually with a raised light relief against a dark intaglio, which serves as a dark backdrop. With that in mind, Oreo's most defiantly fit the bill and is another example of food too good to eat. Check out Judith G. Klausner's page for more examples of her art!  |
Friday, October 07, 2011
Goodreads: recommended reading by Northrop Frye
The Bush Garden: Essays on the Canadian Imagination by Northrop FryeMy rating: 4 of 5 stars
I read this book quite a long time ago as part of a course on CanLit and poetry. I love the way Frye uses language to express ideas, and ideas to create/curate identity... and rereading this book makes me want to go back and reread Anatomy of Criticism and Fearful Symmetry, as well as works by Atwood, McLuhan, Innis, Lampman, Birney etc etc... if you are Canadian and you like poetry, you should read this book because it might introduce you to a previous generation of Canadian romanticism or a previous previous generation of Canadian classicism.
View all my reviews
Ada Lovelace Day 2011
Ada Lovelace day: in my little XML corner of the world, I have learned more than I could possibly mention from +Eve Maler , +Jeni Tennison , Priscilla Walmsley and +Lauren Wood.
Many thanks to all! |
Thursday, October 06, 2011
This animated presentation by Dan Pink is...
This animated presentation by Dan Pink is easily the coolest thing I have seen so far today (via +John Moehrke) on the nature of work, purpose and incentive.
Healthcare Security/Privacy: Standards work is motivating because it gets used and improves lives
Healthcare Security/Privacy. Discussions of Privacy and Security in Healthcare by John Moehrke. Topics: Consent, Access Control, Audit Control, Accounting of Disclosures, Identity, Authorization, Auth...
|
Monday, October 03, 2011
Neal Stephenson - Innovation Starvation
Neal Stephenson on society's failure to mobilize to "get big stuff done":
"Today's belief in ineluctable certainty is the true innovation-killer of our age."
Or in other words, blame Google, since a quick search for a solution to a problem demonstrates either, apparently, that it can't be solved, or that it already has been solved, occluding the possibility that it may not have been solved adequately, and it may not have been solved recently.
"Today's belief in ineluctable certainty is the true innovation-killer of our age."
Or in other words, blame Google, since a quick search for a solution to a problem demonstrates either, apparently, that it can't be solved, or that it already has been solved, occluding the possibility that it may not have been solved adequately, and it may not have been solved recently.
Friday, September 09, 2011
Structured Product Labeling...
I am currently reading about SPL (Structured Product Labeling), an XML-based standard used in the pharmaceutical industry, engineered to reduce pharmaceutical error.  The SPL Standard, DailyMed, and the Consumer – DCLnews BlogBy DCL's Vincent B. Donadio, Editorial Contributions from DCL's Howard Shatz In 2005, the Food and Drug Administration (FDA) implemented an XML-based standard for drug labeling (among other thi... |
One of countless remarkable things about Eno
One of the countless remarkable things about Brian Eno... The Microsoft Sound In 1994, Microsoft corporation designers Mark Malamud and Erik Gavriluk approached Brian Eno to compose music for the Windows 95 project. The result was the six-second start-up music-sound of the Windows 95 operating system, The Microsoft Sound (.wav). In the San Francisco Chronicle he said:[19] The idea came up at the time when I was completely bereft of ideas. I'd been working on my own music for a while and was quite lost, actually. And I really appreciated someone coming along and saying, "Here's a specific problem — solve it." The thing from the agency said, "We want a piece of music that is inspiring, universal, blah- blah, da-da-da, optimistic, futuristic, sentimental, emotional," this whole list of adjectives, and then at the bottom it said "and it must be 31/4 seconds long."  Brian Eno - Wikipedia, the free encyclopediaBrian Eno. Eno at The Long Now Foundation, 26 June 2006. Background information. Birth name, Brian Peter George St. John le Baptiste de la Salle Eno. Born, 15 May 1948 (1948-05-15) (age 63) Woodbridge... |
Thursday, September 08, 2011
Goodreads love for Rohinton Mistry
Tales from Firozsha Baag by Rohinton MistryMy rating: 4 of 5 stars
I have to admit, I've shied away from Mistry's novels due to "not having enough time to read such a big book"... After reading these short stories, I plan to make time for A Fine Balance or one of Mistry's other novels.
View all my reviews
Thursday, August 25, 2011
Use Cases and Test Cases
 Traceability from Use Cases to Test CasesThe article illustrates a formal method of deriving functional test cases from use cases, including how to create a use case, derive all scenarios, and create reasonable test cases, as well as use IBM...  |
This is why I love MulberryTech's xsl-list...
This is why I love MulberryTech's xsl-list: sombody asks a question about an error message during parsing in oXygen using the Saxon 9 parser... and George Bina and Michael Kay respond with an answer, seemingly within moments. xsl-list-digest-subscribe@lists.mulberrytech.com  Consultants specializing in XML Applications for Prose Documents | Mulberry Technologies, Inc.XML and SGML implementation consulting for publishing from Mulberry Technologies, Inc.'s staff: Tonya Gaylord, Debbie Lapeyre, Wendell Piez, B. Tommie Usdin.  |
Tactics for Engagement
A useful set of tactics for engagement with a standard, via Graham Grieve:
 How much should we engage with a standard? « Health Intersections Pty LtdHealth Intersections Pty Ltd. Home. About; Ask me a question about HL7; CDA Tools; Courses. V2 to CDA Mapping Course. Enrolment Form. Roadmap to Blog; Text Display Formats. HL7 v2 FT Type; HTML Colour... |
Tactics for Engagement
A useful set of tactics for engagement with a standard, via Keith Boone:
I have to make up my travel budget annually every December/January. In order to do so, I have to look at the overall strategic picture for standardization, and then pick the tactics that I think I wil... |
Monday, August 22, 2011
Structured Data Website Launch
Structured Data Website Launch (via Gregg Kellogg) A number of Web developers from the RDFa, Microdata and Microformats communities announce the launch of the Structured Data website and community. There are a number of syntaxes for expressing structured data in HTML today: RDFa, Microdata and Microformats. While each syntax has its own parsing rules and data model, the underlying concept among all of them is the same - to express Structured Data in HTML. The Structured Data website (http://structured-data.org/) provides resources to learn about, markup and debug structured data in HTML, including RDFa, Microdata and Microformats. One of the new features, not available anywhere else, is a unified Structured Data Linting Service (http://linter.structured-data.org/), complete with Google Rich Snippets and schema.org examples (http://linter.structured-data.org/examples/) in both Microdata and RDFa format. The Structured Data Linter provides a unified service for verifying and visualizing the structured data contained in web pages, and supports the RDFa and Microdata syntaxes, with Microformats support on the way. At the time of this announcement, the Google and Microsoft testing tools do not support schema.org markup in RDFa or Microdata. The need for such linting service has been expressed many times on the schema.org mailing list and we are happy to announce that the service is now available. Gregg Kellogg has been instrumental in creating the linting service with support from Stéphane Corlosquet. Web developers may now use the linter service to ensure that their schema.org Microdata or RDFa markup is valid. The Structured Data Linting Service is a beta launch and thus contains a number of bugs. That said, we felt that it would be best to get this tool into the hands of the Web developer community. We invite the Web developer community to try it out, report bugs (https://github.com/structured-data/linter/issues), suggest new features (http://groups.google.com/group/structured-data-dev) and contribute new ideas and code. All of the source code is released under a public domain dedication and is available on github (https://github.com/structured-data/). |
 Structured Data on the WebStructured Data on the Web. More and more of the world's data is moving onto the Web. We want to share, re-mix and use this data to build more awesome Web applications. Using structured data techn... |
Thursday, August 18, 2011
Via Health Intersections: Resources For Healthcare
Resources For Healthcare (RFH): Grahame Grieve's proposed response to the HL7 Fresh Look Taskforce, using 37 Signals' uberREST Highrise API as a jumping off point.
RFH defines a RIM-based ontological framework for Resources For Healthcare, based around an exchange, data dictionary and workflow management.
Letter to RFH readers
RFH defines a RIM-based ontological framework for Resources For Healthcare, based around an exchange, data dictionary and workflow management.
Letter to RFH readersLetter to RFH Readers. Grahame Grieve 13-Aug 2011. This specification arose from the remit of the HL7 Fresh Look Taskforce: if HL7 started again from scratch with a new specification, what would a goo...
So, what's important about this? This proposal draws on the HL7 v3 RIM, the Reference Information Model that underlies the HL7 specification. The RIM is a pictorial object model which defines the life cycle of the different messages that comprise the HL7 clinical domains. Because health information is very much workflow based, the RIM-based part is important. moving away from a service architecture towards a REST architecture is indicative of a general shift towards simplicity in the IT industry as a whole.
The timing of this proposal is very much driven by the questions raised by the HL7 Fresh Look taskforce. I recently joked that HL7 v3 is still at a turning point, like one of my son's Choose You Own Adventure books. This screen capture from Graham Grieve's Health Intersections blog recently is perhaps an indication of the signposts facing HL7 v3:
So, what's important about this? This proposal draws on the HL7 v3 RIM, the Reference Information Model that underlies the HL7 specification. The RIM is a pictorial object model which defines the life cycle of the different messages that comprise the HL7 clinical domains. Because health information is very much workflow based, the RIM-based part is important. moving away from a service architecture towards a REST architecture is indicative of a general shift towards simplicity in the IT industry as a whole.
The timing of this proposal is very much driven by the questions raised by the HL7 Fresh Look taskforce. I recently joked that HL7 v3 is still at a turning point, like one of my son's Choose You Own Adventure books. This screen capture from Graham Grieve's Health Intersections blog recently is perhaps an indication of the signposts facing HL7 v3:
Tuesday, August 16, 2011
I'm crossposting this to my personal weblog...
 | I'm crossposting this to my personal weblog for further ingestion. This is partially an experiment in google+... when the article (which I shared to blogspot by email) receives the message, it will post as a draft, since google+ sends blogger (along with the original post here), the credentials I am using to transmit the post...  Question: How to store a CDA document in a relational database « Health Intersections Pty LtdQuestion: How to store a CDA document in a relational database. Posted on August 16, 2011 by Grahame Grieve. 2 commentsLeave a comment. A question (by the ask me a question link above): I am trying to... |
Saturday, August 13, 2011
Can't argue with that...
On Pitchfork, via @camera_obscura_ on Twitter |
 Pitchfork: Watch Neko Case and My Morning Jacket Cover Kenny and Dolly's "Islands in the Stream"With their specific combination of beardedness and hotness, My Morning Jacket's Jim James and Neko Case are kind of ...  |
Wednesday, August 10, 2011
Cross posting from google+ to blogger
Well that's kind of cool... thanks to Rick Klau for the know-how.
Paul Di Filippo reviews a book on identity...
| Piers Hollott shared Piers Hollott's post with you. |
| Piers Hollott Paul Di Filippo reviews a book on identity by Gary Younge (Barnes & Noble)  Second New Review at B&NRI survey a non-fiction item about identity politics: http://bnreview.barn |
 |
Thursday, July 21, 2011
Context+
Here are a couple initial thoughts about Google Plus:
1) I would really like to be able to create some content (like a photo album), and publish this to my circles, using different contexts for different circles. Fine grained, but I think this would be really cool. When you post on your blog, you post photos and then you write a story, and you think the story is the content. But when the post comes up as a result of a google search, it's the pictures - the real content - which you see. With short posts (Twitter, Posterous, Facebook, Google+), it becomes more obvious that what is readily shareable is videos and pictures (my content), not words (my context).
2) Because I can't access Twitter during the work day due to a firewall restriction, I appreciate how several techies I follow collect a week's worth of tweets into "Short Form Fragments" - why couldn't Google+ automatically do this for me, collecting a weeks "stream" into an automatic blogger post? Again, this would be very cool.
1) I would really like to be able to create some content (like a photo album), and publish this to my circles, using different contexts for different circles. Fine grained, but I think this would be really cool. When you post on your blog, you post photos and then you write a story, and you think the story is the content. But when the post comes up as a result of a google search, it's the pictures - the real content - which you see. With short posts (Twitter, Posterous, Facebook, Google+), it becomes more obvious that what is readily shareable is videos and pictures (my content), not words (my context).
2) Because I can't access Twitter during the work day due to a firewall restriction, I appreciate how several techies I follow collect a week's worth of tweets into "Short Form Fragments" - why couldn't Google+ automatically do this for me, collecting a weeks "stream" into an automatic blogger post? Again, this would be very cool.
Friday, July 01, 2011
Canonical Context
The word canon has a literary meaning - in this context, a canon is a set of writing felt by someone to embody and exemplify the norms of those works which are non-canonical. An anti-canon is just a canon appointed by someone else to oppose a hegemonic canon.
In mathematics or informatics, a canonical form is a normative way of expressing or describing an object, so again, a norm created by a group to facilitate sharing of concepts.
In Superman comics, Star Wars books and so forth, "The Canon" refers to the fictional history which is considered (ostensibly by the publishers) as normative by the audience. Other histories may have taken place in alternate realities, parallel storylines and the like, but the canonical events are the ones which "actually" took place, and the chronology within which they are taken to have occurred. Fan fiction, for instance, is non-canonical.
In mathematics or informatics, a canonical form is a normative way of expressing or describing an object, so again, a norm created by a group to facilitate sharing of concepts.
In Superman comics, Star Wars books and so forth, "The Canon" refers to the fictional history which is considered (ostensibly by the publishers) as normative by the audience. Other histories may have taken place in alternate realities, parallel storylines and the like, but the canonical events are the ones which "actually" took place, and the chronology within which they are taken to have occurred. Fan fiction, for instance, is non-canonical.
Thursday, June 30, 2011
Deepening Context and Content (cont)
For instance, here is an application I've talked about before, which one day I would like to build, what I have called a Content Engagement System, though I don't know if I really like this terminology. As with a standard CMS platform, a logged in user would be able to create a textual context, with associated images, video, documents... Within this textual context (which I will start referring to simply as 'context' since this translates roughly as 'with text', right?), another user can identify a phrase, and rather than linking out, the way a standard hyperlink works, link in. Sounds kind of odd, but this is essentially like adding a comment, except the comment is associated back to a phrase within the original context. In HTML terms, this is similar to a link to an anchor within the same page, and in a textbook we would identify this as a footnote.
Okay so far. A blogger posts something, which is then considered canonical, after which anyone else can add footnotes, and these offer an alternative view. A use case then: say I am writing a novel, which is serialized in weekly installments. The math is something like, 1000 words/week = 52,000 words/year, which then gets bundled up into EPUB or PDF and flogged off on Kindle, Smashwords or whatever. The idea is to create demand through serialization, then capitalize on the demand with the actual content.
But, and here's the thing. I want to engage my audience. And but, I want to entertain my audience. And but, a vocal minority within this audience typically demands something edgier; or racier; or, well, smuttier. Which, for the purposes of illustration, let's assume is not really my style. So what I want to provide is the canonical safe version of my novel, and a mechanism, a backstage, which allows the audience created by the canonical story to add (share) their own non-canonical additions to the story, which can then be linked to from within the canonical context as an alternative or supplement. This is similar to a literary parallax (events viewed from multiple vantage points).
More on this at some point. This is an idea I really want to pursue... but it is hard to articulate, so bear with me.
Okay so far. A blogger posts something, which is then considered canonical, after which anyone else can add footnotes, and these offer an alternative view. A use case then: say I am writing a novel, which is serialized in weekly installments. The math is something like, 1000 words/week = 52,000 words/year, which then gets bundled up into EPUB or PDF and flogged off on Kindle, Smashwords or whatever. The idea is to create demand through serialization, then capitalize on the demand with the actual content.
But, and here's the thing. I want to engage my audience. And but, I want to entertain my audience. And but, a vocal minority within this audience typically demands something edgier; or racier; or, well, smuttier. Which, for the purposes of illustration, let's assume is not really my style. So what I want to provide is the canonical safe version of my novel, and a mechanism, a backstage, which allows the audience created by the canonical story to add (share) their own non-canonical additions to the story, which can then be linked to from within the canonical context as an alternative or supplement. This is similar to a literary parallax (events viewed from multiple vantage points).
More on this at some point. This is an idea I really want to pursue... but it is hard to articulate, so bear with me.
Wednesday, June 29, 2011
Deeper Context and Content
I've posted several times now about what I consider the differences between context and content, and why the word "content" kind of annoys me. It's okay, I don't mind being annoyed, and in the right context, content is fine. What I find annoying is that the two terms augment each other, but, so often, one is used when the other is more appropriate. For instance, if I have a web page that you can use to download a PDF of an article I have written, and this web page contains an excerpt of the article - the PDF is the content. Everything on the page, as far as I am concerned, is the context for your act of downloading. Of course, this is important if I am concerned about monetizing, since I have no problem with requiring a specific digital signature or some sort of payment; and I feel that everything else, the context, is like a smile. Why not give this away?
It's quite simple really. People require, create, digest and absorb context. But people like stuff. They like content, because it is something they can grasp onto, whether it's a PDF, an MP3, JPEG, AVI. Something "file-ish." The reason I bring this up, I suppose, is because, well, these things are easy. You can set up a microphone, you can use Prince, DocBook or FOP to turn your words into something more portable in a document format... then you can shade down your context a bit, broaden it, focus attention on the page content. Everything else is really just part of the transmission wrapper. The rest is just part of the vector.
I mean really, is a platform like Blogger or Wordpress actually a Content Management System? No, at best, these are discontent platforms. They separate us from content by masquerading context as content. It's not a bad thing, but I feel it's something we need to move past. You take good pictures, make a commodity out of your pictures. You tell good stories, make a commodity out of your stories. Allow people to focus through the context.
It's quite simple really. People require, create, digest and absorb context. But people like stuff. They like content, because it is something they can grasp onto, whether it's a PDF, an MP3, JPEG, AVI. Something "file-ish." The reason I bring this up, I suppose, is because, well, these things are easy. You can set up a microphone, you can use Prince, DocBook or FOP to turn your words into something more portable in a document format... then you can shade down your context a bit, broaden it, focus attention on the page content. Everything else is really just part of the transmission wrapper. The rest is just part of the vector.
I mean really, is a platform like Blogger or Wordpress actually a Content Management System? No, at best, these are discontent platforms. They separate us from content by masquerading context as content. It's not a bad thing, but I feel it's something we need to move past. You take good pictures, make a commodity out of your pictures. You tell good stories, make a commodity out of your stories. Allow people to focus through the context.
Saturday, January 08, 2011
On The Jungle Planet
Wednesday, September 22, 2010
Ontology of Dream Landscape
A couple things I have been thinking about recently, which come together in this: even dreams typically have a location, but it is a unique quality of dreams, at least the ones I have been having lately, to feature a location in isolation, that is separated from character or context; and: in matters of taxonomy, more than three levels is seldom viable in practical terms, but two is seldom sufficient.
In the work I am currently involved in developing a financial application, I see a three-level vocabulary emerging which I have witnessed in other domains, typified as category, type and subtype.
If I was attempting to describe an ontology of dreams, therefore, I imagine I would use a category of "location", a type of location name or "realm", and a subtype describing each specific "locale" within the realm. So, for instance:
/location/a_forest/one_of_many_paths
What I would like to do is build an API, attached to a cloud storage, to allow people to describe their own dream landscapes in these terms. More on this as it develops. Please comment as you see fit.
In the work I am currently involved in developing a financial application, I see a three-level vocabulary emerging which I have witnessed in other domains, typified as category, type and subtype.
If I was attempting to describe an ontology of dreams, therefore, I imagine I would use a category of "location", a type of location name or "realm", and a subtype describing each specific "locale" within the realm. So, for instance:
/location/a_forest/one_of_many_paths
What I would like to do is build an API, attached to a cloud storage, to allow people to describe their own dream landscapes in these terms. More on this as it develops. Please comment as you see fit.
Friday, August 27, 2010
Context, content and getting over ourselves...
I am a huge fan of Lucas Gonze's weblog, where he wrote something recently which strikes me as quite profound.
What, for that matter, is a Content Management System? The term is a necessary evil; it's not like it is meaningless. But when you use this term to refer to WordPress or Blogger, I get an uneasy feeling, and reading Gonze's comment really cemented for me the reason why. The text on the page in front of you? It's not content. It's context. The page may provide content, but it is itself a context for whatever content it provides.
More on this later, just passing around the lightbulb moment, as it were.
Keep music from the web in the web. Don't go to a music blog, download a track, and then listen in iTunes.Instead, he advocates bookmarking and playing music in the page that contains it, once again returning to fundamental link between URI and resource, between index and content.
What, for that matter, is a Content Management System? The term is a necessary evil; it's not like it is meaningless. But when you use this term to refer to WordPress or Blogger, I get an uneasy feeling, and reading Gonze's comment really cemented for me the reason why. The text on the page in front of you? It's not content. It's context. The page may provide content, but it is itself a context for whatever content it provides.
More on this later, just passing around the lightbulb moment, as it were.
Wednesday, August 25, 2010
Abie and Rondo Redux
Sorry, broke the link in the last post. A better title would be "The Adventures of Abie and Rondo..." And this link should work.
Saturday, August 14, 2010
Abie and Rondo
Abie and Rondo is a serialization of children's adventures I am writing for Web Serial Writing Month this year. The premise is simple: brother and sister team Abie and Rondo travel to remote locations to right the world's wrongs. Irony abounds, and good times are had. I have recently added truly awful vector art courtesy of yours truly, along with pithy captions.
More than anything else, this is an experiment to see how much I can accomplish with very little effort, using the tools at hand (Blogger) without a great deal of modification (JavaScript hijacking the page layout). When WeSeWriMo is over, I will summarize my experience in some sort of "lessons learned" post.
Enjoy.
More than anything else, this is an experiment to see how much I can accomplish with very little effort, using the tools at hand (Blogger) without a great deal of modification (JavaScript hijacking the page layout). When WeSeWriMo is over, I will summarize my experience in some sort of "lessons learned" post.
Enjoy.
Wednesday, May 26, 2010
Because it's a while since I've 'blogged about Identi.ca...
Here's an idea: SourceForge is connected with a great community of open source developers; Twitter is connected with a great community of individuals, some of whom are open source developers. One of the great value propositions for me for Twitter is that rather than following an open source project, I can follow the projects creators, and receive timely information about updates, patches and the like... as long as I am actually logged into a Twitter client when the update in question is pushed out. There is a lot of noise.
Yammer is great for organizational transparency, or so I've heard from people who are using it, but it's a walled garden - I wonder what would happen if a similar approach were taken with an open source repository like SourceForge? What if an open source status network like laconi.ca were hosted and synchronized with the group of individuals with SourceForge projects? Then you could follow this entire list or a segment of this list, and get updates in a timely fashion without the background noise, or aggregate this stream into the broader stream that you might normally follow.
Might inject a bit of life into the open source community as well.
Yammer is great for organizational transparency, or so I've heard from people who are using it, but it's a walled garden - I wonder what would happen if a similar approach were taken with an open source repository like SourceForge? What if an open source status network like laconi.ca were hosted and synchronized with the group of individuals with SourceForge projects? Then you could follow this entire list or a segment of this list, and get updates in a timely fashion without the background noise, or aggregate this stream into the broader stream that you might normally follow.
Might inject a bit of life into the open source community as well.
Saturday, May 15, 2010
The other side of transparency
Really quick, I just wanted to jump in and say, with regards to Facebook privacy, there is another situation that I have yet to see adequately described. The situation I am seeing described is when you publish a piece of yourself, and it goes further afield than you anticipated, ie you share photos with someone with whom you had no intention of sharing.
But consider the obverse situation, when you publish a piece of yourself to your social circle, and it is withheld for some reason from a portion of this circle because of a change in privacy setting, or confusion about the impact of the privacy settings you have selected.
In many ways, this may create more distrust in the platform, when someone in your social circle feels slighted because they did not receive the expected update. Of course, this happens with email spam filters as well as social network privacy settings. In either case, it creates an atmosphere of distrust in the platform.
But consider the obverse situation, when you publish a piece of yourself to your social circle, and it is withheld for some reason from a portion of this circle because of a change in privacy setting, or confusion about the impact of the privacy settings you have selected.
In many ways, this may create more distrust in the platform, when someone in your social circle feels slighted because they did not receive the expected update. Of course, this happens with email spam filters as well as social network privacy settings. In either case, it creates an atmosphere of distrust in the platform.
Friday, May 14, 2010
Tab Sweep - 2010 05 14
Dare Obasanjo on Facebook:
Facebook’s Open Graph Protocol from a Web Developer’s Perspective
danah boyd on Facebook:
Facebook and "radical transparency" (a rant)
Not surprising that Facebook is facing criticism; I appreciate danah's demonization of transparency, and the distinction she draws between being exposed and exposing oneself. One of the things I appreciate about Twitter is that the level of exposure of any conversation I have there is dictated directly by the object graph of those involved in the conversation. If I want to curse and swear, I can engage someone in a conversation with whom this is appropriate. But there is always a risk of exposure.
Dare's point is also well taken on many levels, but particularly from my viewpoint, ontologically speaking, that Facebook is leveraging RDFa and not microformats, and that RDFa is an exponentially more robust technology specifically due to the use of namespaces. And what better way to identify arbitrary URIs as social objects than by using namespaces? In issues of transparency and privacy, it seems that disambiguation, ie clarification of social context will become increasingly important.
Reread danah's rant, especially the Zuckerburg quotes referring to the artificiality of sustaining a multiple identity. My own reaction to this is equally violent, and I call BS - all relationships in a social graph are virtualizations or supplementation of something that they are not, actual relationships. They are by definition artificial and demand disambiguation.
My travels in Flex-land keep coming back to the importance of namespaces outside the strict context of XML. Their time is coming; more widespread use of RDFa and the need for disambiguated rather than radical transparency are definitely indicative of this.
Facebook’s Open Graph Protocol from a Web Developer’s Perspective
danah boyd on Facebook:
Facebook and "radical transparency" (a rant)
Not surprising that Facebook is facing criticism; I appreciate danah's demonization of transparency, and the distinction she draws between being exposed and exposing oneself. One of the things I appreciate about Twitter is that the level of exposure of any conversation I have there is dictated directly by the object graph of those involved in the conversation. If I want to curse and swear, I can engage someone in a conversation with whom this is appropriate. But there is always a risk of exposure.
Dare's point is also well taken on many levels, but particularly from my viewpoint, ontologically speaking, that Facebook is leveraging RDFa and not microformats, and that RDFa is an exponentially more robust technology specifically due to the use of namespaces. And what better way to identify arbitrary URIs as social objects than by using namespaces? In issues of transparency and privacy, it seems that disambiguation, ie clarification of social context will become increasingly important.
Reread danah's rant, especially the Zuckerburg quotes referring to the artificiality of sustaining a multiple identity. My own reaction to this is equally violent, and I call BS - all relationships in a social graph are virtualizations or supplementation of something that they are not, actual relationships. They are by definition artificial and demand disambiguation.
My travels in Flex-land keep coming back to the importance of namespaces outside the strict context of XML. Their time is coming; more widespread use of RDFa and the need for disambiguated rather than radical transparency are definitely indicative of this.
Wednesday, May 05, 2010
Seminal Granularity: I <3 the </>
It's no secret, I love me some XML, whether as an exchange format like XBRL, a messaging standard like HL7 or NIEM, or a document framework like DITA or DocBook. I am not sure what appeals to me so much about data-enrichment using tags, but it has something to do with reducing entropy by adding structure and meaning. In addition, I would rather model something using the sort of extension and restriction available in NIEM than the classical inheritance strategies presented by OOP. I have heard from several sources recently that the seachange from an object-oriented to declarative paradigm is underway, and I am pleased.
But more than this, I just love the angle brackets in a way I could never feel about dot-notation, and I am not alone in this.
I am attempting to develop a notion I am calling "Seminal Granularity." This notion appeals to my background in structuralist literary theory - "seminal" and "granular" are both agricultural references, both seeds, but whereas "seminal" has patriarchal overtones, granular is more mercurial. Between the two axes there lies a tension, bringing to mind a transclusive dilemma.
Simply stated, the transclusive dilemma is this: when faced with modifying an object, do you create a reference to the object for modification, a seminal approach which binds the new object to the original; or do you create a clone of the object, a granular approach which results in modification to the new object becoming estranged from the original, releasing the object through mimesis.
A viral licensed open-source project, for instance, is by design both seminal and granular. The project itself exists as a single seed, and it allows granular modification with the caveat that modifications are returned to the original seed.
Edit: there is also an odd kind of tie in with this short story, The Ice Box.
The transclusive dilemma is a real phenomenon; you cannot do both. Seminal granularity should be about finding ways to negotiate this problem. A wave can't be a particle either, right?
But more than this, I just love the angle brackets in a way I could never feel about dot-notation, and I am not alone in this.
I am attempting to develop a notion I am calling "Seminal Granularity." This notion appeals to my background in structuralist literary theory - "seminal" and "granular" are both agricultural references, both seeds, but whereas "seminal" has patriarchal overtones, granular is more mercurial. Between the two axes there lies a tension, bringing to mind a transclusive dilemma.
Simply stated, the transclusive dilemma is this: when faced with modifying an object, do you create a reference to the object for modification, a seminal approach which binds the new object to the original; or do you create a clone of the object, a granular approach which results in modification to the new object becoming estranged from the original, releasing the object through mimesis.
A viral licensed open-source project, for instance, is by design both seminal and granular. The project itself exists as a single seed, and it allows granular modification with the caveat that modifications are returned to the original seed.
Edit: there is also an odd kind of tie in with this short story, The Ice Box.
The transclusive dilemma is a real phenomenon; you cannot do both. Seminal granularity should be about finding ways to negotiate this problem. A wave can't be a particle either, right?
Tuesday, May 04, 2010
Talking Points: Collaboration and Documentation
A few years ago I wrote about a project I developed for my then employers, which I open sourced under the name CaseBook. The intent was to single-source end-user documentation which could be be transformed into internal and client acceptance test scripts. As I developed it, the project involved XML, Schematron, XSL and XQuery, hosted in an eXist database and accessed using webDAV.
At the time, I had barely heard of DITA, the Darwin Information Typing Architecture, but the approach I took shared some ideas with what I later came to learn about DITA, using concept maps, separation of topics into tasks and steps and so forth. In the mean time, DITA has gained a lot of traction, and my SourceForge page has been hit maybe 500 times.
I have been giving a lot of thought lately to collaborative writing. As Anne Gentle has pointed out on her JustWriteClick 'blog, DITA shines in environments which have a strong collaborative or Agile approach, since both of these emphasize timely repurposing and multipurposing. One of the problems I was addressing with CaseBook was collaboration between development, documentation and testing resources. Now, in part, this was because I was working in a small team, and had responsibilities in each of these areas.
I still think there is a lot of value in facilitating collaboration between these groups, and were I to develop this project today, I would start with the DITA Open Toolkit from day one.
In addition, for the last four months, I've been working with Flex, mxml and ActionScript. One thing that intrigues me about mxml is that it is XML. For instance, what if you could generate end user, acceptance or client walkthrough documentation automatically from the mxml source? Transforming mxml to DITA seems like a useful technique.
Any thoughts?
At the time, I had barely heard of DITA, the Darwin Information Typing Architecture, but the approach I took shared some ideas with what I later came to learn about DITA, using concept maps, separation of topics into tasks and steps and so forth. In the mean time, DITA has gained a lot of traction, and my SourceForge page has been hit maybe 500 times.
I have been giving a lot of thought lately to collaborative writing. As Anne Gentle has pointed out on her JustWriteClick 'blog, DITA shines in environments which have a strong collaborative or Agile approach, since both of these emphasize timely repurposing and multipurposing. One of the problems I was addressing with CaseBook was collaboration between development, documentation and testing resources. Now, in part, this was because I was working in a small team, and had responsibilities in each of these areas.
I still think there is a lot of value in facilitating collaboration between these groups, and were I to develop this project today, I would start with the DITA Open Toolkit from day one.
In addition, for the last four months, I've been working with Flex, mxml and ActionScript. One thing that intrigues me about mxml is that it is XML. For instance, what if you could generate end user, acceptance or client walkthrough documentation automatically from the mxml source? Transforming mxml to DITA seems like a useful technique.
Any thoughts?
Sunday, March 21, 2010
Working with Flex
For the past few months (since the start of the year), I have been working with Adobe Flex, in conjunction with a Java back-end leveraging Hibernate and Spring. The application under development is basically a public sector financial package, which does not specifically require RIA features, although UX has been established as a critical success factor.
I am following a fairly straightforward path to Flex, I suppose - early work with Action Script and other Adobe technologies lead me to Ajax, and then to Prototype and JQuery, after which I spent several years mired in JSP; and now I am back working with Action Script. Plus ça change, plus c'est la même chose.
I will write more about my experience in future articles, but specifically I want to raise a couple points of interest here: as a team, we have settled on Cairngorm as an MVC framework. If anyone has any thoughts on Cairngorm and the alternatives, or thoughts about using Flex as a rapid development tool for public sector work. Also, it seems like Flex could easily become a de facto standard for certain kinds of non-RIA development because of the easy Eclipse integration, and I would love to discuss others' experience.
Please drop by and leave a comment - I have been invaded by anonymous posters!
I am following a fairly straightforward path to Flex, I suppose - early work with Action Script and other Adobe technologies lead me to Ajax, and then to Prototype and JQuery, after which I spent several years mired in JSP; and now I am back working with Action Script. Plus ça change, plus c'est la même chose.
I will write more about my experience in future articles, but specifically I want to raise a couple points of interest here: as a team, we have settled on Cairngorm as an MVC framework. If anyone has any thoughts on Cairngorm and the alternatives, or thoughts about using Flex as a rapid development tool for public sector work. Also, it seems like Flex could easily become a de facto standard for certain kinds of non-RIA development because of the easy Eclipse integration, and I would love to discuss others' experience.
Please drop by and leave a comment - I have been invaded by anonymous posters!
Wednesday, February 03, 2010
Tab Sweep: 2010-02-03
Note: apologies to anyone actually reading this - I intend to collect and comment on things I come across during the week, then push the post out via Twitter on Friday. As this is a cumulative process, if the content seems light there will probably be more later. The alternative is to keep the post in draft for a while, but this seems lame.
From IBM's Smarter Planet: Education
Another former OLPC employee, Ivan Krstic, who now works in core security at Apple, comments on martian sandtraps. I at first thought he was speaking of golf, but apparently not. Since he began working at Apple, Krstic posts infrequently, but invariably leads to spit-take.
Apparently Mike Cane is done with his eBook Test blog, declaring the Apple iPad a future contender, or something. The vision of the iPad/iStore/iBook etc is there, even if the reality is not, yet, but we can confidently say that, yes, the iPad will change the way we read. Though I'm still holding out for the new Pixel Qi technology from OLPC alumnus Mary Lou Jepsen.
From London writer Marc Nash, an excellent critique of Roberto Bolano's 2666 and the hoopla surrounding the global reading of same at #2666 on Twitter. I am taking part in this reading, but wish I had read Bolano's Savage Detectives first, simply because of 2666's sprawling nature. Comparisons with Gravity's Rainbow, Infinite Jest and Finnegans Wake seems apt, based solely on the fly-leaf and first 100 or so pages.
Nice Valentines Day Cards, from Save the Children.
From IBM's Smarter Planet: Education
Now, I'm a big fan of the work that Walter Bender has been doing at Sugarlabs, as far as live booting a Sugar/Fedora OS off a USB stick, and this is more of the same. A combination of live booting thin OS and cloud computing is very potent.School districts operate on tight budgets in good times, but when Pike County found their IT budgets sliced by 80%, they knew it called for drastic measures—or true blue-sky thinking.
A rural Kentucky district of 10,000 students, Pike County administrators had struggled with providing IT resources for its students, teachers and staff. Desktop computers were still running Windows 98 with failing CD and hard drives; and access to the district's portal, which houses the applications and information the students and teachers needed,was inconsistent.
Working with IBM Global Technology Services and Desktone software, the district developed a virtual desktop infrastructure delivered as a cloud service. Students now boot the existing hardware with a special CD that bypasses the operating system and connects them instead to a high-performing virtual desktop environment. This in turn links to the district's portal site with all of the tools and information they need. Pike County can double the life of its hardware—it's planning on using seven-year-old machines without sacrificing performance—while providing students, teachers and administrators with equal, transparent access to its assets.
The district estimates cost savings of 64% over five years, compared to the cost of servicing the desktops on premises.
Another former OLPC employee, Ivan Krstic, who now works in core security at Apple, comments on martian sandtraps. I at first thought he was speaking of golf, but apparently not. Since he began working at Apple, Krstic posts infrequently, but invariably leads to spit-take.
Apparently Mike Cane is done with his eBook Test blog, declaring the Apple iPad a future contender, or something. The vision of the iPad/iStore/iBook etc is there, even if the reality is not, yet, but we can confidently say that, yes, the iPad will change the way we read. Though I'm still holding out for the new Pixel Qi technology from OLPC alumnus Mary Lou Jepsen.
From London writer Marc Nash, an excellent critique of Roberto Bolano's 2666 and the hoopla surrounding the global reading of same at #2666 on Twitter. I am taking part in this reading, but wish I had read Bolano's Savage Detectives first, simply because of 2666's sprawling nature. Comparisons with Gravity's Rainbow, Infinite Jest and Finnegans Wake seems apt, based solely on the fly-leaf and first 100 or so pages.
Nice Valentines Day Cards, from Save the Children.
Saturday, January 16, 2010
Axiom Attic: I
Somewhere between
over the sky and
under the ground
my roots lie
An axiom-tree, idiom-bird
climb climb soil
a thermal
buried deep
Thursday, December 17, 2009
Twitter-stuff: thanks for all the RT?
This is just a quick reflection on normative behaviour and a short personal declaration. I don't thank people for passing along what I have to say, and, while I don't specifically hold it against others when they do so, I do question their motivation. And I have unfollowed people for doing it excessively.
I don't use Twitter for strictly promotional purpose, and if you do, more power to you, especially if you are promoting a product or service I actually use. But I wonder, what is actually happening when you publically thank me for passing along your message? Well, yes, I am getting the thank you, and there is some reciprocation, if one or more of your subscribers decides to add me to to their subscription lists, but this is not likely, particularly if you thank a number of people in a single tweet.
Basically, what I understand when somebody thanks me for passing along a message is "thank you, please do it again" - which is all fine and good, but to be honest, if you were to come out and ask me to "plz RT" or whatever, I would be less likely to do so, and the same goes for a lot of the "thx 4 RT" I see - it makes me feel like I'm being played. So please don't bother.
If you disagree with this belief, let me know. I'm not a rude person, I thank people all the time for all sorts of things. But I'm not going to thank someone for carrying on a conversation with me.
I don't use Twitter for strictly promotional purpose, and if you do, more power to you, especially if you are promoting a product or service I actually use. But I wonder, what is actually happening when you publically thank me for passing along your message? Well, yes, I am getting the thank you, and there is some reciprocation, if one or more of your subscribers decides to add me to to their subscription lists, but this is not likely, particularly if you thank a number of people in a single tweet.
Basically, what I understand when somebody thanks me for passing along a message is "thank you, please do it again" - which is all fine and good, but to be honest, if you were to come out and ask me to "plz RT" or whatever, I would be less likely to do so, and the same goes for a lot of the "thx 4 RT" I see - it makes me feel like I'm being played. So please don't bother.
If you disagree with this belief, let me know. I'm not a rude person, I thank people all the time for all sorts of things. But I'm not going to thank someone for carrying on a conversation with me.
Monday, December 14, 2009
Tab Sweep 2009-12-14
Here are some things which I have been following in the last week:
- Bob DuCharme on the RDFS (RDF Schema) - Useful in theory, Bob summarizes RDFS and considers its more practical implications and application.
- W3C specification for EML (Emotion Markup) 1.0 - Silly, but that's the point I think. Mood is important though, and I keep coming back to this specification.
- Dynamic Planning for COIN in Afghanistan - via MCM at 1889.ca, who I believe uses systemic maps like this using grep and search and replace to build novel outlines.
- Google Launch of Living Stories - News thing (from SearchEngineLand @DannySullivan)
- EBooks and Backlists - past and future collide - (from Paul Witcover at Inferior 4+1 LJ) - When does an electronic publication go out of print?
- Google Enables Realtime Spam - Great analysis of the frightening implications of Google's move to open up to Twitter content (OutspokenMedia). Seriously, people were using 'blogs to googlebomb, how could microblogging not be more dangerous?
Friday, December 11, 2009
Reader, Writer, User Points: Engagement Engines
This comes as a response to an ongoing discussion at weblit.us regarding user points and reward systems for online fiction readers. Essentially, the motivation for a user points system is to increase engagement by giving readers something to achieve. The downside is that in order to implement a points system, as a writer you need to produce more, or deny some of your readership access to writing in which they would normally participate. This is problematic.
The system I am trying to sketch out here works within a larger framework that I am proposing, which I am calling an engagement engine. It works like this:
A writer begins with a blank slate, on which she can add descriptions of people, places and things. These are big categories that structure the engagement engine. As a writer, you are able to write as much as you want, but you cannot publish a new person, place or thing until the system allows you to do so - shortly after you start writing, you receive a gift (much like a gift in a social networking environment), which upon opening reveals itself to be, for instance, a place. You use this gift to breathe life into one of the locations you have already privately given a description, and this location is now available for use in your story. After you describe your location more deeply, you receive another gift, and this in turn allows you to breathe life into one of the characters you have described. Now you have a place and you have a person. You can start to really tell your story.
In an engagement engine, multiple writers are supported. This is not essential to the points and rewards system, but I honestly think this is an important component in creating a community, by creating healthy competition and collaboration. As opposed to a content management system, an content engagement system, applies many of the concepts of game-play and social networks, and these work best if they operate within and encourage a wider community.
What really drives the engagement system is the act of creating content, so as you add more content to the system, you receive more gifts, which allows you to breathe life into more people, places and things. This may seem artificial, but I am hazarding a guess that it actually plays well to a strength of many writers that I have known: they are more creative when faced with restrictions and challenges. And there is no limit on the amount of detail, narrative and dialog you can write, or the number of people, places and things you can describe - it's just that you can't actually publicly use these people, places or things until the system has allowed you to breathe life into them. Which means you will want to use your best ideas, and that is what you do anyway.
So this is where the points system comes into play. As your story is published in serial and people read it, you collect extra points from them toward the gifts you use to breathe life into your creations. So you might say "I need 50 more readers before I can add this really cool story arc," and your existing reader base have an incentive to pass the word along, because they benefit from the gifts you receive.
The more readers read a writer, the more that writer can write. This defines story arcs, and encourages reader and writer engagement in an organic fashion. This is by no means a complete description of what I am describing when I say engagement engine, but it is a start. Please feel free to leave a comment with any questions.
The system I am trying to sketch out here works within a larger framework that I am proposing, which I am calling an engagement engine. It works like this:
A writer begins with a blank slate, on which she can add descriptions of people, places and things. These are big categories that structure the engagement engine. As a writer, you are able to write as much as you want, but you cannot publish a new person, place or thing until the system allows you to do so - shortly after you start writing, you receive a gift (much like a gift in a social networking environment), which upon opening reveals itself to be, for instance, a place. You use this gift to breathe life into one of the locations you have already privately given a description, and this location is now available for use in your story. After you describe your location more deeply, you receive another gift, and this in turn allows you to breathe life into one of the characters you have described. Now you have a place and you have a person. You can start to really tell your story.
In an engagement engine, multiple writers are supported. This is not essential to the points and rewards system, but I honestly think this is an important component in creating a community, by creating healthy competition and collaboration. As opposed to a content management system, an content engagement system, applies many of the concepts of game-play and social networks, and these work best if they operate within and encourage a wider community.
What really drives the engagement system is the act of creating content, so as you add more content to the system, you receive more gifts, which allows you to breathe life into more people, places and things. This may seem artificial, but I am hazarding a guess that it actually plays well to a strength of many writers that I have known: they are more creative when faced with restrictions and challenges. And there is no limit on the amount of detail, narrative and dialog you can write, or the number of people, places and things you can describe - it's just that you can't actually publicly use these people, places or things until the system has allowed you to breathe life into them. Which means you will want to use your best ideas, and that is what you do anyway.
So this is where the points system comes into play. As your story is published in serial and people read it, you collect extra points from them toward the gifts you use to breathe life into your creations. So you might say "I need 50 more readers before I can add this really cool story arc," and your existing reader base have an incentive to pass the word along, because they benefit from the gifts you receive.
The more readers read a writer, the more that writer can write. This defines story arcs, and encourages reader and writer engagement in an organic fashion. This is by no means a complete description of what I am describing when I say engagement engine, but it is a start. Please feel free to leave a comment with any questions.
Thursday, December 10, 2009
Weblit-tle Town of Festivity, lend me your voice!
Hey!
Okay, look back to the start of November if you want the back story, but in a nutshell, Hallowe'en came and went and I managed to read a sum total of one creepy story online - although I know for a fact there were others - because my kids were already into the chocolate, and I was prepping a knight and a butterfly princess for further looting. So I sent out a request to the WebFic/WebLit community requesting that for the next big holiday season, ChristaKanzaNukkahTurkey, we get ourselves together and record a collection of festive tales, which we will then publish as public domain or Creative Commons NC for all to hear. People responded, and now that NaNoWriMo is done, the time has come.
So here we go.
Please send your seasonal tale to piers.hollott at gmail dot com, following these specifications as closely as you can manage:
Thanks,
Piers
Okay, look back to the start of November if you want the back story, but in a nutshell, Hallowe'en came and went and I managed to read a sum total of one creepy story online - although I know for a fact there were others - because my kids were already into the chocolate, and I was prepping a knight and a butterfly princess for further looting. So I sent out a request to the WebFic/WebLit community requesting that for the next big holiday season, ChristaKanzaNukkahTurkey, we get ourselves together and record a collection of festive tales, which we will then publish as public domain or Creative Commons NC for all to hear. People responded, and now that NaNoWriMo is done, the time has come.
So here we go.
Please send your seasonal tale to piers.hollott at gmail dot com, following these specifications as closely as you can manage:
- Easy on the swears. For my kids - they may be listening.
- 1000 words ~ 10 minutes, which is the length we are looking for.
- If possible 256 VBR mp3 would be ideal. I would like to put the collection on Internet Archive, and because they archive a lot of live recordings, they tend to be contiguous, meaning all files in an archive are similar in nature. If you are using GarageBand on a Mac, the best bet is to use the default setting (I have no idea what this is, but it will keep all Macusers consistent).
- Zip up your mp3 with a text version - I'll organize these as necessary, so word, text, even html are fine - not sure if I'll use them, but it would be good to make the archive searchable.
- Please include your name as you would like to be attributed and any other supporting info you might wish to include in a separate text file.
- Deadline Dec 18th or ASAP. I know some of you have already begun, and others have been busy with other things, so just let me know if this is a problem.
- I'm sure I am forgetting something, so comment if you think I have omitted anything.
Thanks,
Piers
Wednesday, December 09, 2009
What if a Brand were a Secured Namespace for Identity?
This is in part a response to an article on @mikecane's eBook Test, titled How Book Publishing Will Lose: eBooks Vs. Smart Digital Books, but it is also something I have been trying to articulate for a while. The question that haunts me is how to separate narrative concern from brand in a published work. So, I am asking, what if a brand were a secured namespace for identity?
Namespaces are an oft-maligned and misunderstood component of the plumbing of XML based representations of information, such as XHTML, DocBook, DITA and the like. When you create an HTML page, all of the tags you use to create the page are HTML tags, so you have no need for a namespace. When you create an XHTML page, or any other XML based representation, you may use tags from more than one vocabulary, so you use namespaces, represented by URIs, to discriminate between nodes in your document.
When you use a namespace in a document, you associate it with a prefix, which is used as a placeholder for the actual URI within the document. The URI itself must be unique, and often references a collection of schema or vocabulary documents.
What I would like to suggest is that a document representation of a text could be marked up using an appropriate namespace in order to determine an appropriate brand for the markup within the document. For instance,
So if you have the correct signature for the actor and the ISBN, you access the namespace, and you are blessed for use of the associated branding, which might be images, type-faces and so on. In the case of the pseudo-code above, you would require two signatures, one for Dora and one for Diego.
Or would you?
Well, this is where it gets interesting. What if you have secured one of the signatures, and not the other? Can you still read the text? Ostensibly, since this is pseudo-code, yes you can, if you change the namespace in the header declaration to a namespace for which you do have access; for instance, if an open-branded namespace were available, this could be used instead. In this way, if you were purchasing a book about Dora and Diego, you could pay for the entire branding, a portion of the branding, or just purchase the book itself without purchasing the branding, and rebrand the book with an open brand.
And then let the consumers decide.
So what does this all mean? I honestly believe that, as electronic publishing grows as an industry, it will become more and more necessary to separate narrative concern from commercial concern. So, what if brand were a secured namespace for identity? How would that change the industry?
Namespaces are an oft-maligned and misunderstood component of the plumbing of XML based representations of information, such as XHTML, DocBook, DITA and the like. When you create an HTML page, all of the tags you use to create the page are HTML tags, so you have no need for a namespace. When you create an XHTML page, or any other XML based representation, you may use tags from more than one vocabulary, so you use namespaces, represented by URIs, to discriminate between nodes in your document.
When you use a namespace in a document, you associate it with a prefix, which is used as a placeholder for the actual URI within the document. The URI itself must be unique, and often references a collection of schema or vocabulary documents.
What I would like to suggest is that a document representation of a text could be marked up using an appropriate namespace in order to determine an appropriate brand for the markup within the document. For instance,
<xhtmlis very rudimentary pseudo-code representing a description of Dora and Diego walking down the road, along with a picture of each of them doing so. This is not production code, mind you, this is merely a sketch of an idea, that the namespace used in this case securely identifies an actor, so that information such as images associated with this actor are not available unless some blessed mechanism, such as the involvement of a digital signature, is involved. More than likely, this mechanism would also involve the ISBN, since it would be unlikely that licensing an branded actor for use by a reader in one text would allow access for all texts.
xmlns='http://www.w3.org/1999/xhtml'
xmlns:dora='https://www.dora.com'
xmlns:diego='https://www.diego.com'
xmlns:isbn='urn:ISBN:0-395-36341-6'>
<title>El Camino Grande</title>
<p property="isbn:number" content="123-456789"/>
<p>
<img src="dora:walking"/>
<span actor="dora:actor">Dora</span> and
<span actor="diego:actor" >Diego</span>
walked down the road
<img src="diego:walking"/>
</p>
So if you have the correct signature for the actor and the ISBN, you access the namespace, and you are blessed for use of the associated branding, which might be images, type-faces and so on. In the case of the pseudo-code above, you would require two signatures, one for Dora and one for Diego.
Or would you?
Well, this is where it gets interesting. What if you have secured one of the signatures, and not the other? Can you still read the text? Ostensibly, since this is pseudo-code, yes you can, if you change the namespace in the header declaration to a namespace for which you do have access; for instance, if an open-branded namespace were available, this could be used instead. In this way, if you were purchasing a book about Dora and Diego, you could pay for the entire branding, a portion of the branding, or just purchase the book itself without purchasing the branding, and rebrand the book with an open brand.
And then let the consumers decide.
So what does this all mean? I honestly believe that, as electronic publishing grows as an industry, it will become more and more necessary to separate narrative concern from commercial concern. So, what if brand were a secured namespace for identity? How would that change the industry?
Prepare for Parallax: Files in the Cloud
Following up on a conversation with a co-worker this morning, something struck me as obvious. One of the things Sugar OS handles really well (either as sugar-on-a-stick or on the OLPC XO laptop) is simplifying the file/resource paradigm to make it consumable by children, by basing access on chronology rather than hierarchy, reminiscent of a search engine rather than a file system. Also, on Sugar you work with activities rather than files.
What struck me recently is that on the one hand, movement towards a cloud OS reflects a shift in consumer tastes from tasks like email (where you attach files in order to share) to social networking (where you pass around links and participate in activities in order to share), so when somebody asks me, in the context of a cloud OS, "but how will you be able to locate your files?" my initial reaction is this: either chronologically, or collaboratively (or possibly spatially, but that is a separate issue).
Think about it this way: was the document or picture I am trying to find something I touched recently? That should make it easy to find. No? Is it something I shared or created with another person or group of people? That narrows the field. As I add in more relationships with people who may have come in contact with the activity in question, I have fewer and fewer activities to sift through.
I think the desktop of the future will not be a desktop at all, it will be more like a shared light-box, emphasizing transparency. In order to find something again easily, you must give it relevance, and the best way you can do this is to share it, to make it available to the people with whom you already have instantiated relevant relationships.
Far more intriguing to me, while at the same time quite far out, is the idea of a spatial desktop, where the first question you ask when you want to locate a particular item is where was I? Where was I when I took the picture? Did I participate in this activity at work, on a plane, at home, in the living room or in the dining room? On the one hand, this sort of information might not be readily available for many activities, but if it were, how quickly would that narrow the field if you could recall your location when you took that picture?
The advantage of this approach is obvious as well. If you can't locate the actual picture, you can ask who else was there? Be prepared for parallax.
What struck me recently is that on the one hand, movement towards a cloud OS reflects a shift in consumer tastes from tasks like email (where you attach files in order to share) to social networking (where you pass around links and participate in activities in order to share), so when somebody asks me, in the context of a cloud OS, "but how will you be able to locate your files?" my initial reaction is this: either chronologically, or collaboratively (or possibly spatially, but that is a separate issue).
Think about it this way: was the document or picture I am trying to find something I touched recently? That should make it easy to find. No? Is it something I shared or created with another person or group of people? That narrows the field. As I add in more relationships with people who may have come in contact with the activity in question, I have fewer and fewer activities to sift through.
I think the desktop of the future will not be a desktop at all, it will be more like a shared light-box, emphasizing transparency. In order to find something again easily, you must give it relevance, and the best way you can do this is to share it, to make it available to the people with whom you already have instantiated relevant relationships.
Far more intriguing to me, while at the same time quite far out, is the idea of a spatial desktop, where the first question you ask when you want to locate a particular item is where was I? Where was I when I took the picture? Did I participate in this activity at work, on a plane, at home, in the living room or in the dining room? On the one hand, this sort of information might not be readily available for many activities, but if it were, how quickly would that narrow the field if you could recall your location when you took that picture?
The advantage of this approach is obvious as well. If you can't locate the actual picture, you can ask who else was there? Be prepared for parallax.
Monday, November 23, 2009
Twitter Retweet Follow/Unfollow
I really have only one thing to add to the ongoing discussion of the new Twitter Retweet integration, other than the obvious, that I use a third party client so I don't really care.
I am noticing that when somebody in my network retweets somebody who is not in my network from the Twitter home page, I see:
If Twitter gave me the option to follow the person I am not following, or unfollow the person I am following, I would absolutely love this feature.
I am noticing that when somebody in my network retweets somebody who is not in my network from the Twitter home page, I see:
- the retweet,
- a message telling me "Wondering who this is? Someone you follow thought this was worth retweeting, which is why you are seeing it in your Home timeline."
If Twitter gave me the option to follow the person I am not following, or unfollow the person I am following, I would absolutely love this feature.
Saturday, November 21, 2009
More Semantic Silliness
<object>
<span property="dc:creator">Dan Brown</span>
<span property="dc:title">The Du Blinci Core</span>
</object>
...in which Tom Hanks plays a singleton node who discovers that he is somehow miraculously able to hold content, assisted in his search for meaning by Audrey Tautou, who along the way learns to re-purpose several hitherto erstwhile under-appreciated property attributes.
Sir Ian McKellen turns in a riveting performance as a priest who is actually an xml spy utilizing a Saxon transformer-implementation.
This perhaps is a film I would enjoy....
<span property="dc:creator">Dan Brown</span>
<span property="dc:title">The Du Blinci Core</span>
</object>
...in which Tom Hanks plays a singleton node who discovers that he is somehow miraculously able to hold content, assisted in his search for meaning by Audrey Tautou, who along the way learns to re-purpose several hitherto erstwhile under-appreciated property attributes.
Sir Ian McKellen turns in a riveting performance as a priest who is actually an xml spy utilizing a Saxon transformer-implementation.
This perhaps is a film I would enjoy....
Friday, November 20, 2009
Sketches for a Group Membership Vocabulary
(Or the Strange Tale of RDFa and the Room with Two Doors)
I am sketching these ideas out here because I think they may be useful at some point, and I would really appreciate feedback; if this sort of vocabulary is already available somewhere, please ping me and let me know. And I'm going to save the RPG analogy for the end, because I know these can be deterrent. [ed. whatever! skip to the jump; it's funny!]
An activity I have had to address on several projects now involves profiling or gate-keeping groups of people or objects for the purpose of authorization or processing. For instance, in a CRM application, it might be necessary to tag potential customers as prospects, clients, inactive, etc. Or for a workflow application for a working group, it might be necessary to track people who are actively developing, people who have left the group, but are still useful resources and so on. I have yet to see a reasonable vocabulary for tracking these people. If such a vocabulary exists, I am sure it has many uses in a variety of contexts.
This vocabulary would have the following component(s):
Membership Status (mg:status):
This is the status of an individual, group or artifact within a larger community, given the following states, which should be mutually exclusive:
So here is the RPG example:
A group of adventurers is exploring a location, when they reach two doors, one red and one blue. At this point, with respect to each of the doors, the two rooms could be described using the following RDFa-like pseudoterminology:
<room id="behind_the_red_door">
<member id="adv1" property="mg:status" content="prospect"/>
<member id="adv2" property="mg:status" content="prospect"/>
<member id="adv3" property="mg:status" content="prospect"/>
</room>
...and similarly for the room behind_the_blue_door.
Now, one of the adventurers discovers a key to one of the doors. At this point, this adventurer becomes content="candidate", whereas the other adventurers become content="intitiate" - they have an understanding of how to enter, but only the first adventurer has the key. However, since the door is now unlocked. Sicne the door is locked, only candidates can enter. When the first adventurer unlocks the door, the state of the room changes such that now candidates and initiates may enter (the state of the door in this case might be handled by a separate vocabulary - also this example hinges painfully poorly on the assumption that once unlocked, a door cannot be relocked).
At this point, adv2, the knight steps forward and enters the room:
<room id="behind_the_red_door">
<member id="adv1" property="mg:status" content="candidate"/>
<member id="adv2" property="mg:status" content="member"/>
<member id="adv3" property="mg:status" content="intitiate"/>
</room>
Naturally, the brave knight discovers that the room is full of a poisonous gas, and sensibly flees. The group of adventurers investigates the second door:
<room id="behind_the_blue_door">
<member id="adv1" property="mg:status" content="prospect"/>
<member id="adv2" property="mg:status" content="prospect"/>
<member id="adv3" property="mg:status" content="prospect"/>
</room>
Fortunately, the same key unlocks this door as well, and the door is unlocked. The knight is less enthusiastic, so the curious wizard enters the room.
<room id="behind_the_blue_door">
<member id="adv1" property="mg:status" content="candidate"/>
<member id="adv2" property="mg:status" content="intitiate"/>
<member id="adv3" property="mg:status" content="member"/>
</room>
So far so good. Mind you, this room is full of a tasteless and odourless poisonous gas, but nobody seems to have noticed. The wizard beckons to his companions to enter the room:
<room id="behind_the_red_door">
<member id="adv1" property="mg:status" content="candidate"/>
<member id="adv2" property="mg:status" content="alumnus"/>
<member id="adv3" property="mg:status" content="initiate"/>
</room>
<room id="behind_the_blue_door">
<member id="adv1" property="mg:status" content="member"/>
<member id="adv2" property="mg:status" content="member"/>
<member id="adv3" property="mg:status" content="member"/>
</room>
And now the diabolically cunning design of the room becomes painfully clear, as the combined effect of the gases in the two rooms becomes apparent, and the unfortunate knight, who has membership || alumnus status for both rooms, turns into a pillar of salt.
<room id="behind_the_red_door">
<member id="adv1" property="mg:status" content="candidate"/>
<member id="adv2" property="mg:status" content="alumnus"/>
<member id="adv3" property="mg:status" content="initiate"/>
</room>
<room id="behind_the_blue_door">
<member id="adv1" property="mg:status" content="alumnus"/>
<member id="adv2" property="mg:status" content="permanent"/>
<member id="adv3" property="mg:status" content="alumnus"/>
</room>
So ends the story of "RDFa and the Diabolic Room with Two Doors."
I am sketching these ideas out here because I think they may be useful at some point, and I would really appreciate feedback; if this sort of vocabulary is already available somewhere, please ping me and let me know. And I'm going to save the RPG analogy for the end, because I know these can be deterrent. [ed. whatever! skip to the jump; it's funny!]
An activity I have had to address on several projects now involves profiling or gate-keeping groups of people or objects for the purpose of authorization or processing. For instance, in a CRM application, it might be necessary to tag potential customers as prospects, clients, inactive, etc. Or for a workflow application for a working group, it might be necessary to track people who are actively developing, people who have left the group, but are still useful resources and so on. I have yet to see a reasonable vocabulary for tracking these people. If such a vocabulary exists, I am sure it has many uses in a variety of contexts.
This vocabulary would have the following component(s):
Membership Status (mg:status):
This is the status of an individual, group or artifact within a larger community, given the following states, which should be mutually exclusive:
- unknown - this is a nicety and not essential. Undefined.
- prospect - potential only to be a group member.
- candidate - selected by an automated process to become a group member, but not one yet.
- nominee - recommended to become a group member by an existing member.
- initiate - has completed self-registration etc, but not yet a group member.
- member - an active member of the group.
- banned - removed from group by process with proviso of reentry.
- permban - removed from groupt by process with no proviso for reentry. TERMINAL.
- alumnus - a non-active former member of the group. TERMINAL.
- permanent - a member that can never be removed from the group. TERMINAL.
So here is the RPG example:
A group of adventurers is exploring a location, when they reach two doors, one red and one blue. At this point, with respect to each of the doors, the two rooms could be described using the following RDFa-like pseudoterminology:
<room id="behind_the_red_door">
<member id="adv1" property="mg:status" content="prospect"/>
<member id="adv2" property="mg:status" content="prospect"/>
<member id="adv3" property="mg:status" content="prospect"/>
</room>
...and similarly for the room behind_the_blue_door.
Now, one of the adventurers discovers a key to one of the doors. At this point, this adventurer becomes content="candidate", whereas the other adventurers become content="intitiate" - they have an understanding of how to enter, but only the first adventurer has the key. However, since the door is now unlocked. Sicne the door is locked, only candidates can enter. When the first adventurer unlocks the door, the state of the room changes such that now candidates and initiates may enter (the state of the door in this case might be handled by a separate vocabulary - also this example hinges painfully poorly on the assumption that once unlocked, a door cannot be relocked).
At this point, adv2, the knight steps forward and enters the room:
<room id="behind_the_red_door">
<member id="adv1" property="mg:status" content="candidate"/>
<member id="adv2" property="mg:status" content="member"/>
<member id="adv3" property="mg:status" content="intitiate"/>
</room>
Naturally, the brave knight discovers that the room is full of a poisonous gas, and sensibly flees. The group of adventurers investigates the second door:
<room id="behind_the_blue_door">
<member id="adv1" property="mg:status" content="prospect"/>
<member id="adv2" property="mg:status" content="prospect"/>
<member id="adv3" property="mg:status" content="prospect"/>
</room>
Fortunately, the same key unlocks this door as well, and the door is unlocked. The knight is less enthusiastic, so the curious wizard enters the room.
<room id="behind_the_blue_door">
<member id="adv1" property="mg:status" content="candidate"/>
<member id="adv2" property="mg:status" content="intitiate"/>
<member id="adv3" property="mg:status" content="member"/>
</room>
So far so good. Mind you, this room is full of a tasteless and odourless poisonous gas, but nobody seems to have noticed. The wizard beckons to his companions to enter the room:
<room id="behind_the_red_door">
<member id="adv1" property="mg:status" content="candidate"/>
<member id="adv2" property="mg:status" content="alumnus"/>
<member id="adv3" property="mg:status" content="initiate"/>
</room>
<room id="behind_the_blue_door">
<member id="adv1" property="mg:status" content="member"/>
<member id="adv2" property="mg:status" content="member"/>
<member id="adv3" property="mg:status" content="member"/>
</room>
And now the diabolically cunning design of the room becomes painfully clear, as the combined effect of the gases in the two rooms becomes apparent, and the unfortunate knight, who has membership || alumnus status for both rooms, turns into a pillar of salt.
<room id="behind_the_red_door">
<member id="adv1" property="mg:status" content="candidate"/>
<member id="adv2" property="mg:status" content="alumnus"/>
<member id="adv3" property="mg:status" content="initiate"/>
</room>
<room id="behind_the_blue_door">
<member id="adv1" property="mg:status" content="alumnus"/>
<member id="adv2" property="mg:status" content="permanent"/>
<member id="adv3" property="mg:status" content="alumnus"/>
</room>
So ends the story of "RDFa and the Diabolic Room with Two Doors."
Thursday, November 12, 2009
My Morning Archive
I am currently listening what I consider My Morning Jacket's finest live recording, live at the Palace in Louisville, KY, 2005-11-23, recorded nearly four years ago. I can tell you several things about MMJ:
If you want to download the recording, check out archive.org. It will be there, because the Internet Archive is an archive of artifacts; nothing ever goes out of print on IA. In fact, Internet Archive is wholly remarkable, largely because of the vision of one person, Brewster Kahle. Look him up on Wikipedia. You could even use the Wayback Machine at IA to do so, because the entire internet is backed up there. This is kind of misleading. It's actually also backed up by the same organization as a secondary backup in Alexandria. How cool is that?
Also, the Internet Archive is poised to deliver some amazing things in the future, as well as the past. If you are not paying attention to IA, and you are interested in the future of culture, books and reading, pay attention, and do some research on the Open Content Alliance, archive.org, Open Library, Book Reader and Brewster Kahle. You will not regret this.
- Michael Mahemoff has written about Ajax design patterns, and has used MMJ as the intro to a podcast on the subject; also, follow @mahemoff on Twitter if you are so inclined.
- MMJ are fans of the movie Ghostbusters, and have often played the Ghostbusters music pre-show. In the recording to which I am listening, they refer to "busting ghosts."
- The recording I am listening to fits nicely onto a single CD if you strategically remove one song, otherwise, it splits nicely into a double CD. You supply the cover art.
If you want to download the recording, check out archive.org. It will be there, because the Internet Archive is an archive of artifacts; nothing ever goes out of print on IA. In fact, Internet Archive is wholly remarkable, largely because of the vision of one person, Brewster Kahle. Look him up on Wikipedia. You could even use the Wayback Machine at IA to do so, because the entire internet is backed up there. This is kind of misleading. It's actually also backed up by the same organization as a secondary backup in Alexandria. How cool is that?
Also, the Internet Archive is poised to deliver some amazing things in the future, as well as the past. If you are not paying attention to IA, and you are interested in the future of culture, books and reading, pay attention, and do some research on the Open Content Alliance, archive.org, Open Library, Book Reader and Brewster Kahle. You will not regret this.
Tuesday, November 10, 2009
Tab Sweep 2009-11-10
For whatever reason, I have been reading up on Provenance Models recently (semantic models and vocabularies for tracking sources of truth, ownership and creative process), also a directory of book trade people on twitter and a post-modern literary review. Because this is NaNoLnkMo for me, and because I believe URLs should be human-parsable, I am not going to link to these. I am however going to close these tabs now so I can get some work done.
[http://eprints.ecs.soton.ac.uk/16148/1/opm-v1.01.pdf]
[http://dig.csail.mit.edu/TAMI/harveyj/provenance-final/paper.pdf]
[http://www.highspotinc.com/blog/2008/12/a-directory-of-book-trade-people-on-twitter/]
[http://www.fictionweek.com/fwliteraryreview/fictionweekliteraryreview.html]
[http://eprints.ecs.soton.ac.uk/16148/1/opm-v1.01.pdf]
[http://dig.csail.mit.edu/TAMI/harveyj/provenance-final/paper.pdf]
[http://www.highspotinc.com/blog/2008/12/a-directory-of-book-trade-people-on-twitter/]
[http://www.fictionweek.com/fwliteraryreview/fictionweekliteraryreview.html]
Subscribe to:
Posts (Atom)
