| |||||||||
|
176. #21089 A directory of more than 100 online resources about RSS (Really Simple Syndication). 177. #20735 RSS Primer for Knowledge Base Publishers RSS (Rich Site Summary or Really Simple Syndication) is an XML format designed for sharing headlines and other Web content. Print and Web publishers such as BBC, CNET, CNN, Disney, Forbes, Motley Fool, Wired, Red Herring, Salon, Slashdot, and ZDNet use it to distribute stock tickers, sport scores, weather reports, news headlines and other information. Montague Institute Review (2003). Articles>Information Design>XML>RSS 178. #29961 Save Time and Code with XPath 2.0 and XSLT 2.0 Three interesting new features in XPath 2.0 and XSLT 2.0 are the item data type, the to operator, and the concept of sequences. Build a sample application that uses these features to generate a sophisticated HTML view of an XML document, and with the new features in XSLT 2.0, create shorter stylesheets that are easier to maintain. Along the way, spend a bit of time on data typing in XSLT 2.0, and learn to use the new Tidwell, Doug. IBM (2007). Articles>Web Design>XML>XSL 179. #21626 XML syntax is just the foundation for data interoperability. The next step is semantic transparency. Some groups are working to address this by defining entire document formats to be adopted wholesale, while other groups are working on ways to express common terminology and concepts at a more granular level. In this installment, Uche Ogbuji looks at XML Topic Maps Published Subjects and Universal Data Element Framework (UDEF), two ideas that take the granular approach by seeking to provide anchors in the semantic stream. Ogbuji, Uche. IBM (2003). Design>Information Design>XML>Metadata 180. #29977 Semantic, Structured Authoring This article looks at the impact of the introduction of semantic markup and structured authoring on the world of technical writers, editors, Help authors and content developers. This article is not specifically about the Semantic Web movement itself, but about the implementation of semantic concepts in the documentation field. Self, Tony. HyperWrite (2006). Articles>Information Design>XML>Technical Writing 181. #21003 This document is not intended to teach you RDF via my own words, but rather to hand-hold you through the 'good' parts of the same journey I took. If it looks like a big link-list with menial comments from the peanut gallery, then you're not far off the mark of my intent. This is by no means definitive, nor was that the goal. Disobey.com (2003). Articles>Information Design>Metadata>XML 182. #21002 The Semantic Web: An Introduction This document is designed as being a simple but comprehensive introductory publication for anybody trying to get into the Semantic Web: from beginners through to long time hackers. Recommended pre-reading: the Semantic Web in Breadth. Palmer, Sean B. InfoMesh (2001). Articles>Information Design>Metadata>XML 183. #21599 This is a general collection of my Semantic Web hackings, often using CWM and the Notation3 (N3) format. Palmer, Sean B. InfoMesh (2001). Articles>Information Design>Metadata>XML 184. #21001 This piece speaks about the different parts of the Semantic Web and how they fit together. Swartz, Aaron. LogicError (2003). Articles>Information Design>Metadata>XML 185. #28070 Service Oriented Architecture (SOA) Made Simple Even if you're wrapping a legacy application, you'll need a service description that other web services applications can use. Of course, there are many data-binding tools available that are, for example, capable of turning a Java class into an XML Schema or a Windows-compatible wizard with a "generate WSDL" button. But even then, you'll have to give those descriptions to others, the tools may have bugs (surprising, I know, but it's been known to happen), or you'll need to hand-tweak the generated files because a particular customer "just wants the namespace or URL changed." At that point, you don't want to have to burn the midnight oil with a copy of the WSDL and Schema specs in hand and the generated WSDL file on your screen. Salz, Rich. XML.com (2005). Articles>Information Design>XML 186. #27285 The fact that many decisions need a combination of information sources makes easy integration of geospatial data an important data usability issue. Our vision is to achieve automated just-in-time integration. As a foundation, we present a system architecture with distributed data and services. Existing and evolving standards and technologies fitting into this architecture are presented along with their scope and shortcomings. A major point is the appropriate definition of data and operation semantics. Further research is needed here to make the automatic formation of service chains for data integration possible. Riedemann, Catharina and Christian Timm. Data Science Journal (2003). Articles>Information Design>XML>Geography 187. #21174 Jason shares his knowledge about RSS: What it is, how it's used, and why you need it. Just don't ask him what it stands for. Cook, Jason. Webmonkey (2003). Design>Web Design>XML>RSS 188. #29587 Simple Web Syndication with RSS 2.0 Simply put RSS is an XML application for simple web feed syndication and content subscriptions. Let's say you have content on your site that you want to feed, or make available for other sites. This is known as web syndication. Most commonly this takes the form of sharing news headlines, product releases, or some similar timely content. RSS provides a standardized method for web sites to use when creating these feeds. Dev Articles (2007). Articles>Information Design>XML>RSS 189. #27722 SOAP is a protocol for exchanging XML-based messages over a computer network, normally using HTTP. SOAP forms the foundation layer of the Web services stack, providing a basic messaging framework that more abstract layers can build on. SOAP can be used to facilitate a Service-Oriented architectural pattern. Wikipedia (2006). Articles>Information Design>XML>SOAP 190. #22199 Some Thoughts about SOAP versus REST on Security REST is the underlying architecture of the World Wide Web and its two core specifications, URIs and HTTP. It has been proposed that instead of using new-from-scratch Web Services technologies we can get much more bang for our buck by understanding the full generality of what we've got. A community has arisen around this idea and we spend our time proving that what the Web already has is better than what is being developed. This page addresses the security weaknesses of the SOAP approach. 191. #27915 About ten years ago, a handful of highly specialised consultants were trying with missionary zeal to establish SGML as the basic format in technical communication; today, the XML-standard is no longer something that can be dispensed with, and is, in fact, even mandatory in many projects. This article takes a look in hindsight at the beginnings of SGML and XML, and the current developments and standards around XML, and also hazards a guess at what the years to come might hold in store. Rath, Hans Holger. tekom (2006). Articles>Information Design>Standards>XML 192. #21499 Strategies in Re-Purposing Graphics for Interactive Intelligent Delivery In the domain of aerospace/defense, a products life cycle may likely span up to 30 years. The amount of technical data required to manufacture, operate, and maintain those products is immense. The graphic representation of that data facilitates the communication of operational and maintenance instructions. This paper outlines issues with creating, authoring, revising, and delivering intelligence with graphics and the associated meta-data. Woolsey, Jeremiah and Martin Jackson. XML Europe (2001). Articles>Information Design>XML>Metadata 193. #30120 Streamlining Content Creation and Publishing with XMetaL and DITA To streamline the product documentation process, many technical publication teams are moving to Darwin Information Typing Architecture (DITA). Learn best practices for applying this information model, and hands-on techniques for improved content creation and publishing with JustSystems XMetaL. Silver, Jerry. Intercom (2007). Articles>Content Management>XML>DITA 194. #19468 Implementing structured authoring with XML allows organizations to create better content. The addition of hierarchy and metadata to content improves reuse and content management. These benefits, however, must be weighed against the time and money required to implement a structured authoring approach. The business case is compelling for larger writing organizations; they will be the first to adopt structured authoring. Over time, improvements in available tools will reduce the cost of implementing structured authoring and make it affordable for smaller organizations. O'Keefe, Sarah S. Scriptorium (2002). Design>Publishing>Information Design>XML 195. #28185 Structured Authoring and XML: Part One Implementing structured authoring with XML allows organizations to create better content. The addition of hierarchy and metadata to content improves reuse and content management. These benefits, however, must be weighed against the time and money required to implement a structured authoring approach. The business case is compelling for larger writing organizations; they will be the first to adopt structured authoring. Over time, improvements in available tools will reduce the cost of implementing structured authoring and make it affordable for smaller organizations. O'Keefe, Sarah S. Carolina Communique (2003). Articles>Documentation>Information Design>XML 196. #28177 Structured Authoring and XML: Part Three Not every content-creation group will benefit from structured authoring and XML. Sometimes, the expense of implementation outweighs the benefits realized, especially in smaller groups with less total page count. O'Keefe, Sarah S. Carolina Communique (2004). Articles>Documentation>Information Design>XML 197. #28186 Structured Authoring and XML: Part Two In a structured authoring environment, authors create documents by assembling elements and text in an order permitted by the structure definition document. You might think of structured authoring as being similar to template-based authoring with a strict template. Authors do not assign formatting; the formatting is automatically assigned based on the structure of the document. Formatting may differ for different output media. O'Keefe, Sarah S. Carolina Communique (2003). Articles>Documentation>Information Design>XML 198. #28184 Structuring Your Documents for Maximum Reuse A major topic among information development managers these days is single sourcing--writing information once and using it many times. Structured documents are critical for single sourcing. So, let's explore: what we mean by structuring documents; why structuring is useful; some of the concerns that writers have about structuring documents. Redish, Janice C. 'Ginny'. Center for Information-Development Management (2005). Articles>Content Management>Information Design>XML 199. #14683 Styling XML: An Opinionated Guide McLaughlin evaluates the abilities of CSS (Cascading Style Sheets) and XSLT (eXstensible Style Language for Transformation) to render XML content in Internet browsers. McLaughlin, Douglas J. Intercom (2001). Design>Web Design>XML 200. #29402 Subsetting and Customizing DITA This article explores ideas related to subsetting and customizing the DITA specification without the addition of new elements. Instead, we explore taking default rules and adapting them to meet the needs of specific writing and publishing environments. Introductory information about the DITA specification and the difference between subsetting and specialization is provided. Aschwanden, Bernard. Publishing Smarter (2006). Articles>Information Design>XML>DITA
| |||||||||
| |||||||||
Click here to learn how to embed the RSS feed of this category in your website.