Senin, 24 Oktober 2011
Web document
07.28 |
Diposting oleh
Unknown
A web document is similar in concept to a web page, but also satisfies the following broader (W3C) definition:
- "... Every Web document has its own URI. Note that a Web document is not the same as a file: a single Web document can be available in many different formats and languages, and a single file, for example a PHP script, may be responsible for generating a large number of Web documents with different URIs. A Web document is defined as something that has a URI and can return representations (responses in a format such as HTML or JPEG or RDF) of the identified resource in response to HTTP requests. In technical literature ... the term Information Resource is used instead of Web document.".[1]
The term "web document" has been used as a fuzzy term in many sources (see ,[2] ,[3] ,[4] ,[5] ,[6] and others), but in all of them the W3C definition given above applies. Recent research in fields like "Web Document Retrieval" and "Web Document Analysis" (see p. ex.,[7] ,[8] ,[9] ,[10] ,[11] [12]) has revived interest in clarifying the correct use of the term.
The key idea is that a single underlying resource in an HTTP system, may have several different representations, which can be exposed by mechanisms such as content negotiation.
Label:
Web document
Langganan:
Posting Komentar (Atom)
Statistik
Translate
Blog Archive
-
▼
2011
(1064)
-
▼
Oktober
(834)
-
▼
Okt 24
(256)
- Etymology of the word
- Modeling
- Animation
- Rendering
- form•Z on the small and big screen
- Overview
- History
- Transporter
- Modeler
- Product family
- Drafting Assistant
- Animation tools
- Surfacing
- Cobalt (CAD program)
- There is no one way to practice design methods. Jo...
- Current State of Design Methods
- Significance of Design Management
- Proliferation of Information Technologies
- Significance of Proliferation of Information Techn...
- Significance of Emergence of Design Research and D...
- Professional Design Practice
- Significance of Role of Professional Design Practice
- Design Management
- Alternative View
- Background of Design Methods
- Where Process Meets Method
- Emergence of Design Research and Design Studies
- Design methods
- Globalization and governance controversy
- Internet governance
- Formation and growth of the network
- Governors
- Roles
- Elements
- Principle 4: Ensure separation of project governan...
- Additional and complementary principles of governa...
- Additional principles exist where projects are mul...
- Principle 1: Ensure a single point of accountabili...
- Principle 2: Service delivery ownership determines...
- Principle 3: Ensure separation of stakeholder mana...
- Project governance
- Three pillars of project governance
- Professional certification
- Frameworks
- Problems with IT governance
- Corporate governance of information technology
- Definitions
- Background
- Domination by large organizations
- Administration
- Membership
- Recommendations and Certifications
- History
- Areas of responsibility
- Website management team
- Governance models
- World Wide Web Consortium
- Webmaster
- Website governance
- Effective separation
- Flexible presentation
- Reusability
- Web template
- Template uses
- History
- Web syndication as a commercial model
- Web syndication and e-commerce
- Web syndication
- Motivation
- Representational state transfer (REST)
- Automated design methodologies
- Criticisms
- Big Web services
- Web API
- Remote procedure calls
- Service-oriented architecture
- Web service
- Web document
- Advanced
- Security Considerations
- Client Side + Server Side
- Basic
- Web development as an industry
- Client Side Coding
- Server Side Coding
- Best practices
- Changes and updates
- Web development
- Web design
- Advantages
- Disadvantages
- Web content management system
- Capabilities
- Online processing (called "frying" systems)
- Role of information management
- Four stages
- Five stages
- Governance rather than workflow
- Web content lifecycle
- Career
-
▼
Okt 24
(256)
-
▼
Oktober
(834)
0 komentar:
Posting Komentar