DOCSLIB.ORG

Copyrighted Material

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

22_087889 bindex.qxp 10/19/06 4:04 PM Page 495 Index Index SYMBOLS AND Accessibility...: Problem—Design—Solution,95 accessibility issues NUMERICS aural CSS, 106 & (ampersand) automatic redirects, 107 XML reserved character, 224 automatic refresh, 107 XML symbol for, 224 BuzzWatch, 25–28 <-- -->, XML comments, 225 color, 96–99 ‘ (apostrophe), XML symbol for, 224 dealing with images, 96–99 === (equal signs), type comparison operator, deprecated tags, 99 64–65 device independent scripts, 105 == (equal signs), type conversion operator, distractions, 104 64–65 frames, 106 > (greater than sign), XML, 224 headers, 107–108 # (hash character), comment indicator, 436 inline styles, 99 < (less than sign), XML, 224 labels on form inputs, 105 “ (quotation marks), XML symbol for, 224 legislation, 95 <? ?> (processing instructions), 122–124 links, 104 1xx Informational responses, 207–208 Olympic Games case study, 95 2xx Success responses, 207–208 pop-up windows, 107 3xx Redirection responses, 207–208 previewing pages, 108 4xx Client Error responses,COPYRIGHTED 207–208 separating MATERIAL content from presentation, 99–103 5xx Server Error responses, 207–208 sidebars, 107–108 302 Found status code, 427 tables, 99–103 404 Not Found status code, 431–433 text emphasis, 99–103 user-friendly URLs, 104 A W3C recommendations, 95 <abbr> element, 272–273 Adleman, Len, 469 Abdera Atom toolkit, 374–375 Adobe SVG plug-in, 141 22_087889 bindex.qxp 10/19/06 4:04 PM Page 496 ADO.NET, converting relational data to XML ADO.NET, converting relational data to XML, APIs 343–348 DOM adr & geo microformats, 271–272 online resources, 51 Advanced Systems Format (ASF), 449 overview, 49–50 aggregation reference, 51 BuzzWatch, 2 Flickr SOAP, 295–299 feeds, 412 Google Maps, 417–419 AIFF (Audio Interchange File Format), 448 JAXP (Java API for XML Processing), 315–317 Ajax (Asynchronous JavaScript and XML). See serialization, 315–317 also JavaScript. XML, 235 definition, 70 &apos (apostrophe) entity, 224 displaying XML information on a page, 71–75 apostrophe (‘), XML symbol for, 224 extracting information from XML files, 71–75 APP (Atom Publishing Protocol), 235, 291 Google Web Toolkit, 78–79 application architecture, 374 HTTP queries, 71–75 application layer, 195 loading XML files, 71–75 “Architectural Styles and the Design of Network- memory leaks, 79–81 based Software Architectures,” 194 technologies, 70–71 Architecture of the World Wide Web, 194 user experience, 71 articles. See books and publications. XMLHttpRequest object ASF (Advanced Systems Format), 449 example, 72–75 ASP.NET history, 71–72 authentication YUI (Yahoo! UI) Library, 75–78 configuring, 466 YUIConnectionManager object, 77–78 overview, 462–464 aligning text, 128 authorization alternate value, 260 configuring, 466 Amazon.com, 294, 406 overview, 462–464 &amp (ampersand) entity, 224 dynamic content (XML), serving over HTTP, ampersand (&), XML, 224 317–320 animation, 136–137 HTTP redirection, 433 Apache serving XML dynamic content over HTTP, Abdera Atom toolkit, 374–375 317–320 authentication, 466–467 Asynchronous JavaScript and XML (Ajax). See authorization, 466–467 Ajax (Asynchronous JavaScript and XML). SSL (Secure Sockets Layer) Atom format certificate request, generating on Unix, alternate value, 260 476–477 description, 258–260 certificate request, submitting in IIS, 477 enclosure value, 260 configuring the site, 478 enclosures, 262–263 issued certificates. installing, 477–479 history of, 257 setting up, 474–478 href attribute, 260 Web server, 208 hreflang attribute, 260 496 22_087889 bindex.qxp 10/19/06 4:04 PM Page 497 binary data, converting to XML Index length attribute, 260 Audio Interchange File Format (AIFF), 448 <link> element, 260 Audio Video Interleave (AVI), 448–449 podcasting, 262–263 aural CSS, 106 rel attribute, 260 authentication related value, 260 in Apache, 466–467 self value, 260 in ASP.NET specifications, 261 configuring, 466 title attribute, 260 overview, 462–464 type attribute, 260 custom, web services, 487–489 via value, 260 definition, 459–460 Atom Publishing Protocol (APP), 235, 291 HTTP type, 466–467 Atom service for syndication channels in IIS Apache Abdera toolkit, 374–375 configuring, 464–465 application architecture, 374 overview, 462–464 code overview providers, 466–467 AtomServlet.java class, 375, 377–383 authority section, URIs, 197 clearFeed method, 384 authorization clearing the feed, 376 in Apache, 466–467 compare method, 384–385 in ASP.NET core files, 375 configuring, 466 createEntry method, 387 overview, 462–464 createFeed method, 385–386 definition, 460 isEntryInFeed method, 387 in IIS loadFeed method, 386 configuring, 464–465 MailClient.java class, 375 overview, 462–464 MailEntryCollector.java class, 375 providers, 466–467 MessageReader.java class, 375 autodiscovery, 251 Settings.java class, 375, 388 AVI (Audio Video Interleave), 448–449 sortEntries method, 384 Utils.java class, 375, 383–388 writeTo method, 386–387 B e-mail support badges, 416–417, 418 Berners-Lee, Tim MailClient.java class, 393–396 “Cool URIs don’t change,” 198 MailEntryCollector implementation, 396–400 web browsers, 194 and the WWW (World Wide Web), 168 MessageReader interface, 396 binary data, converting to XML readMessage method, 399–400 feed reader, 373 automatically, 363–370 user interface, 372–373 manually, 358–363 Atom Syndication Format, 235 from Microsoft Word, 358 overview, 229–230 AtomServlet.java class, 375, 377–383 attributes, XML, 223–224 viewing raw data, 361 497 22_087889 bindex.qxp 10/19/06 4:04 PM Page 498 binding data to external source binding data to external source, 188–190 database query, 13–20 blind users. See accessibility issues. document presentation, 1–12 Blogs channel, 274 internals, examining BMP (Basic Multilingual Plane), 227 HTTP headers, 7–9 bookmarks scripts, 7–9 design issues, 84–88 web server log, 6–7 sharing, 293 libraries, 4–5 books and publications maintainability, 28–33 Accessibility...: Problem—Design—Solution,95 menu bar “Architectural Styles and the Design of Net- creating, 10–12 work-based Software Architectures,” 194 populating, 12 Architecture of the World Wide Web, 194 structure of, 2 “Cool URIs don’t change,” 198 microformats, 29–30 HTTP (Hypertext Transfer Protocol) specifica- pages tions, 194 illustration, 3 URI (Uniform Resource Identifier) structure of, 2 specification, 194 proxies, 20 Web Content Accessibility Guidelines,95 query strings, 18 BPE4LAWS. See WS-BPEL. schemas, 23–24 broken links, 421. See also URIs (Uniform scripting languages, 5–6, 33–35 Resource Identifiers), maintenance. server side, 5 browser-based applications. See XAML (eXten- syndication formats, 5 sible Application Markup Language). technical architecture, 4–6 browsers. See also rich clients. technologies, 5 behavior, modifying with XUL, 182–184 transforming XML into (X)HTML, 30–33 directing to content, XUL, 180–182 URL space, defining, 34–35 drawbacks, 168 watches, 13–20 security issues, 168 web accessibility, 25–28 WHATWG (Web Hypertext Application Technol- web server interaction, 12–24 ogy Working Group), 142–143 XHTML, semantic information, 29–33 browsing source code, 174–175 business card example, 208–212 <button> element C OpenLaszlo, 173 C#, serving XML dynamic content over HTTP, XUL, 181 317–320 buttons C (Cubic Bézier curve) command, 135 OpenLaszlo, 173 Caesar shift encryption, 467–468 XForms, 145 callbacks, limiting, 92–93 Buy.com, 406 calls, REST services, 291 BuzzWatch <canvas> element, 172–173 aggregation, 2 Cascading Style Sheets (CSS). See CSS application tasks, 9–10 (Cascading Style Sheets). client side, 4–5 case management example, 288–292 498 22_087889 bindex.qxp 10/19/06 4:04 PM Page 499 content encoding, RSS 2.0 Index categories of mashups, 402, 405 MailEntryCollector implementation, CDATA sections, 230 396–400 change management, URIs, 425–428 MessageReader interface, 396 channels overview, 389–390 Blogs, 274 readMessage method, 399–400 microformats, 274 going live, 389 channels, syndication running the application, 388–389 Atom service character data, XML, 224–225 Apache Abdera toolkit, 374–375 character encoding application architecture, 374 serving XML over HTTP, 310 feed reader, 373 XHTML, 46–47 user interface, 372–373 XML, 227–229 Atom service, code overview classified ads, microformats, 272 AtomServlet.java class, 375, 377–383 clearFeed method, 384 clearFeed method, 384 Client Error responses, 207–208 clearing the feed, 376 client side applications, 4–5 compare method, 384–385 client-server pattern, 195 core files, 375 client-side transformation, 343–348 createEntry method, 387 Close path (Z) command, 135 createFeed method, 385–386 code points, XML, 227 isEntryInFeed method, 387 code security loadFeed method, 386 data overflow, 482 MailClient.java class, 375 definition, 460 MailEntryCollector.java class, 375 general principles, 479–482 MessageReader.java class, 375 SQL injection, 479–481 Settings.java class, 375, 388 XSS (cross-site scripting), 481–482 sortEntries method, 384 collections, URI maintenance, 423–424 Utils.java class, 375, 383–388 color writeTo method, 386–387 accessibility issues, 96–99 Atom service, e-mail support SVG, 140 MailClient.java class, 393–396 combining multiple requests, 91–92 MailEntryCollector implementation, community microformats, 273–274 396–400 compare method, 384–385 MessageReader interface, 396 compile options, OpenLaszlo, 176 readMessage method, 399–400 compiling syndication channels, 388–389 compiling, 388–389 compound microformats, 271–272 deploying, 388–389 concise communication, 90–91 e-mail for confidentiality,
Recommended publications
  • Jersey 1.8 User Guide Jersey 1.8 User Guide Table of Contents

    Jersey 1.8 User Guide Jersey 1.8 User Guide Table of Contents

    Jersey 1.8 User Guide Jersey 1.8 User Guide Table of Contents Preface ............................................................................................................................ ix 1. Getting Started ............................................................................................................... 1 1.1. Creating a root resource ........................................................................................ 2 1.2. Deploying the root resource ................................................................................... 3 1.3. Testing the root resource ....................................................................................... 3 1.4. Here's one Paul created earlier ................................................................................ 4 2. Overview of JAX-RS 1.1 ................................................................................................. 5 2.1. Root Resource Classes .......................................................................................... 5 2.1.1. @Path ...................................................................................................... 5 2.1.2. HTTP Methods .......................................................................................... 6 2.1.3. @Produces ................................................................................................ 7 2.1.4. @Consumes .............................................................................................. 9 2.2. Deploying a RESTful Web Service .........................................................................
  • Hidden Meaning

    Hidden Meaning

    FEATURES Microdata and Microformats Kit Sen Chin, 123RF.com Chin, Sen Kit Working with microformats and microdata Hidden Meaning Programs aren’t as smart as humans when it comes to interpreting the meaning of web information. If you want to maximize your search rank, you might want to dress up your HTML documents with microformats and microdata. By Andreas Möller TML lets you mark up sections formats and microdata into your own source code for the website shown in of text as headings, body text, programs. Figure 1 – an HTML5 document with a hyperlinks, and other web page business card. The Heading text block is H elements. However, these defi- Microformats marked up with the element h1. The text nitions have nothing to do with the HTML was originally designed for hu- for the business card is surrounded by meaning of the data: Does the text refer mans to read, but with the explosive the div container element, and <br/> in- to a person, an organization, a product, growth of the web, programs such as troduces a line break. or an event? Microformats [1] and their search engines also process HTML data. It is easy for a human reader to see successor, microdata [2] make the mean- What do programs that read HTML data that the data shown in Figure 1 repre- ing a bit more clear by pointing to busi- typically find? Listing 1 shows the HTML sents a business card – even if the text is ness cards, product descriptions, offers, and event data in a machine-readable LISTING 1: HTML5 Document with Business Card way.
  • The Girlboss Guide to Killing It Online & Making an Impact in the Digital Space

    The Girlboss Guide to Killing It Online & Making an Impact in the Digital Space

    AN INTRODUCTORY GUIDE TO MAKING YOUR MARK IN THE DIGITAL SPACE FOR GIRBOSSES, BLOGGERS AND CREATIVES. By Dani Watson A N I N T R O T O M A K I N G Y O U R M A R K O N L I N E B Y D A N I W A T S O N WITH THE AMOUNT OF COMPETITION IN THE ONLINE WORLD, IT CAN BE AN OVERWHELMING TASK TO THINK ABOUT HOW YOU ARE EVER GOING TO MAKE YOU AND YOUR BRAND STAND OUT FROM THE NOISE. WHETHER YOU'RE A BUSINESS LOOKING TO LAUNCH ONLINE, A BLOGGER WHO WANTS TO TURN THEIR BLOG INTO A FULL TIME INCOME OR A BRAND THAT IS LOOKING TO ELEVATE ITS PRESENCE IN THE DIGITAL SPACE, ITS ALL ABOUT FINDING AND CONNECTING WITH YOUR CLIQUE AND ONCE YOU DO, LOVING THEM HARD. I AM A FIRM BELIEVER THAT WHENEVER YOU ARE LOOKING TO CREATE AN INCOME ONLINE, THE COMMUNITY COMES BEFORE THE SELL. PEOPLE HAVE TO KNOW, LIKE AND TRUST YOU BEFORE THEY ARE WILLING TO INVEST. THIS IS WHY IT IS SO IMPORTANT TO BE THINKING ABOUT CREATING NOT ONLY YOUR PRODUCTS/ SERVICES/BLOG, BUT FIGURING OUT WAYS TO MAKE PEOPLE FALL IN LOVE WITH YOU AND YOUR BRAND SO THEY BUY WHATEVER IT IS YOU SELL. I AM SOMEONE WHO THOROUGHLY UNDERSTANDS THE IMPORTANCE OF FINDING YOUR TRIBE ONLINE AND BECOMING KNOWN FOR WHAT YOU DO AS THIS IS EXACTLY WHAT I HAVE BEEN ABLE TO DO WITH MY OWN BUSINESS AND BRAND. WHAT STARTED OFF AS A SMALL BLOG AND SOCIAL MEDIA CONSULTANCY HAS QUICKLY DEVELOPED INTO AN ONLINE EMPIRE THAT SHOWS NO SIGNS OF SLOWING DOWN.
  • Opening Plenary State of the Feather

    Opening Plenary State of the Feather

    Opening Plenary Lars Eilebrecht V.P., Conference Planning at ASF and Lead for ApacheCon Europe 2009 State of the Feather Jim Jagielski Chairman, The Apache Software Foundation Welcome to Amsterdam Presented by The Apache Software Foundation Produced by Stone Circle Productions, Inc. Conference Program • Detailed conference program guide available as a PDF from the ApacheCon Web site – www.eu.apachecon.com • Printed Conference-at-a- Glance program available at registration desk Presentations • 4 Tracks every day starting at 9:00 • Presentation slides provided by speakers will be made available on the ApacheCon Web site during the conference Wednesday Special Events • 9:15-9:30: Jim Jagielski “State of the Feather” • 9:30-10:30: Raghu Ramakrishnan “Data Management in the Cloud” • 10:30-11:30: Arjé Cahn, Ajay Anand, Steve Loughran, and Mark Brewer “Panel: The Business of Open Source”, moderated by Sally Khudairi • 13:00-14:00: Lars Eilebrecht “Behind the Scenes of The ASF” Wednesday Special Events • 18:30-20:00: Welcome Reception and ASF 10th Anniversary Party – Celebrating a Decade of Open Source Leadership • 19:30: OpenPGP Key Signing – [email protected] – moderated by Jean-Frederic Clere Thursday Special Events • 13:00-14:00: Jim Jagielski “Sponsoring the ASF at the Corporate and Individual Level” • 17:30-18:30: James Governor “Open Sourcing The Analyst Business – Turning Prop. Knowledge Inside Out” • 18:30-20:00: “Lightning Talks”, mod. by Danese Cooper and Rich Bowen Friday Special Events • 11:30-13:00: Lars Eilebrecht, Dirk- Willem van Gulik, Jim Jagielski, Sally Khudairi, Cliff Skolnick, “Apache Pioneer's Panel – 10 years of the ASF”, mod.
  • Le Microformat Hproduct C'est Quoi ? Pourquoi Utiliser Le Microformat

    Le Microformat Hproduct C'est Quoi ? Pourquoi Utiliser Le Microformat

    Apprendre à utiliser les microformats : hProduct 2017-02-21 23:02:01 Nicolaseo Le microformat hProduct c’est quoi ? hProduct est un microformat approprié pour publier et embarquer les données de vos produits. C’est une sorte de méta tags qui permet de structurer vos données pour permettre aux robots des moteurs de recherche de mieux référencer votre contenu. Pourquoi utiliser le microformat hProduct Le microformat hProduct est basé sur un ensemble de champs très important pour communiquer avec les robots des moteurs de recherche comme Google. Utiliser les {meta- tags|richsnippets|microformats} (et tout ce qui peut permettre aux moteurs de recherche de mieux classer votre contenu) vous apportera plus de visibilité sur internet grâce à un meilleur référencement de votre site et de son contenu. Comment utiliser le microformat hProduct Le schéma hProduct se compose de ce qui suit : hproduct brand. optionnel. texte. peut aussi utiliser hCard pour les fabricants. category. optionnel. texte. peut aussi utiliser rel-tag. ré-utilisé à partir de hCard. price. optionnel. floating point number. peut utiliser un format de devise. description. optionnel. texte. peut aussi inclure un marquage HTML valide. réutilisé à partir de hReview. fn. requis. texte. nom du produit ou titre. réutilisé de hCard. photo. optionnel. élément image ou lien. réutilisé de hCard. url. optionnel. href. peut contenir rel-tag rel=’product’. ré-utilisé de hCard. review. optionnel. hReview, ou hReview-aggregate. listing. optionnel. hListing, ou hListing-aggregate. identifier. optionnel. type. requis. – exemples : model mpn upc isbn issn ean jan sn vin sku value. requis. – l’étiquette peut être implicite. Détails des champs du microformat hProduct Les noms de classe category, fn, photo, url sont réutilisés à partir de hCard.
  • Return of Organization Exempt from Income

    Return of Organization Exempt from Income

    OMB No. 1545-0047 Return of Organization Exempt From Income Tax Form 990 Under section 501(c), 527, or 4947(a)(1) of the Internal Revenue Code (except black lung benefit trust or private foundation) Open to Public Department of the Treasury Internal Revenue Service The organization may have to use a copy of this return to satisfy state reporting requirements. Inspection A For the 2011 calendar year, or tax year beginning 5/1/2011 , and ending 4/30/2012 B Check if applicable: C Name of organization The Apache Software Foundation D Employer identification number Address change Doing Business As 47-0825376 Name change Number and street (or P.O. box if mail is not delivered to street address) Room/suite E Telephone number Initial return 1901 Munsey Drive (909) 374-9776 Terminated City or town, state or country, and ZIP + 4 Amended return Forest Hill MD 21050-2747 G Gross receipts $ 554,439 Application pending F Name and address of principal officer: H(a) Is this a group return for affiliates? Yes X No Jim Jagielski 1901 Munsey Drive, Forest Hill, MD 21050-2747 H(b) Are all affiliates included? Yes No I Tax-exempt status: X 501(c)(3) 501(c) ( ) (insert no.) 4947(a)(1) or 527 If "No," attach a list. (see instructions) J Website: http://www.apache.org/ H(c) Group exemption number K Form of organization: X Corporation Trust Association Other L Year of formation: 1999 M State of legal domicile: MD Part I Summary 1 Briefly describe the organization's mission or most significant activities: to provide open source software to the public that we sponsor free of charge 2 Check this box if the organization discontinued its operations or disposed of more than 25% of its net assets.
  • A Method to Analyze Multiple Social Identities in Twitter Bios

    A Method to Analyze Multiple Social Identities in Twitter Bios

    A Method to Analyze Multiple Social Identities in Twitter Bios ARJUNIL PATHAK, University at Buffalo, USA NAVID MADANI, University at Buffalo, USA KENNETH JOSEPH, University at Buffalo, USA Twitter users signal social identity in their profile descriptions, or bios, in a number of important but complex ways that are not well-captured by existing characterizations of how identity is expressed in language. Better ways of defining and measuring these expressions may therefore be useful both in understanding howsocial identity is expressed in text, and how the self is presented on Twitter. To this end, the present work makes three contributions. First, using qualitative methods, we identify and define the concept of a personal identifier, which is more representative of the ways in which identity is signaled in Twitter bios. Second, we propose a method to extract all personal identifiers expressed in a given bio. Finally, we present a series of validation analyses that explore the strengths and limitations of our proposed method. Our work opens up exciting new opportunities at the intersection between the social psychological study of social identity and the study of how we compose the self through markers of identity on Twitter and in social media more generally. CCS Concepts: • Applied computing Sociology; Additional Key Words and Phrases: Twitter, self-presentation, social identity, computational social science ACM Reference Format: Arjunil Pathak, Navid Madani, and Kenneth Joseph. 2018. A Method to Analyze Multiple Social Identities in Twitter Bios. J. ACM 37, 4, Article 111 (August 2018), 35 pages. https://doi.org/10.1145/1122445.1122456 1 INTRODUCTION A social identity is a word or phrase that refers to a particular social group (e.g.
  • Where Is the Semantic Web? – an Overview of the Use of Embeddable Semantics in Austria

    Where Is the Semantic Web? – an Overview of the Use of Embeddable Semantics in Austria

    Where Is The Semantic Web? – An Overview of the Use of Embeddable Semantics in Austria Wilhelm Loibl Institute for Service Marketing and Tourism Vienna University of Economics and Business, Austria [email protected] Abstract Improving the results of search engines and enabling new online applications are two of the main aims of the Semantic Web. For a machine to be able to read and interpret semantic information, this content has to be offered online first. With several technologies available the question arises which one to use. Those who want to build the software necessary to interpret the offered data have to know what information is available and in which format. In order to answer these questions, the author analysed the business websites of different Austrian industry sectors as to what semantic information is embedded. Preliminary results show that, although overall usage numbers are still small, certain differences between individual sectors exist. Keywords: semantic web, RDFa, microformats, Austria, industry sectors 1 Introduction As tourism is a very information-intense industry (Werthner & Klein, 1999), especially novel users resort to well-known generic search engines like Google to find travel related information (Mitsche, 2005). Often, these machines do not provide satisfactory search results as their algorithms match a user’s query against the (weighted) terms found in online documents (Berry and Browne, 1999). One solution to this problem lies in “Semantic Searches” (Maedche & Staab, 2002). In order for them to work, web resources must first be annotated with additional metadata describing the content (Davies, Studer & Warren., 2006). Therefore, anyone who wants to provide data online must decide on which technology to use.
  • Content Management Interoperability Services (CMIS)

    Content Management Interoperability Services (CMIS)

    Content Management Interoperability Services (CMIS) CMIS (Content Management Interoperability Services) is a standard for improving interoperability between ECM systems. It specifies a domain model plus a set of services and protocol bindings for Web Services (SOAP) and AtomPub. You can get more detail on what CMIS is from OASIS. Documentation Note: This page needs to be updated for Alfresco 4 The most current documentation on using CMIS in Alfresco is available at: https://developer.alfresco.com/ and http://docs.alfresco.com There is also a book on the topic called CMIS and Apache Chemistry in Action. History The latest published CMIS 1.0 Committee Specification 01. Keep up-to-date Cover Pages blog posts twitter press. On May 3rd, 2010, Mary McRae announced CMIS as an approved OASIS Standard. On April 16, 2010, OASIS initiated a Call For Vote (which closes April 30) to approve the CMIS Committee Specification as an OASIS standard. On April 9, 2010, Alfresco released Alfresco Community 3.3 with full support for CMIS 1.0 CD07. On March 12, 2010, the CMIS technical committee approved and submitted CMIS 1.0 Committee Draft CD07 to OASIS for consideration as an OASIS standard. From wiki.alfresco.com/wiki/CMIS 1 On January 28, 2010, CMIS entered its second Public Review, which closed on February 12, 2010. On October 23, 2009, CMIS entered its first Public Review, which closed on December 22, 2009. On August 18, 2009, Alfresco provided http://cmis.alfresco.com, a hosted version of its CMIS repository and TCK. On October 06, 2008, OASIS issued a public call for participation in a new technical committee chartered to define specifications for use of Web services and Web 2.0 interfaces to enable information sharing across content management repositories from different vendors.
  • Microformats the Next (Small) Thing on the Semantic Web?

    Microformats the Next (Small) Thing on the Semantic Web?

    Standards Editor: Jim Whitehead • [email protected] Microformats The Next (Small) Thing on the Semantic Web? Rohit Khare • CommerceNet “Designed for humans first and machines second, microformats are a set of simple, open data formats built upon existing and widely adopted standards.” — Microformats.org hen we speak of the “evolution of the is precisely encoding the great variety of person- Web,” it might actually be more appropri- al, professional, and genealogical relationships W ate to speak of “intelligent design” — we between people and organizations. By contrast, can actually point to a living, breathing, and an accidental challenge is that any blogger with actively involved Creator of the Web. We can even some knowledge of HTML can add microformat consult Tim Berners-Lee’s stated goals for the markup to a text-input form, but uploading an “promised land,” dubbed the Semantic Web. Few external file dedicated to machine-readable use presume we could reach those objectives by ran- remains forbiddingly complex with most blog- domly hacking existing Web standards and hop- ging tools. ing that “natural selection” by authors, software So, although any intelligent designer ought to developers, and readers would ensure powerful be able to rely on the long-established facility of enough abstractions for it. file transfer to publish the “right” model of a social Indeed, the elegant and painstakingly inter- network, the path of least resistance might favor locked edifice of technologies, including RDF, adding one of a handful of fixed tags to an exist- XML, and query languages is now growing pow- ing indirect form — the “blogroll” of hyperlinks to erful enough to attack massive information chal- other people’s sites.
  • Sociolinguistically Driven Approaches for Just Natural Language Processing

    Sociolinguistically Driven Approaches for Just Natural Language Processing

    University of Massachusetts Amherst ScholarWorks@UMass Amherst Doctoral Dissertations Dissertations and Theses April 2021 Sociolinguistically Driven Approaches for Just Natural Language Processing Su Lin Blodgett University of Massachusetts Amherst Follow this and additional works at: https://scholarworks.umass.edu/dissertations_2 Part of the Artificial Intelligence and Robotics Commons Recommended Citation Blodgett, Su Lin, "Sociolinguistically Driven Approaches for Just Natural Language Processing" (2021). Doctoral Dissertations. 2092. https://doi.org/10.7275/20410631 https://scholarworks.umass.edu/dissertations_2/2092 This Open Access Dissertation is brought to you for free and open access by the Dissertations and Theses at ScholarWorks@UMass Amherst. It has been accepted for inclusion in Doctoral Dissertations by an authorized administrator of ScholarWorks@UMass Amherst. For more information, please contact [email protected]. SOCIOLINGUISTICALLY DRIVEN APPROACHES FOR JUST NATURAL LANGUAGE PROCESSING A Dissertation Presented by SU LIN BLODGETT Submitted to the Graduate School of the University of Massachusetts Amherst in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY February 2021 College of Information and Computer Sciences © Copyright by Su Lin Blodgett 2021 All Rights Reserved SOCIOLINGUISTICALLY DRIVEN APPROACHES FOR JUST NATURAL LANGUAGE PROCESSING A Dissertation Presented by SU LIN BLODGETT Approved as to style and content by: Brendan O’Connor, Chair Mohit Iyyer, Member Hanna Wallach, Member Lisa Green, Member James Allan, Chair of the Faculty College of Information and Computer Sciences ACKNOWLEDGMENTS First and foremost, I would like to thank my advisor, Brendan O’Connor, who introduced me to natural language processing and computational sociolinguistics, taught me more than I can say about research, NLP, and writing, and has been endlessly supportive of my many and growing research interests; I consider myself amazingly lucky to have stumbled into his lab.
  • Avaliando a Dívida Técnica Em Produtos De Código Aberto Por Meio De Estudos Experimentais

    Avaliando a Dívida Técnica Em Produtos De Código Aberto Por Meio De Estudos Experimentais

    UNIVERSIDADE FEDERAL DE GOIÁS INSTITUTO DE INFORMÁTICA IGOR RODRIGUES VIEIRA Avaliando a dívida técnica em produtos de código aberto por meio de estudos experimentais Goiânia 2014 IGOR RODRIGUES VIEIRA Avaliando a dívida técnica em produtos de código aberto por meio de estudos experimentais Dissertação apresentada ao Programa de Pós–Graduação do Instituto de Informática da Universidade Federal de Goiás, como requisito parcial para obtenção do título de Mestre em Ciência da Computação. Área de concentração: Ciência da Computação. Orientador: Prof. Dr. Auri Marcelo Rizzo Vincenzi Goiânia 2014 Ficha catalográfica elaborada automaticamente com os dados fornecidos pelo(a) autor(a), sob orientação do Sibi/UFG. Vieira, Igor Rodrigues Avaliando a dívida técnica em produtos de código aberto por meio de estudos experimentais [manuscrito] / Igor Rodrigues Vieira. - 2014. 100 f.: il. Orientador: Prof. Dr. Auri Marcelo Rizzo Vincenzi. Dissertação (Mestrado) - Universidade Federal de Goiás, Instituto de Informática (INF) , Programa de Pós-Graduação em Ciência da Computação, Goiânia, 2014. Bibliografia. Apêndice. Inclui algoritmos, lista de figuras, lista de tabelas. 1. Dívida técnica. 2. Qualidade de software. 3. Análise estática. 4. Produto de código aberto. 5. Estudo experimental. I. Vincenzi, Auri Marcelo Rizzo, orient. II. Título. Todos os direitos reservados. É proibida a reprodução total ou parcial do trabalho sem autorização da universidade, do autor e do orientador(a). Igor Rodrigues Vieira Graduado em Sistemas de Informação, pela Universidade Estadual de Goiás – UEG, com pós-graduação lato sensu em Desenvolvimento de Aplicações Web com Interfaces Ricas, pela Universidade Federal de Goiás – UFG. Foi Coordenador da Ouvidoria da UFG e, atualmente, é Analista de Tecnologia da Informação do Centro de Recursos Computacionais – CERCOMP/UFG.