DOCSLIB.ORG

Guidance for the Production of MEDIN Metadata

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Guidance for the Production of MEDIN Metadata Title Guidance notes for the production of discovery metadata for the Marine Environmental Data and Information Network (MEDIN) MEDIN Discipline Discovery Metadata Author(s) Becky Seeley (DASSH), James Rapaport, (SeaZone), Olivia Merritt (SeaZone), Mark Charlesworth (BODC), Sean Gaffney (BODC). Document Owner Marine Environmental Data Information Network (MEDIN) Standards Working Group Licence This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/ or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042, USA. Reviewed by MEDIN Standards Working Group Date reviewed 18 May 2020 Version 3.1 Date approved and 08 July 2020 published on MEDIN website Date last checked for 08 July 2020 accuracy Summary The discovery metadata standard for resources submitted to the Marine Environmental Data Information Network. Keywords Discovery Metadata Metadata standards are evolving at an international level and these guidelines are therefore subject to change. It is recommended that you use a download of this document from the Marine Environmental Data and Information Network (MEDIN) website (www.medin.org.uk) rather than storing a local copy. A log of changes will be available on the website. 1 Change History Version Author Date of last Status revision Interim Draft BS 2008-12-20 Draft for comment 1.0 Interim Draft BS 2009-31-01 Draft for comment 1.1 Interim Draft BS 2009-22-02 Final Draft 1.2 Interim Version BS 2009-03-19 First interim release 2.0 Interim Version MC 2009-03-27 Minor edits to test 2.1 Interim Version BS 2009-03-31 Mapped to 19115 2.2 Interim Version BS 2009-05-07 Updated WRT INSPIRE and GEMINI 2 2.3 Public OM & JR 2009-05-20 SeaZone Review Standard 2.3.1 Public MC 2009-10-01 Updated to reflect changes in GEMINI 2. Standard 2.3.2 Public MC 2010-01-27 Some small tweaks following discussions Standard 2.3.3 to 2010-03-11 within MEDIN and GEMINI 2 and extra guidance on spatial resolution and URIs and a refresh of xml examples Public MC/JR 17-11-2010 Some minor tweaks following changes to Standard 2.3.4 GEMINI 2.1 standard. New Element ‘Parent ID’ and explanation of file identifier added. Some cosmetic changes. Details of changes available on request. Public MC/JR 11-04-2011 Minor presentational changes to Standard 2.3.5 document. Changes to the way controlled vocabularies are encoded (see page 4) and the way end date is encoded if the resource is ongoing. Inclusion of sub element ‘Online resource function code’ and clarification of responsible party roles. Public MC 06-10-2011 Minor changes to follow changes in Standard 2.3.6 GEMINI 2. Geographic bounding box and temporal extant made multiple; date of publication made conditional to follow GEMINI 2. Public MC 14-04-2012 Minor changes: Clarification of encoding Standard 2.3.7 when resource end date is ongoing and of the N010 keyword. Some typos corrected. 2 Public CP 14-03-2013 Minor changes to the Guidance Notes. e.g. Standard 2.3.7 correcting typos, updating web addresses. No Changes to the standard. Public CP 29-10-2013 Minor changes to follow changes in Standard 2.3.8 GEMINI 2.2: Multiple occurrences of Unique Resource Identifier allowed, multiple occurrences of spatial reference system allowed. Some changes to Temporal extent to match GEMINI 2.2. Distributor made mandatory to match INSPIRE and GEMINI 2.2. Inserted sub element Equivalent scale to match INSPIRE guidance (NB difference between INSPIRE and GEMINI 2.2 in obligation of this element). Also updated links to NERC vocabulary server to reflect a change to NVS2.0. Public SG 08-03-2019 Update of MEDIN Discovery Standard to Standard 3.0 account for change from GEMINI 2.2 to GEMINI 2.3. See separate document ‘MEDIN_Discovery_Metadata_Standard_2 _3_8_to_3_0_Mar2019.pdf’ for details of changes. Public SG 08-07-2020 Clarifications on encoding and use of Standard 3.1 many metadata elements from AGI GEMINI Working Group. See separate document ‘MEDIN_Discovery_Metadata_Standard_3 _0_to_3_1_July2020.pdf’ for details of changes 3 MEDIN Elements 1. Introduction .................................................................................................. 7 2. Data Discoverability ..................................................................................... 7 2.1 Date and time formatting ......................................................................... 8 3. Using this document .................................................................................... 8 4. Filling in an element ..................................................................................... 9 5. Elements for identifying a resource .......................................................... 12 Element 1 - Resource title (M) ................................................................................... 12 Element 2 - Alternative resource title (O) ................................................................... 13 Element 3 - Resource abstract (M) ............................................................................ 14 Element 4 - Resource type (M) .................................................................................. 16 Element 31 – Hierarchy level name (C) ..................................................................... 17 Element 5 - Resource locator (C) .............................................................................. 18 Sub Element 5.1 - Resource locator URL (C) .......................................................... 18 Sub Element 5.2 - Resource locator name (O) ........................................................ 18 Sub Element 5.3 - Resource function (O) ................................................................ 18 Sub Element 5.4 - Resource locator description (C) ................................................ 18 Element 6 - Unique resource identifier (C) ................................................................ 21 Sub Element 6.1 - Code (M) .................................................................................... 22 Sub Element 6.2 - Code Space (O) ......................................................................... 22 Element 7 - Coupled resource (C) ............................................................................. 24 Element 8 - Resource language (C) .......................................................................... 25 6. Elements classifying spatial data and services ....................................... 26 Element 9 - Topic category (C) .................................................................................. 26 Element 10- Spatial data service type (C) ................................................................. 27 Element 32 – Spatial representation type (C) ............................................................ 27 Element 11 - Keywords (M) ....................................................................................... 28 Sub Element 11.1 - Keyword value (M) ................................................................... 29 Sub Element 11.2 - Originating controlled vocabulary (M) ....................................... 30 Element 12 - Geographic bounding box (C) .............................................................. 36 Sub element 12.1 - West bounding longitude (M) .................................................... 36 Sub element 12.2 - East bounding longitude (M) ..................................................... 36 Sub element 12.3 - North bounding latitude (M) ...................................................... 36 Sub element 12.4 - South bounding latitude (M) ..................................................... 37 Element 13 - Extent (O) ............................................................................................. 38 Sub element 13.1 - Extent name (M) ....................................................................... 38 Sub element 13.2 - Originating controlled vocabulary (M) ....................................... 39 Element 14 - Vertical extent information (C) .............................................................. 43 Sub element 14.1 - Minimum Value (M) ................................................................... 43 Sub element 14.2 - Maximum Value (M) .................................................................. 43 Sub element 14.3 - Vertical coordinate reference system (M) ................................. 43 Element 15 - Spatial reference system (M) ................................................................ 45 Sub element 15.1 - Code (M) .................................................................................. 45 Sub element 15.2 - Originating controlled vocabulary (O) ....................................... 45 Element 16 - Temporal reference (M) ........................................................................ 47 Sub element 16.1 - Date of publication (M) ............................................................. 47 Sub element 16.2 - Date of last revision (C) ............................................................ 48 4 Sub element 16.3 - Date of creation (C) .................................................................. 48 Sub element 16.4 - Temporal extent (C) .................................................................. 48 7. Elements describing data quality .............................................................. 52 Element 17 - Lineage (C) .......................................................................................... 52 Element
Load more

