Skip to main content

Home/ Diigo Community/ Group items matching "xml" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
2More

XML Parsing using NSXMLParse in Swift - 0 views

www.theappguruz.com/...parsing-using-nsxmlparse-swift NSXMLParsing in Swift
shared by TheAppGuruz on 18 Nov 14 - No Cached
  • TheAppGuruz on 18 Nov 14
     
    NSXMLParse is a main class of XML parsing. NSXMLParse is XML Parser, inbuilt class and SAX Parser. It calls the parser delegate method.
  • TheAppGuruz on 18 Nov 14
     
    NSXMLParse is a main class of XML parsing. NSXMLParse is XML Parser, inbuilt class and SAX Parser. It calls the parser delegate method.
2More

Unity - XML PARSING IN UNITY - 0 views

www.theappguruz.com/...unity-xml-parsing-unity xml parsing in unity3d
shared by TheAppGuruz on 24 Sep 14 - No Cached
  • TheAppGuruz on 24 Sep 14
     
    The main objective of this blog is to show how to do XML Parsing in unity.
  • TheAppGuruz on 24 Sep 14
     
    The main objective of this blog is to show how to do XML Parsing in unity.
2More

Cyn City: Web 2.0--very fun & informative - 3 views

cyncity.typepad.com/...web_20_the_mach.html diigo review video
shared by Maggie Tsai on 13 Mar 07 - Cached
hudaghaly liked it
  • Text is linear Text is unlinear Text is said to be unlinear Text is often said to be unlinear Text is unlinear when written on paper Digital text is different. Digital text is more flexible. Digital text is moveable. Digital text is above all…hyper. Digital hypertext is above all… hypertext is above all… hypertext can link hypertext can link here here or here… virtually anywhere anywhere virtually anywhere virtual The WayBack Machine http://yahoo.com Take Me Back Oct 17, 1996 Yahoo View Source Most early websites were written in HTML HTML HTML was designed to define the structure of a web document. p is a structural element referring to “paragraph” LI LI is also a structural element referring to “List Item” As HTML expanded, more elements were added. Including stylistic elements like B for bold and I for italics Suck elements defined how content would be formatted. In other words, form and content became inseparable in HTML Digital Text can do better. Form and content can be separated. http://www.cnn.com RSS XML View Source XML was designed to do just that. http://www.cnn.com/?eref=rss_topstories same withCNN.com and and virtually all other elements in this document. They describe the content, not the form. So the data can be exported, free of formatting constraints. Latest News Anthro Blogs (124) Savage Minds 8apps: Social Networking for Productive People WORLD CHANGING ANOTHER WORLD IS HERE Antrho Journals (124) University of California Press Journals Digital Publishing Current Anthropology AESonline.org Google With form separated from content, users did not need to know complicated code to upload content to the web, I’m Feeling Lucky Create Blog Name Your Blog Beyond Etext http://beyondetext.blogspot.com Choose a template Your blog has been created! Monday, January 29, 2007 Hello World! POSTED BY PROFESSOR WESCH AT 8:14 PM 0 COMMENTS There’s a blog born every half second and it’s not just text…Search YouTube Broadcast Yourself This is a video response to The Beauty of Being Human flickr Ahoy mwesch! Upload Photos Anthropology club Created by you. KSU Anthropology club Club Photos Google XML facilitates automated data exchange font-size: 14px; font-f
  • anonymous on 02 Oct 13
     
    Most quality online stores. Know whether you are a trusted online retailer in the world. Whatever we can buy very good quality. and do not hesitate. Everything is very high quality. Including clothes, accessories, bags, cups. Highly recommended. This is one of the trusted online store in the world. View now www.retrostyler.com
1More

Cognos Framework Manager - ABC LEARN - 0 views

www.abclearn.com/...cognos-framework-manager cognos ibm tutorials
shared by abclearn on 27 Feb 17 - No Cached
  • abclearn on 27 Feb 17
     
    Getting started with Cognos Framework Manager Framework Manager is a metadata modeling tool that drives query generation for IBM Cognos software. A model is a collection of metadata that includes physical information and business information for one or more data sources. Whenever we start creating a model, we need to understand the requirement first and then we can choose whether to go for star schema or snowflake schema or just a relational schema. While creating a framework manager metadata model we will come across the below terms: Project: A project contains a model, namespaces, packages, data sources, and related information for maintaining and sharing model information. The project will be saved as a .cpf file and an XML file which defines the project. Different terms associated with Framework Manager: Models: Model contains your dimension tables, fact tables, and the related join information. A framework manager model is a metadata layer between your database and the reporting applications. Using Model, we can create dimension tables, fact tables and even create filters. Namespace: A namespace uniquely identifies query items, dimensions, query subjects, and other objects. You import different databases into separate namespaces to avoid duplicate names. Packages: A package is a subset of the dimensions, query subjects, and other objects defined in the project. A package is what is actually published to the IBM Cognos BI server, and it is used to create reports, analyses, and ad hoc queries. Dimensions: A dimension is a broad grouping of data about a major aspect of a business, such as products, dates, or markets. Query Subjects: A query subject is a set of query items that have an inherent relationship. In most cases, query subjects behave like tables. Query subjects produce the same set of rows regardless of which columns were queried. There are different types of query subjects which we can learn going further. Query Items: A query it
31More

ODF versus OOXML: Don't forget about HTML! - O'Reilly XML Blog - 0 views

www.oreillynet.com/...ersus_ooxml_dont_forget_a.html ODF OOXML PDF HTML gpd4
shared by Graham Perrin on 28 Jul 09 - Cached
  • Don't forget about HTML
  • February 25, 2007
  • HTML’s potential and actual suitability for much document interchange
  • ...27 more annotations...
  • HTML is the format to consider first
  • validated, standards compliant XHTML in particular
  • HTML at one end (simple WP documents)
  • PDF at the other end (full page fidility but read-only)
  • W3C versus ISO
  • HTML, ODF, OOXML, PDF
  • Lie adopts an extreme view towards overlap of standards:
  • overlap at all brings nothing but misery and bloat.
  • The next dodgy detail is to make blanket comparisons between HTML and ODF/OOXML.
  • ODF and OOXML deal with many issues that HTML/CSS simply does not.
  • the W3C argument might be to say that every part should have a URL
  • a strange theory that MS wants ODF and OOXML to both fail
  • being pro-ODF does not mean you have have to be anti-OOXML
  • HTML is the format ｏｆ choice for interchange of simple documents
  • ODF will evolve to be the format of choice for more complicated documents
  • OOXML is the format of choice for full-fidelity dumps from MS Office
  • PDF is the format of choice for non-editable page-faithful documents
  • all have overlap
  • we need to to encourage a rich library of standard technologies,
  • widely deployed,
  • free,
  • unencumbered,
  • explicit,
  • awareness of when each is appropriate
  • an adequate set of profiles and profile validators
  • using ISO Schematron
  • Plurality
  • Graham Perrin on 28 Jul 09
     
    Relevance to Diigo Community: of the four formats (HTML, ODF, OOXML, PDF) mentioned in this 2007 post, HTML is clearly most suitable for services/software such as Diigo.
1 - 20 of 68 Next › Last »
Showing 20▼ items per page