Recommended publications
  • Network Working Group T. Berners-Lee Request for Comments: 3986 W3C/MIT STD: 66 R
    Network Working Group T. Berners-Lee Request for Comments: 3986 W3C/MIT STD: 66 R. Fielding Updates: 1738 Day Software Obsoletes: 2732, 2396, 1808 L. Masinter Category: Standards Track Adobe Systems January 2005 Uniform Resource Identifier (URI): Generic Syntax Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2005). Abstract A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. Berners-Lee, et al. Standards Track [Page 1] RFC 3986 URI Generic Syntax January 2005 Table of Contents 1. Introduction . 4 1.1. Overview of URIs . 4 1.1.1. Generic Syntax . 6 1.1.2. Examples . 7 1.1.3. URI, URL, and URN . 7 1.2. Design Considerations .
    [Show full text]
  • Bibliography of Erik Wilde
    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
    [Show full text]
  • A Framework for Auto-ID Enabled Business
    A Framework for Auto-ID Enabled Business by Timothy Porter Milne M.S. Mechanical Engineering, 1995 Brigham Young University B.S. Mechanical Engineering, 1992 Brigham Young University Submitted to the Department of Mechanical Engineering in partial fulfillment of the requirements for the degree of MASTER OF SCIENCE at the MASSACHUSETTS INSTITUTE OF TECHNOLOGY MASSACHUSETTS INSTITUTEINSTITUTE August 8, 2003 OF TECHNOL OGY OCT 0 6 ©2003 Massachusetts Institute of Technology All Rights Reserved. LIBRAR IES Signature of Author:................................ ....... .. ............. Departm of Mechanic Engineering (V August 8, 2003 C ertified by:............................................... Sanjay E. Sarma Associat e Professor of Mechanical Engineering Thesis Supervisor A ccepted by:......................................... Ain A. Sonin Chairman, Department Committee on Graduate Students BARKER A Framework for Auto-ID Enabled Business by Timothy Porter Milne Submitted to the Department of Mechanical Engineering August 8, 2003 In partial fulfillment of the requirements for the degree of Master of Science ABSTRACT Modern commerce is as much about trading information as it is about exchanging goods and money. With an Auto-ID enabled future, the expeditious exchange of information will be even more critical. The fundamental problem with e-commerce today is the soft connection between goods and their related information, which frequently results in breakdowns between the physical and information worlds. The Auto-ID Center at MIT has proposed a system using Radio Frequency Identification (RFID) tags on objects, coupled with a distributed information system using the Internet, that will allow the tracking of physical objects and the automatic association of relevant data about those objects. This thesis outlines a framework for a new method of using Auto-ID to connect the physical world to the information world using an example from commerce: Shipping and Receiving Verification.
    [Show full text]
  • FAA-STD-075, Creating Service Identifiers
    FAA-STD-075 June 29, 2021 SUPERSEDING FAA-STD-063 May 1, 2009 U.S. Department of Transportation Federal Aviation Administration U.S. Department of Transportation Federal Aviation Administration Standard Practice CREATING SERVICE IDENTIFIERS FAA-STD-075 June 29, 2021 FOREWORD This standard is approved for use by all Departments of the Federal Aviation Administration (FAA). This standard sets forth requirements for creating globally-unique identifiers for FAA service-oriented architecture (SOA)-based services. This standard has been prepared in accordance with FAA-STD-068, Department of Transportation Federal Aviation Administration, Preparation of Standards [STD068]. Comments, suggestions, or questions on this document shall be addressed to: Federal Aviation Administration System Wide Information Management (SWIM) Program Office, AJM-316 800 Independence Avenue, SW Washington, DC 20591 https://www.faa.gov/air_traffic/technology/swim/contacts/ i FAA-STD-075 June 29, 2021 Table of Contents 1 SCOPE ..................................................................................................................................................1 1.1 INTRODUCTION ...........................................................................................................................................1 1.2 INTENDED AUDIENCE ....................................................................................................................................1 1.3 BASIC CONCEPTS .........................................................................................................................................2
    [Show full text]
  • Globally Unique Flight Identifier (GUFI) Format and Content
    Globally Unique Flight Identifier (GUFI) Format and Content A collaborative effort to establish the Flight Information Exchange Model (FIXM) has been underway for several years. A key component of the flight model is a Globally Unique Flight Identifier (GUFI) that is included on every Air Traffic Management (ATM) flight data transaction to unambiguously identify the flight to which the data applies. The June 23, purpose of the GUFI is to eliminate problems that have occurred in the past when 2014 systems try to accurately correlate data that is received from many other systems. This paper discusses the format and content of the GUFI. Version: 2.1 GUFI Format Version 2.1 Table of Contents Document History ........................................................................................................................................ 3 1 Introduction .......................................................................................................................................... 4 2 Background/Discussion ......................................................................................................................... 4 2.1 Purpose ..................................................................................................................................... 4 2.2 General Concept ....................................................................................................................... 4 2.3 General Approaches .................................................................................................................
    [Show full text]
  • Bookings of Westin Diplomat Bookings
    RESTful Web Applications with Spring 3.0 Arjen Poutsma Senior Software Engineer SpringSource Speaker’s qualifications • Fifteen years of experience in Enterprise Software Development • Six years of Web service experience • Development lead of Spring Web Services • Working on Spring 3.0 • Contributor to various Open Source frameworks: (XFire, Axis2, NEO, ...) SpringSource Confidential. Do not distribute without express permission Overview • RESTful URLs • URI templates • Content negotiation • HTTP method conversion • ETag support SpringSource Confidential. Do not distribute without express permission RESTful URLs Resources • URLs are unique identifiers for Resources • Typically nouns • Customer • Orders • Shopping cart URLs [scheme:][//authority][path][?query][#fragment] http://www.springsource.com https://mybank.com http://www.google.com/search?q=arjen %20poutsma http://java.sun.com/j2se/1.4.2/docs/api/java/lang/ String.html#indexOf(int) SpringSource Confidential. Do not distribute without express permission Paths • Represents hierarchy • Represents value for consumers • Collections on higher levels SpringSource Confidential. Do not distribute without express permission Example Path Description /hotels List of all hotels /hotels/westindiplomat Details of Westin Diplomat /hotels/westindiplomat/ List of bookings of Westin Diplomat bookings /hotels/westindiplomat/ Individual booking bookings/42584 No Hierarchy? Path Description maps/24.9195,17.821 Commas maps/24.9195;17.821 Semicolons Query Variables • Input for algorithms • Get ignored by proxies
    [Show full text]
  • Introduction to the Course
    Introduction to the course 1 Introduzione alla programmazione web – Marco Ronchetti 2021 – Università di Trento Prerequirements § OOP + Java: essential! (Must have passed Linguaggi di Programmazione!) § Network fundamentals § Database § No need to already know HTML/HTTP etc. 2 Introduzione alla programmazione web – Marco Ronchetti 2021 – Università di Trento Topics § HTTP + HTML + CSS § Server side programming: PHP – Java, parameter passing, state problem… § Data access (DB) § Javascript – EcmaScript – Typescript § Patterns: MV* + … § AJAX/XML/JSON § JS frameworks/libraries: JQuery, (brief remarks on React, Angular…) § General considerations (accessibility, security…) 3 Introduzione alla programmazione web – Marco Ronchetti 2021 – Università di Trento We’ll use Piazza As soon as the dept Buys the licence For now we go with moodle (sigh) 4 Introduzione alla programmazione web – Marco Ronchetti 2021 – Università di Trento Exam § Similar to “Linguaggi di Programmazione – mod.1” § 1st part: output prediction of 8 brief code fragments + 8 true/fase questions (40 minutes) § 2nd part: small project development (4 hours) If possiBle, in presence. Else, Responsus+Moodle+VDI 5 Introduzione alla programmazione web – Marco Ronchetti 2021 – Università di Trento 6 Introduzione alla programmazione web – Marco Ronchetti 2021 – Università di Trento What is the difference between the Web and the Internet? 7 Introduzione alla programmazione web – Marco Ronchetti 2021 – Università di Trento What is the difference between the Web and the Internet? § "The
    [Show full text]
  • UK Research Data Registry Mapping Schemes
    UK Research Data Registry Mapping Schemes Project Information Project Identifier PID TBC Project Title UK Research Data (Metadata) Registry Pilot Project Hashtag #jiscrdr Start Date 1 October 2013 End Date 31 March 2014 Lead Institution Jisc Project Director Rachel Bruce Project Manager — Contact Email — Partner Institutions Digital Curation Centre (Universities of Edinburgh, Glasgow, Bath); UKDA (University of Essex) Project Webpage URL TBC Programme Name Jisc Capital Programme Document Information Author(s) and Role(s) Alex Ball (Metadata Coordinator) Date 12 February 2014 Project Refs T3.1; D3.1 Filename uk-rdr-mapping-v06.pdf URL TBD Access This report is for general dissemination Document History Version Date Comments 01 29 November 2013 Summary of RIF-CS. First draft of DDI mapping. 02 8 January 2014 Second draft of DDI mapping. First draft of DataCite mapping. 03 22 January 2014 New introduction. Expanded summary of RIF-CS. First draft of EPrints ReCollect, NERC Discovery, and OAI-PMH Dublin Core mappings. 04 23 January 2014 Section on tips for contributors. 05 31 January 2014 Second draft of NERC Discovery (UK GEMINI), EPrints mappings. 06 12 February 2014 Third draft of DDI mapping. 1 Contents 1 Introduction 3 1.1 Typographical conventions . 3 2 RIF-CS 4 2.1 Elements . 4 2.2 Controlled vocabularies . 8 3 Internally managed RIF-CS elements 20 4 Mapping from DDI to RIF-CS 21 4.1 Related Objects . 22 5 Mapping from UK GEMINI 2 to RIF-CS 24 5.1 Related Objects . 26 6 Mapping from DataCite to RIF-CS 27 6.1 Related Objects .
    [Show full text]
  • Gemini and NTS Exit Reform API Usage Guidelines
    Gemini and NTS Exit Reform API Usage Guidelines ~ 1 ~ Table of Contents 1. Introduction ............................................................................................................................................6 1.1. API Technology Overview ....................................................................................................................6 2. API Client Development Guidelines .....................................................................................................8 2.1. HTTPS and SSL ...................................................................................................................................9 2.2. Authentication and Authorization ...................................................................................................... 10 2.3. Maintaining the Session .................................................................................................................... 10 2.4. Authentication / Loss of Session / Authorization Failures ................................................................. 10 2.5. Request a Compressed Response to your API Client ...................................................................... 11 3. API Configuration Details ................................................................................................................... 14 3.1. API Technology Overview ................................................................................................................. 14 3.2. Network Requirements .....................................................................................................................
    [Show full text]
  • Technical Standards Catalogue VERSION 6.2
    e-Government Technical Standards Catalogue VERSION 6.2 FINAL September 2005 Technical Standards Catalogue / version 6.2 final / September 2005 1 CONTENTS 1 INTRODUCTION ...........................................................................................................................3 2 CHANGES FROM PREVIOUS VERSION..................................................................................4 3 ISSUES UNDER CONSIDERATION............................................................................................5 4 INTERCONNECTION ...................................................................................................................7 TABLE 1 SPECIFICATIONS FOR INTERCONNECTIVITY.......................................................................7 TABLE 2 SPECIFICATIONS FOR WEB SERVICES ..............................................................................10 5 DATA INTEGRATION ................................................................................................................16 TABLE 3 SPECIFICATIONS FOR DATA INTEGRATION ...........................................................................16 6 CONTENT MANAGEMENT METADATA ...............................................................................19 TABLE 4 SPECIFICATIONS FOR CONTENT MANAGEMENT METADATA .................................................19 TABLE 5 SPECIFICATIONS FOR IDENTIFIERS .......................................................................................20 7 E-SERVICES ACCESS.................................................................................................................23
    [Show full text]
  • HTTPAPI S. Dalal Internet-Draft Intended Status: Standards Track E
    HTTPAPI S. Dalal Internet-Draft Intended status: Standards Track E. Wilde Expires: January 11, 2022 July 10, 2021 The Deprecation HTTP Header Field draft-ietf-httpapi-deprecation-header-02 Abstract The HTTP Deprecation Response Header Field can be used to signal to consumers of a URI-identified resource that the resource has been deprecated. Additionally, the deprecation link relation can be used to link to a resource that provides additional context for the deprecation, and possibly ways in which clients can find a replacement for the deprecated resource. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on January 11, 2022. Copyright Notice Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust’s Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
    [Show full text]
  • ECE 435 – Network Engineering Lecture 3
    ECE 435 { Network Engineering Lecture 3 Vince Weaver http://web.eece.maine.edu/~vweaver [email protected] 4 February 2021 Announcements • Homework #1 was posted/due Friday now (extension) • Last class cancelled due to snow. I guess they're going to be cancelling remote/hyrbid classes. • Sorry if that last class was a bit overwhelming with the C • Yes, HW#1 and #2 lots of coding. Know non-computer engineers not like this. Amount of coding drops off a lot after HW#2. 1 HW #1 notes • strace can be useful when tracking down issues. • Finding the \struct sockaddr" can be difficult. even if you find in under /usr/include it's tricky as it's a struct that is multiplexed via casting (to handle all possible socket types). Horrible thing about C. • How read() and write() work. ◦ Some people are having issues where they are writing 256 bytes (write will write as many bytes as you said, even if they are trailing zeros), but only reading 255. 2 This means the next read is going to get the last 0 rather than the following write. ◦ When reading, read(fd,buffer,size); What happens if you read 10 bytes but other side only has 4? Only read 4 (result). ◦ What happens read 10 bytes and other size has 12? You read 10 (result) but to get the rest you need to read again, otherwise it's there the next time you read. You can do a while loop. ◦ Also note that when you write, you should specify how many bytes you are writing or your whole buffer gets 3 sent even if empty.
    [Show full text]